this was also addressed in snapd in
https://github.com/snapcore/snapd/pull/9530 in 2.48
** Changed in: snapd
Status: In Progress => Won't Fix
** Changed in: snapd
Status: Won't Fix => Fix Committed
** Changed in: snapd
Status: Fix Committed => Fix Released
--
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:
Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X
display)
Status in Mutter:
Unknown
Status in snapd:
Fix Released
Status in mutter package in Ubuntu:
Fix Released
Status in snapd package in Ubuntu:
Won't Fix
Status in mutter source package in Groovy:
Fix Released
Status in snapd source package in Groovy:
Won't Fix
Status in mutter source package in Hirsute:
Fix Released
Status in snapd source package in Hirsute:
Won't Fix
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://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508
[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/.X11-unix/X0" (the abstract socket).
---
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/mutter/+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
