Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mutter |
Fix Released
|
Unknown
|
|||
snapd |
Fix Released
|
Undecided
|
Zygmunt Krynicki | ||
mutter (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Groovy |
Fix Released
|
High
|
Unassigned | ||
Hirsute |
Fix Released
|
High
|
Unassigned | ||
snapd (Ubuntu) |
Won't Fix
|
High
|
Unassigned | ||
Groovy |
Won't Fix
|
High
|
Unassigned | ||
Hirsute |
Won't Fix
|
High
|
Unassigned |
Bug Description
[Impact]
* Users who select the Wayland session on Ubuntu 20.10 cannot run snap
confined X11 applications, due to gnome-shell no longer listening on an
abstract socket for connections.
* The fix, which has been accepted into upstream's gnome-3-38 branch
reverts the change removing the abstract socket, and fixes the bug that
prompted it's removal:
https:/
[Test Case]
* Start with a stock Ubuntu 20.10 desktop install.
* At the GDM login screen, after selecting your user account use the gear
icon to select the "Ubuntu on Wayland" session, and log in.
* Ensure Chromium is installed by running "sudo snap install chromium".
* Try to run "chromium" from the terminal. Without the fix, it will fail
with the error "Unable to open X display". With the fix applied, it
will launch as normal.
[Regression Potential]
* The patch modifies the logic gnome-shell uses to launch Xwayland. So
there is a potential that the change could break X11 application
support on the Wayland session.
* The default configuration for gnome-shell is to launch Xwayland on
session start, so it should be immediately obvious if there are
problems.
* In addition to checking snapped X11 apps like Chromium, verify that a
few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc).
[Other Info]
* Running "ss -xlp | grep Xwayland" should show that it is listening on
both "/tmp/.X11-unix/X0" (the regular unix domain socket) and
"@/tmp/
---
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:
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
ProcVersionSign
Uname: Linux 5.8.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu47
Architecture: amd64
CasperMD5CheckR
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/
UpgradeStatus: No upgrade log present (probably fresh install)
summary: |
- chromium wayland won't start: Unable to open X display + [snap] chromium wayland won't start: Unable to open X display |
tags: | added: rls-gg-incoming |
Changed in mutter (Ubuntu): | |
assignee: | nobody → Daniel van Vugt (vanvugt) |
importance: | Undecided → High |
status: | New → In Progress |
Changed in snapd: | |
status: | New → Confirmed |
summary: |
- [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open - X display + Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X + display) |
no longer affects: | chromium-browser (Ubuntu) |
Changed in mutter (Ubuntu): | |
status: | Fix Committed → In Progress |
Changed in mutter (Ubuntu Groovy): | |
status: | Fix Committed → In Progress |
Changed in mutter: | |
status: | Unknown → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.