Comment 11 for bug 1897224
Revision history for this message
| James Henstridge (jamesh) wrote Re: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display | #11 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
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.