Red Hat Bugzilla – Bug 479481
KDE applications cannot be launched from konsole after su to another user
Last modified: 2009-01-10 19:29:30 EST
Description of problem:
KDE applications cannot be launched from konsole after su to another user.
This appears to be related to the value of DBUS_SESSION_BUS_ADDRESS
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start konsole
2. su fred # any user, root or non-root
kwrite hangs with no output to konsole and no display.
similar results with dolphin, kate
This is not an X11 authentication problem - non-KDE X11 apps have no problem.
kwrite opens in its own window
Run this command before launching kwrite:
(I found that I could launch KDE applications as another user by switching user with ssh; I compared the environments created by ssh and su, and discovered this fix by trial and error.)
System installed from x86_64 live CD to fresh partition, SELinux disabled, many more RPMs installed with yum. All components up to date with yum mirrors at
Fri Jan 9 22:25:07 GMT 2009
Nice workaround, but what do you expect us to do with this information?
This bug is a regression - this method of launching KDE applications as a different user worked with KDE 3 in Fedora 8 and earlier.
I am not sufficiently knowledgeable about the KDE/DBUS ecosystem to know where exactly the bug lies. However, I am sure that one of the Fedora maintainers will have that knowledge, and if the bug is considered sufficiently important, he/she will consider fixing it.
My workaround suggests that the problem lies in the interaction between KDE4 and DBUS, but does not come with any greater understanding than that. I thought you'd rather have the information than not have it.
Running GUI apps under su has never been a good idea, I've seen all sorts of problems caused by it in KDE 3, like permissions on Unix sockets used by KDE getting screwed up.
That's what kdesu is for (currently /usr/libexec/kde4/kdesu, we're going to replace the broken KDE 3 /usr/bin/kdesu with a symlink to that in the KDE 4.2 update, maybe already in an earlier update).
*** This bug has been marked as a duplicate of bug 473465 ***
(Oh, and your workaround is not a fix.)
Re #4: fair comment.