This problem still exists in Karmic Kubuntu, even though gtk-qt-engine is now replaced by kcm-gtk. The workaround is still the same.
First you need to configure theme separately for root/sudo by starting system settings with command:
kdesudo systemsettings
The file .gtkrc-2.0-kde4 will be created in the root directory after you choose theme for GTK apps under the GTK Appearance. This file is worthless until you create .gthrc-2.0 symbolic link that points to it. For the security-conscious users out there, use the following command:
sudo ln -s /root/.gtkrc-2.0-kde4 /root/.gtkrc-2.0
This avoids linking user's file to root's file. I just hope that Kubuntu developers will some way, some how, make this work out of the box, so new users won't have to go through this. I've filed a bug report on this, but it is being mark as a duplicate of gtk-qt-engine bug.
This problem still exists in Karmic Kubuntu, even though gtk-qt-engine is now replaced by kcm-gtk. The workaround is still the same.
First you need to configure theme separately for root/sudo by starting system settings with command:
kdesudo systemsettings
The file .gtkrc-2.0-kde4 will be created in the root directory after you choose theme for GTK apps under the GTK Appearance. This file is worthless until you create .gthrc-2.0 symbolic link that points to it. For the security-conscious users out there, use the following command:
sudo ln -s /root/. gtkrc-2. 0-kde4 /root/.gtkrc-2.0
This avoids linking user's file to root's file. I just hope that Kubuntu developers will some way, some how, make this work out of the box, so new users won't have to go through this. I've filed a bug report on this, but it is being mark as a duplicate of gtk-qt-engine bug.
https:/ /bugs.launchpad .net/ubuntu/ +source/ kcm-gtk/ +bug/406747