GTK apps launched as superuser are unthemed

[usr]

Kubuntu 9.04 Beta: GTK apps launched as superuser are unthemed.

Screenshot: http://imagebin.ca/view/mHAgvzy.html

[Anthony Mercatante (tonio)]

Hi,

There isn't much more we can do right now on that point.
Indeed, the settings are set while the user logs in, within startkde, and therefore, only having launched a kde session once well make the gtk settings available.

This is due to gtk apps not beeing able to deal with kiosk settings in the first place.

The only way to fix in your case is to force globally the gtk settings for all users which is a lot too much untrusive.

We have to think of a better way to let kde settings available, but at the moment, there is nothing we can do on that point, especially this late in the release cycle.

That's something I knew about and that concerns me, and I'll try my best to make gtk bindings to kde more reliable and efficient in the future...

[usr (usrlp-deactivatedaccount-deactivatedaccount)]

Mandriva Linux's tools are GTK+, and this distribution doesn't have this problem.

In any case, although this can not be solved now, I think this bug should be marked as confirmed. It is a significant weakness in the consistency of appearance.

[usr (usrlp-deactivatedaccount-deactivatedaccount)]

Unacceptable. kademar Linux (it's based on Debian testing) can do this.
http://www.kademar.org/

[Ofir Klinger (klinger-ofir)]

In this thread there is a temporary solution:
http://ubuntuforums.org/showthread.php?t=811752

Or, as noted in one of the duplicates of this bug, run:
sudo cp ~/.gtkrc-2.0-kde4 /root/gtkrc-2.0
after each change you made to your GTK+ theme settings.

Hope that helps while the bug is being fixed.

[Harald Sitter (apachelogger)]

The problem is that the env variable that is responsible for the theming is reset by *sudo

2 Options:
1) Make kdesudo preserve that particular variable
2) Patch KApplication to (re)set the variable and thus make the whole startkde-hook stuff unnecessary

[Radovic Aleksandar (radovic1985)]

I can confirm this bug in kubuntu hardy and jaunty.

[Radovic Aleksandar (radovic1985)]

This works:
sudo cp ~/.gtkrc-2.0-kde4 /root/gtkrc-2.0

for hardy, you need to run
sudo cp ~/.gtkrc-2.0-kde /root/gtkrc-2.0

[Harald Sitter (apachelogger)]

I really think this should be fixed in kdesudo, not kds. The problem is really that sudo strips the env variable that would set the appropriate rc files as part of the lookup chain.

Ideally kdesudo would somehow transfer the env var into the sudo'd environment.