Administrator mode should adapt to Qt theme

[tr.koch]

When go into the "Administrator mode", widgets don't respect my style and color
settings. To change this, kdesu should load the user's settings from ~./qt

[Kai F. Lahmann (kl)]

they do, but ~ is /root in admin mode...

[tr.koch (tristan-tknetwork)]

I see. Any other suggestions to solve this?
Btw, When running sudo kcontrol, kcontrol respects my settings.

[Bradley T Hughes (bhughes)]

I can confirm this bug... I run a 1280x800 screen at 120 dpi... the default fonts for all things root is 12pt, which ends up being 20
pixels on my screen. This makes doing most administrative tasks painful or impossible as windows are generally too large and buttons
are placed off the bottom of the screen.

[Robin (robin02)]

Same thing here.

If I start synaptic from konsole with "sudo synaptic" it uses the kde theme (so
the ugly gnome theme is replaced).
But when I start it with "kdesu synaptic" it uses the plain ugly gnome theme
instead of the kde theme.

I think the normal behaviour of kdesu should be the same as 'su'.

[Yuriy Kozlov (yuriy-kozlov)]

On my kubuntu dapper system the style I set is not used with either kdesu or sudo.

[Yuriy Kozlov (yuriy-kozlov)]

This would probably be difficult to fix since the program that's running as root would somehow have to know what user launched it to use their .qt

[Didier Raboud (odyx)]

As the root is not meant to be activated, add a (root) script that would dynamically link /root/.qt to ~/.qt before launching GUI's?

[Serhiy Kachaniuk (serzholino)]

When i running KDE application either with kdesu or sudo, the app gets theme settings from root user(lipstik).
When running Qt-only apps - with sudo app has my theme settings(plastic), with kdesu app gets root's qt theme settings(windows), which is even not root's KDE theme(lipstik)

System: Kubuntu Dapper release

[Sarah Kowalik (hobbsee-deactivatedaccount)]

presumably the settings in kubuntu-default-settings should be copied over to the root directory, like any new user?

[Anthony Mercatante (tonio)]

Basically, the kubuntu-default-settings are applying to any user, including root, as long as personnal settings are not set for that particular user too.

The settings are read and merged between the different config files in that order with that priority :
home folder > kds folder > /usr/share/apps/

As long as you customise either your account or the root one, there is not way to keep the parameters sync except copying ~/.kde too /root.

If you want to get that syncronized, what you can do is a script in /etc/init.d/rcS.d that copies /home/youruser/.kde and /home/youruser/.qt to /root.

There is no other way to make it automatic for us, basically because a system can have more than one user and it doesn't make sense synching the settings between all of them.

Secondly, the thing that makes kdesu doesn't use the gtk-qt-engines plugin is that the only way to get this confiured is with the first login, via the startkde script.

Sudo is using the user profile while kdesu is using the root one, and because there is no way to login as root by default, there is no way to get that gtk-qt-engine thing configured except copying from a configured profile.

I'm affraid there is no way to get that working as you all except, because touching too widely to kdesu implies security issues etc... although I admit that would be nice in that specific case :)

I don't have another option than to reject this, with the hope that maybe kde4 will deal with profiles differently.

[Rocco Stanzione (trappist)]

I would like to un-reject this, because I think there's a bug here - maybe a wishlist bug (which isn't a bug)... but anyway... I think kdesu should behave like sudo. Our docs say to use kdesu in place of sudo for launching KDE GUI apps, and sudo preserves $HOME. I expect kdesu to behave similarly, as it serves a similar purpose, and I expect most users do too.

[Yuriy Kozlov (yuriy-kozlov)]

How about having kdesu symlink /root/.qt and /root/.kde to the respective folders in /home/user? (at least rather than copying the folders) Is this possible?

[Anthony Mercatante (tonio)]

@ Rocco : It is very dangerous to let kdesu use the user's profile because the usage isn't the same.
Imagine the issues a software like kleansweep could cause with kdesu configured that way...

@ Yuriy : That's possible, but which account to link to ? There is not obviously one user account on a machine, there can be many of them, launched at the same time.
So even if you link manually, your trick can only work for one account.
Thus, this is not a possible solution for us.

[klerfayt (klerfayt-deactivatedaccount)]

so is there any hope hope that adept will behave same way as synaptics in the future, or the fact that user system settings can't be applied to package manager is the limitation of "kdesu"?
what happens then adept is launched with gksudo instead?

[klerfayt (klerfayt-deactivatedaccount)]

Can you make adept behave similar to synaptic packager manager, that does integrate better with customized desktop? (I guess synaptic uses some sort of workaround?)

[Che Guevara (che-guevara-3)]

We probably could use gksudo instead, but that will attract unnecessary GTK dependencies to a KDE installation.
Synaptic uses gksudo unless I am mistaken.

[Yuriy Kozlov (yuriy-kozlov)]

Tonio, is there some way to fix this in kdesudo?

[klerfayt (klerfayt-deactivatedaccount)]

fixed in gutsy gibbon ;-)

[Anthony Mercatante (tonio)]

Yep, I should have commented on this bug before, but kdesudo, replacement for kdesu, fixes those user<>root profiles issues

[Sarah Kowalik (hobbsee-deactivatedaccount)]

marking as fix released, based on Anthony's comment.

[klerfayt (klerfayt-deactivatedaccount)]

what happened? why the recent regression? Adept no longer adapts customized kde like it did then 7.10 was released.

[Anthony Mercatante (tonio)]

The reason of the regression is that letting the root profile write in the user's one make touched files unwriteable.
Therefore, there is no proper solution to let root started apps use the users profile...