FS#50314 - [gnome-shell] Running apps as root with sudo/gksudo doesn't work when using Wayland
Attached to Project:
Arch Linux
Opened by beta990 (beta990) - Monday, 08 August 2016, 18:20 GMT
Last edited by Jan de Groot (JGC) - Thursday, 04 May 2017, 21:48 GMT
Opened by beta990 (beta990) - Monday, 08 August 2016, 18:20 GMT
Last edited by Jan de Groot (JGC) - Thursday, 04 May 2017, 21:48 GMT
|
Details
Description:
When using Wayland as session for Gnome-Shell running applications as root, results in: No protocol specified Additional info: * gnome-shell 3.20.3-1 * wayland 1.11.0-1 * wayland-protocols 1.5-1 * xorg-server-xwayland 1.18.4-1 * GDM3 with Wayland as session Steps to reproduce: * sudo atom /tmp/do.sh * gksudo/gksu atom /tmp/do.sh (hangs, unable to enter password) |
This task depends upon
Closed by Jan de Groot (JGC)
Thursday, 04 May 2017, 21:48 GMT
Reason for closing: Won't fix
Additional comments about closing: This is by design, Wayland will not fix this upstream and neither will we.
Thursday, 04 May 2017, 21:48 GMT
Reason for closing: Won't fix
Additional comments about closing: This is by design, Wayland will not fix this upstream and neither will we.
2. Is there anything in the logs when gksu/gksudo hang?
1. Atom isn't a good example, take an app like bleachbit that allows more cleaning when running as root.
But it should be no problem launching atom as root, since this works perfectly on a non Wayland-session.
2. Only the 'No protocol specified' message when executing this command in a terminal.
I'm happy to provide any debug info, unfortunately I'm not aware of available tools when using Wayland.
@JGC: Maybe this issue? https://bugs.freedesktop.org/show_bug.cgi?id=96547
I can remember this error showing up somewhere.
If this isn't an Arch-bug, maybe it's better to report upstream? :)
$ xhost +local:
But this command is a bit risky, could this be a Wayland-bug?
1. focusing of gksudo prompt: you can work around this by using pkexec or regular sudo
2. gui processes running under any form of sudo (sudo, gksudo, pkexec, etc) are unable to access the display
See here for more details about #2: https://bugzilla.redhat.com/show_bug.cgi?id=1274451
It seems that this is an upstream issue. However I think it's worth tracking here in case there is a distribution level workaround. It's unlikely to be a quick upstream fix, given that it's been an open issue on redhat for over a year. Freedesktop.org seems to be down for me right now, so I'm not able to see if it's been submitted there or not.