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 Desktop
Packages, 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

Status in snapd:
  Confirmed
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run chromium installed via snap in Ubuntu 20.10 when
  running Ubuntu Wayland session. Unfortunately, chromium wouldn't
  start:

  > chromium 
  [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to 
open X display.

  I am able to run Firefox just fine (assuming that Firefox still runs
  on xwayland) and also Intellij snap works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu47
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 25 09:45:16 2020
  InstallationDate: Installed on 2016-09-05 (1480 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Snap: chromium 85.0.4183.121 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to