On 14 October 2010 07:10, Jimmy Johnson <JimmyJhn@...> wrote:
> Timothy Pearson wrote:
>>
>> OK, I have a workaround: deinstall kdesudo-trinity
>>
>> Yes, it seems odd.  However, kdesu is provided by kdelibs, and functions
>> correctly under Debian.  kdesudo is an addon program, and functions
>> correctly under Ubuntu, but not Debian.  I think this has something to do
>> with the X server as mentioned in the link I posted earlier, but I am not
>> sure.  I do know that the same problem with kdesudo is also present
>> (sporadically) on KDE4 up to version 4.2, and possibly even after that.
>>
>> Hope this helps!
>>
>> Tim
>>
>
>
> Just so you know, removing kdesudo-trinity does get kmenu "run as a
> different user" working, thanks. :-)
>
> But at the same time my Squeeze install with kde4 has the kdesudo file
> installed and does not have the "run as a different user" problem. :-(
>
> And something is going on that's causing a 15min sudo timeout, that is not
> the Debian Way, root passwd should be asked for each time elevated
> permissions are needed and something besides the sudoers file is causing
> this and I don't know what it is, what ever it is I want to kill it.
>
> Just thought I'd let you know.
>
> --
> Jimmy Johnson
>
> Debian Squeeze - Trinity KDE 3.5.12 at sda12
> Registered Linux User #380263
>
>

Ok, getting somewhere now but still some odd behaviour. Purged
kdesudo-trinity and disabled my user from /etc/sudoers.

~/trinity/share/config/kdesurc reads:

[Passwords]
Keep=false

[super-user-command]
super-user-command=su

Now, if I do, e.g. <kdesu kwrite> in konsole:

dzz@exelinux:~$ kdesu kwrite
Error: "/tmp/kde-dzz" is owned by uid 1000 instead of uid 0.
Error: "/tmp/ksocket-dzz" is owned by uid 1000 instead of uid 0.
kdeinit: Shutting down running client.
/usr/bin/iceauth:  creating new authority file /root/.ICEauthority
Error: "/tmp/ksocket-dzz" is owned by uid 1000 instead of uid 0.
Error: "/tmp/kde-dzz" is owned by uid 1000 instead of uid 0.
kbuildsycoca running...
Error: "/var/tmp/kdecache-dzz" is owned by uid 1000 instead of uid 0.
Error: "/tmp/kde-dzz" is owned by uid 1000 instead of uid 0.
DCOP Cleaning up dead connections.
Error: "/var/tmp/kdecache-dzz" is owned by uid 1000 instead of uid 0.
Error: "/var/tmp/kdecache-dzz" is owned by uid 1000 instead of uid 0.
Error: "/var/tmp/kdecache-dzz" is owned by uid 1000 instead of uid 0.

It opens but then I can't use kicker or the menu to open anything
else, dcop server crashes:

"KLauncher could not be reached via DCOP"

If I then issue (as user) <kdeinit> everything then behaves normally
for the rest of the session! The error reappears on next login though.

This is now consistent over numerous reboots/relogins and for a second
user account also

Similar behaviour with sux

An annoyance but not a showstopper so far.

@Jimmy:

<help:/kdesu/using-kdesu.html> (in a konq window) might have a clue to
the password retention issue, seems a kde thing (probably
configurable)

Note my kdesurc

[Passwords]
Keep=false