Description of problem: Please refer to 126771 Under native X11 the GNOME Display Manager (gdm) creates an xauth security token to allow apps access to the X11 display server, but under Wayland it doesn't. I tried this but so far I haven't been able to make it work: Version-Release number of selected component (if applicable): Gnome 3.18 or Wayland How reproducible: under Wayland, X11 clients run as another user (via su or sudo) are not authorised to connect to the X11 display server. However under native X11, clients run as another user are authorised to connect to the X11 display server. Under native X11 this works: [mike@localhost ~]$ sudo xdpyinfo | head -3 [sudo] password for mike: name of display: :0 version number: 11.0 vendor string: Fedora Project Under Wayland this fails: [mike@localhost ~]$ sudo xdpyinfo | head -3 [sudo] password for mike: No protocol specified xdpyinfo: unable to open display ":0". So far I have found these workarounds to allow GParted to run: 1) Login as root to the GNOME on Wayland desktop 2) Allow all local connections to the X11 display server xhost +local: Under native X11 the GNOME Display Manager (gdm) creates an xauth security token to allow apps access to the X11 display server, but under Wayland it doesn't. I tried this but so far I haven't been able to make it work: [mike@localhost ~]$ export XAUTHORITY=/run/user/`id -u`/Xauthority [mike@localhost ~]$ touch $XAUTHORITY [mike@localhost ~]$ xauth add $DISPLAY . `mcookie` [mike@localhost ~]$ sudo xdpyinfo | head -3 Invalid MIT-MAGIC-COOKIE-1 keyxdpyinfo: unable to open display ":0". Thanks, Mike Fleetwood (GParted Developer) Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Make that 1266771 (one 6 omitted from comment 1)
Closing this as duplicate of the original report to keep discussion in one place. *** This bug has been marked as a duplicate of bug 1266771 ***