** Changed in: gdm
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using XAUTHORITY, prevents root applications from
conne
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
https://help
** 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 => bugzilla.gno
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using XAUTHORITY, prevents
** Changed in: mutter
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using XAUTHORITY, prevents root applicat
** 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 because
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
Importanc
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 Xwa
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 compositin
** Changed in: gnome-shell (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using XAUTHORITY, prevents root applicatio
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 crashed
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 in
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 ins
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
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using
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
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using
** Changed in: gdm
Status: Confirmed => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using XAUTHORITY, prevents root applications from
c
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
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using XAUTHO
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 an
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.
W
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 in
> 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
$ 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 there'
** Project changed: wayland => balsa (Ubuntu)
** No longer affects: balsa (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using XAUTHORITY, preven
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
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/165228
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
25 matches
Mail list logo