** Changed in: gdm
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using XAUTHORITY, prevents root applications from
connecting
To manage
Launchpad has imported 30 comments from the remote bug at
https://bugzilla.gnome.org/show_bug.cgi?id=776437.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Bug watch added: bugzilla.gnome.org/ #776437
https://bugzilla.gnome.org/show_bug.cgi?id=776437
** Changed in: gparted
Importance: High => Unknown
** Changed in: gparted
Status: Fix Released => Unknown
** Changed in: gparted
Remote watch: GNOME Bug Tracker #776437 =>
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using XAUTHORITY, prevents root applications from
** Changed in: mutter
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using XAUTHORITY, prevents root applications from
connecting
** Changed in: gdm3 (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: mutter (Ubuntu)
Status: Confirmed => Triaged
** Changed in: mutter (Ubuntu)
Status: Triaged => In Progress
** Tags added: fixed-in-3.33.3 fixed-upstream
--
You received this bug notification
Sounds like a fix is on the way:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/626
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #643
https://gitlab.gnome.org/GNOME/mutter/issues/643
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/issues/643
I'm only recently familiar with the Mutter design, but...
Mutter is the graphics platform on which gnome-shell is built. Mutter
supports running under a Xorg server, or none at all on bare metal
(Wayland mode). So in order to provide a seamless consistent interface
in the latter case it spawns
On 8/21/2018 9:34 PM, Daniel van Vugt wrote:
> Phillip,
>
> Mutter is not just a binary, but is also the library which provides ALL
> the graphics for the login screen and gnome-shell. So yes Ubuntu does
> use mutter for everything :)
Ohh... I thought it was an alternative light weight
** Changed in: gnome-shell (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using XAUTHORITY, prevents root applications from
Phillip,
Mutter is not just a binary, but is also the library which provides ALL
the graphics for the login screen and gnome-shell. So yes Ubuntu does
use mutter for everything :)
If your Wayland login option has gone missing then that means the
Wayland backend ("eglnative") of mutter had
Ubuntu doesn't use mutter by default though ( is that what lubuntu uses?
). I looked at this again today and for some reason gdm isn't giving
the option to log in with a wayland session. I switched to lightdm and
it appears to not bother with Xwayland and just runs gnome-shell, and
gnome-shell
I updated the bug description to point to how openSUSE handles this bug
and opened a mutter task in case we want to copy it.
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
When running wayland, GDM fails to set up an XAUTHORITY file and
The official upstream GNOME bug has been moved to here:
https://gitlab.gnome.org/GNOME/gdm/issues/342
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using XAUTHORITY,
The official upstream GNOME bug has been moved to here:
https://gitlab.gnome.org/GNOME/gdm/issues/342
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using XAUTHORITY,
** Changed in: gdm
Status: Confirmed => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using XAUTHORITY, prevents root applications from
connecting
To
Because a non-root program can then use X11 to make that root program do
things you don't want.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using XAUTHORITY, prevents
How is not properly setting up the session, and preventing root from
showing things on the display, "for security"?
root, by definition, has the ability to do anything anywhere on the
system. Including reading and writing other users' files; reading and
writing the memory of processes (and FD's
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
It has been widely publicized at least since Fedora 25's release a year
ago that GNOME on Wayland does not support running GUI apps as root. It
has long been best practice for apps to not do this. Instead of trying
to implement clever workarounds, app developers should follow best
practice here.
On 12/7/2017 3:39 PM, Jeremy Bicha wrote:
> $ sudo su
> root@mycomputer:/home/me# gedit
> No protocol specified
> Unable to init server: Could not connect: Connection refused
>
> (gedit:4492): Gtk-WARNING **: cannot open display: :0
sudo defaults to scrubbing the environment; use sudo -E gedit
> And that's the problem here. When gparted is ported to gtk3, the
> xhost workaround will stop working.
When/if GParted is ported to gtk3, THEN the work around can be removed.
In the mean time the xhost workaround enables people to continue using
GParted.
--
You received this bug notification
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: balsa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
** Project changed: wayland => balsa (Ubuntu)
** No longer affects: balsa (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using XAUTHORITY, prevents root
$ sudo su
root@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
No, it is NOT the new standard since as I have said, wayland apps have
no issue running as root. Applications will NOT be totally rewritten to
split off the parts that need root into a separate program. YOU stop
changing the title, YOU are being a nuisance: this does not just affect
gparted. In
Wayland is now looking into this Dont know what they will do yet.In the
meantime I have found that if you insert (xhost si:localuser:root) into
start up applications it will work without having to do it in terminal
every time you start up.
--
You received this bug notification because you are a
@Jeremy, Yes, from what I've heard, that doesn't sound quite right
either. However I really have no idea so I'll let you guys deal with
this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652282
> Wayland applications running as root work just fine under Wayland. It
is X11 applications that do not work
I don't think that's true.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Ok, it worked now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using XAUTHORITY, prevents root applications from
connecting
To manage notifications about this bug
@Phillip, I am afraid that this is the new standard and it's not going
to change. Just use Xorg if you don't like it. But anyway, soon
applications will all upgrade their source code, and then when they meet
the set requirements they will all work as before. Just more securely.
So please stop
** Summary changed:
- GParted does not work in GNOME on Wayland
+ Xwayland not using XAUTHORITY, prevents root applications from connecting
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652282
I am afraid that this is a Wayland security feature and that it is not
going to be removed just because some users don't like it or don't
understand why it is there. As a workaround you can just carry on using
Xorg, but under Wayland the program has to be adapted in order not to
run the whole
It is a shame that you are unwilling to make a simple configuration
change to prevent a completely broken experience for your users. People
get very frustrated when they try to open an application and nothing
happens. No error message; nothing. All because of a silly default
policy. This is
@Dave Stroud,
If you spend a few minutes to create/install/modify some file(s), for
example 'gks' according to my previous comment, you need not type 'xhost
si:localuser:root' every time you boot up.
1. Some of us think that this is an unnecessary complication or worse,
2. Some of us think that
(xhost si:localuser:root) Is a work around I found on fedora forum. Only
problem is it has to be used every time you boot up.This is happening
with any program that uses root. It is a game breaker for wayland.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Philip, please file a bug with GNOME about that issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using XAUTHORITY, prevents root applications from
connecting
To
There are workarounds for GUI programs with elevated permissions in
Wayland. See these links
https://askubuntu.com/questions/961967/why-dont-gksu-gksudo-or-
launching-a-graphical-application-with-sudo-work-with-w
https://wiki.ubuntu.com/Wayland/gks
--
You received this bug notification because
38 matches
Mail list logo