gtkrc-2.0-kde deletion seems to happen in lines 200 to 231 of /usr/bin/startkde. The script checks there for existence of the new gtk2-engine-oxygen and activates it. To do so it deletes previous settings from qtcurve included the existing gtkrc-2.0-kde.
gtk2-engine-oxygen is not available for maverick, unless somebody plans to make it available with kde 4.6 which could point to a packaging error.
Anyway, the logic in these startkde lines looks a bit extrange to me, because it deletes gtkrc-2.0-kde even if gtk.engines-oxygen is not installed which I think is not correct.
gtkrc-2.0-kde deletion seems to happen in lines 200 to 231 of /usr/bin/startkde. The script checks there for existence of the new gtk2-engine-oxygen and activates it. To do so it deletes previous settings from qtcurve included the existing gtkrc-2.0-kde.
gtk2-engine-oxygen is not available for maverick, unless somebody plans to make it available with kde 4.6 which could point to a packaging error.
Anyway, the logic in these startkde lines looks a bit extrange to me, because it deletes gtkrc-2.0-kde even if gtk.engines-oxygen is not installed which I think is not correct.