http://bugzilla.novell.com/show_bug.cgi?id=622080
http://bugzilla.novell.com/show_bug.cgi?id=622080#c5
--- Comment #5 from Jon Nelson 2010-08-16 15:27:19 UTC ---
With all due respect, dbus-launch is *not* used to obtain super-user
privileges. dbus-launch has no capabilities to change user ids. The "File
Manager (Super User Mode)" menu entry gets its user-changing abilities from the
X-KDE-SubstituteUID=true entry in the dolphinsu.desktop file:
cat /usr/share/applications/kde4/dolphinsu.desktop
X-KDE-SubstituteUID=true essentially means "run kdesu for me".
(Click that command and instead of entering your password/passphrase, type in
another shell 'ps wax | grep dolphin') and you will see (something like) this:
/usr/lib64/kde4/libexec/kdesu -u root -c /usr/bin/dbus-launch dolphin -icon
system-file-manager -caption 'File Manager - Super User Mode' ''
I did eventually find out that moving the .Xauthority file (or removing it) is
sufficient to restore kdesu functionality. However, I can't tell you *why* the
Xauthority file is being corrupted, or how. On another machine, which I
execute kdesu *much* more frequently, I don't have the same issue (different
filesystem and block device layout, but both are openSUSE 11.3).
I wonder if the underlying issue has to do with this:
http://osdir.com/ml/network.openssh.general/2005-06/msg00029.html
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
