Bug 573098 – kde-apps/konsole:5 can't be started via su

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description manuel 2016-01-27 10:55:01 UTC]

Created attachment 423972 [details]
Last relevant lines from journalctl -b

I've installed kde-apps/konsole-15.08.3, kde-apps/kdesu-15.08.3 and kde-frameworks/kdesu-5.18.0. Whenever I call kdesu konsole, I get asked for my password and when I enter it correctly, nothing happens. See attached log. It used to work with konsole:4.

[Comment 1 Andreas Sturmlechner 2016-01-27 16:05:21 UTC]

Does it work with kdesu5?

[Comment 2 manuel 2016-01-27 20:56:37 UTC]

Created attachment 424024 [details]
journalctl -b with kdesu5

[Comment 3 manuel 2016-01-27 20:57:14 UTC]

No, still doesn't work. Behaviour (and log as far as I can see) are the same.

[Comment 4 Andreas Sturmlechner 2016-01-27 22:03:07 UTC]

Hm true, although the use is not clear to me, I can confirm the error.

[Comment 5 Michael Palimaka (kensington) 2016-01-29 11:14:47 UTC]

I can't launch konsole:5 from regular su either, so perhaps it's not specific to kdesu. Can you confirm?

[Comment 6 manuel 2016-01-29 13:59:28 UTC]

I can't start konsole from su either, with this error:


QCoreApplication::arguments: Please instantiate the QApplication object first
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
KUniqueApplication: Cannot find the D-Bus session server:  "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." 

KUniqueApplication: Pipe closed unexpectedly. 


I can't start krusader from su either, with a different error:


krusader(16522)/kdeui (kdelibs): Session bus not found 
To circumvent this problem try the following command (with Linux and bash) 
export $(dbus-launch) 
KCrash: Application 'krusader' crashing...
KCrash: Attempting to start  from kdeinit
KCrash: Connect sock_file=/root/.kde4/socket-enigmage/kdeinit4__0                                                                                                                
Warning: connect() failed: : Connection refused                                                                                                                                  
KCrash: Attempting to start  directly                                                                                                                                            
KCrash failed to exec(), errno = 2      


But I can start krusader with kdesu! And kdesu5 as well, but I think that only has a difference in the frontend (not sure though).


I can start firefox with su and kdesu.

[Comment 7 manuel 2016-01-29 14:03:09 UTC]

I think KDE applications aren't meant to be started via su. I can't start okular via su either. There is some DBus issue in general if you start KDE stuff via su. In my limited understanding, that's just what kdesu fixes. The point is that the error in konsole is different from that.

[Comment 8 Andreas Sturmlechner 2016-08-18 00:04:42 UTC]

`kdesu5 konsole` works for me in konsole-16.07.90.

[Comment 9 manuel 2016-08-18 10:59:23 UTC]

Yes, fixed for me exactly as you describe. Thanks!