FS#51026 - [dbus] kde apps running via kdesu cannot connect to dbus socket
Attached to Project:
Arch Linux
Opened by Tomasz Przybył (FadeMind) - Wednesday, 28 September 2016, 19:02 GMT
Last edited by Jan de Groot (JGC) - Monday, 25 December 2017, 23:16 GMT
Opened by Tomasz Przybył (FadeMind) - Wednesday, 28 September 2016, 19:02 GMT
Last edited by Jan de Groot (JGC) - Monday, 25 December 2017, 23:16 GMT
|
Details
dbus 1.10.10-3
Launch any app with kdesu. App will not launched due dbus socket issue. Main sample kdesu systemsettings5 does not work at all. After Launch kdesu kate and launch OPEN window is not usable due socket dbus connection issue. |
This task depends upon
Closed by Jan de Groot (JGC)
Monday, 25 December 2017, 23:16 GMT
Reason for closing: Won't fix
Additional comments about closing: If you want to run applications as root, make sure the dbus session is setup for root yourself.
More and more GUI applications refuse to run as root anyways.
Monday, 25 December 2017, 23:16 GMT
Reason for closing: Won't fix
Additional comments about closing: If you want to run applications as root, make sure the dbus session is setup for root yourself.
More and more GUI applications refuse to run as root anyways.
The proper thing to do would be to ensure root's user systemd is around and set the environment correctly. pam_systemd will do that.
Starting from dbus version 1.10.10 I can't run GTK applications, like mousepad, with sudo. Application can't change it setting, and console spamming with one warning message.
dbus latest version on this moment - 1.10.12-1 (I'm on testing, but package with bug is in core repo).
Steps to reproduce:
1. Run 'sudo mousepad' or 'sudo gedit' or etc. in terminal emulator.
2. Try to change any settings and preferences.
3. Console will start spamming with message like:
(mousepad:5866): dconf-WARNING **: failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=de61eefaab024df39c960ff6b4067f9b --binary-syntax --close-stderr': Child process exited with code 1
I determined that the package must be configured through ./configure with the option --enable-x11-autolaunch, and mousepad or gedit can start and work properly through sudo.
AND
If I will type this command in terminal, it says:
1 dx37@Archey ~ % dbus-launch --autolaunch=de61eefaab024df39c960ff6b4067f9b --binary-syntax --close-stderr
Autolaunch requested, but X11 support not compiled in.
Cannot continue.
https://bugs.kde.org/show_bug.cgi?id=376189
see https://bbs.archlinux.org/viewtopic.php?id=224266
for example if I type :
kdesu kate
then there is no window, and no error message, even in dmesg,
it means that I can not run GUI programs in root mode with kdesu,
what is the alternative if kdesu doesn't work ?
I tried also to run dolphin with kdesu : it doesn't work,
the fact that there is no error/information message is annoying, the user will think that kdesu is not working