Re: [trinity-users] kdesudo and kdesu

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