Unable to start graphical apps as root in konsole anymore

[Sebastian Vahl]

Hi.

I've seen this for some time now but hadn't had the time to look deeper into 
it: If I become root in konsole via su I'm not able to start graphical apps 
like kwrite or s-c-* anymore. There is no output in .xsession-errors, 
/var/log/messages or /var/log/secure, nor in the terminal itself. Also 
"reboot" or "halt -p" are not working. Simple x-apps like xterm or
xeyes are 
still working fine, though.

I see this on rawhide, F10 and F9, all with KDE 4.2.2. It doesn't matter if I 
use kdm or gdm, my normal user accout or a clean new one, nor a new clean 
installation. 

Is anyone else seeing this?

Sebastian

[José Abílio Matos]

On Tuesday 28 April 2009 10:48:44 Sebastian Vahl wrote:
>  Hi.
>
>  I've seen this for some time now but hadn't had the time to look deeper
>  into it: If I become root in konsole via su I'm not able to start graphical
>  apps like kwrite or s-c-* anymore. There is no output in .xsession-errors,
>  /var/log/messages or /var/log/secure, nor in the terminal itself. Also
>  "reboot" or "halt -p" are not working. Simple x-apps like xterm or
> xeyes
>  are still working fine, though. 
Are you using "su" or "su -"?

I don't have any problems here using the second version, it is necessary to 
get the environment variables right (read root's profile).

>  I see this on rawhide, F10 and F9, all with KDE 4.2.2. It doesn't
> matter if
>  I use kdm or gdm, my normal user accout or a clean new one, nor a new clean
>  installation.
>
>  Is anyone else seeing this?
>
>  Sebastian 
-- 
José Abílio

[Rex Dieter]

Sebastian Vahl wrote:

>  I've seen this for some time now but hadn't had the time to
> look deeper into 
>  it: If I become root in konsole via su I'm not able to start graphical apps 
>  like kwrite or s-c-* anymore.  
My advice:    Running gui apps, esp kde ones, under su is asking for 
trouble, and in general, is something you simply should not do.  That's 
what kdesu is for.

-- Rex