Looking at the reasoning behind that change, Mutter introduced lazy
initialisation of Xwayland: binding the two sockets, and starting
Xwayland when someone connected to the abstract namespace socket.
Flatpak apps apparently can't speak to the abstract namespace socket, so
would hang forever when started since the connection to the non-abstract
/tmp/.X11-unix socket was never accepted.
Rather than fixing the initialisation logic to start Xwayland on connect
to either socket, they dropped the abstract namespace socket. I'll talk
to the snapd folks about it, but this sounds like it should be dealt
with on the Mutter side.
** Changed in: mutter (Ubuntu)
Status: Invalid => Confirmed
--
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/1897224
Title:
[snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to
open X display
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1897224/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
