[Bug 1652282] Re: Xwayland not using XAUTHORITY, prevents root applications from connecting

[Jeremy Bicha]

$ sudo su
root at mycomputer:/home/me# gedit
No protocol specified
Unable to init server: Could not connect: Connection refused

(gedit:4492): Gtk-WARNING **: cannot open display: :0

=====
And that's the problem here. When gparted is ported to gtk3, the xhost workaround will stop working. And there's no incentive for GNOME to fix apps to run as root under XWayland, if they won't be able to under Wayland. GNOME wants to *encourage* apps to upgrade from gtk2 to gtk3 to get native Wayland support, better HiDPI support and several other features and improvements.

Therefore, I'm closing this bug. Sorry.

** Changed in: ubuntu-gnome
       Status: Triaged => Invalid

** Changed in: gdm3 (Ubuntu)
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gparted in Ubuntu.
https://bugs.launchpad.net/bugs/1652282

Title:
  Xwayland not using XAUTHORITY, prevents root applications from
  connecting

Status in gdm:
  Confirmed
Status in GParted:
  Fix Released
Status in Ubuntu GNOME:
  Invalid
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gparted package in Ubuntu:
  Invalid

Bug description:
  When running wayland, GDM fails to set up an XAUTHORITY file and instead
  relies on the process UID for authentication.  This prevents
  applications run as root, like gparted or synaptic from connecting to
  the server.  GDM needs to set up the XAUTHORITY file when running
  Xwayland just like it does when it runs the conventional Xorg.

  A large list of applications broken by this can be found here:

  https://codesearch.debian.net/search?q=Exec%3Dsu-to-
  root+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1652282/+subscriptions