trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: November 2011

[trinity-users] 3.5.13 : Use of gksu or sux causes klauncher crash

From: David Hare <davidahare@...>
Date: Wed, 02 Nov 2011 15:02:49 +0000
3.5.13 is now working fine (so far) with kdesu. Thanks Trinity team for 
dealing with bugs 394/451.

There is still an issue (here at least) with some apps, usually gtk, 
that use by default "gksu" (e.g. gparted) or "su-to-root -X -c command" 
(many of my custom scripts) Synaptic is ok, it already has a .desktop 
file for kde

The problem is just like before, e.g. "klauncher could not be reached 
via dcop" requiring relogin or to call kdeinit in a terminal (if you can 
get one)

This is however minor and easily fixable compared to 3.5.12, where sudo 
was mandatory by default (unacceptable for many Debian users)

I note also, <sux> still causes similar errors (worked in kde 3.5.9/10 
in Debian Lenny)

Workaround, if affected: Change relevant .desktop files to include 
"X-KDE-SubstituteUID=true" OR using kmenuedit tick "run as different 
user" OR just call <kdesu rootappname> in terminal or run box. Don't use 
"sux". Check your custom apps/scripts.

Regards,
David