** Changed in: mutter
Status: Unknown => Fix Released
--
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:
Graphical snaps can't run in Gnome 3.38 Wayland sessions
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 was fixed in the package mutter - 3.38.1-2ubuntu1
---
mutter (3.38.1-2ubuntu1) groovy; urgency=medium
* Merge with debian, including various upstream fixes. Remaining changes:
- debian/gbp.conf: update upstream branch to point to ubuntu/master
-
It appears the update is being blocked by bug 1878293. Let's see if I
can unblock it...
--
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:
Graphical snaps can't run in
Is it possible to say (approximately) when the update will come to
regular Groovy release?
--
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:
Graphical snaps can't run
Scratch #38. It needed a reboot and now everything works fine.
--
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:
Graphical snaps can't run in Gnome 3.38 Wayland
I installed the Groovy-proposed updates, including:
Package mutter:
p A 3.38.1-1ubuntu1 groovy500
i A 3.38.1-2ubuntu1 100
Running a Snap results in the same
There is no mechanism to make it come faster. It's already on the way as
a proposed groovy update:
https://launchpad.net/ubuntu/+source/mutter/3.38.1-2ubuntu1
You can't get faster than that.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
For a substantial amount of users Wayland is important as it has better
performance and battery for integrated graphics. Having this bug unfixed
and breaking graphical snaps including chromium (which does not have an
apt package alternative) forces users to revert to X11/Xorg.
What is the
The KeePassXC and Stretchly snaps were not running under Wayland on
Groovy. The mutter 3.38.1-2ubuntu1 package from groovy-proposed fixed
the issue so that both of these snaps work again.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
This bug does not exist in Ubuntu 20.04 because the code that was
deleted to cause this bug is NOT deleted in Ubuntu 20.04.
You are experiencing a different problem so please open a new bug.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Hi,
I'm running focal (20.04.1 LTS) -- and hit this only just now when
upgrading to the new LTS.
So this is to confirm this affects the LTS release and I'd like to ask
for it back-ported. :)
Thanks,
-- Peter
--
You received this bug notification because you are a member of Ubuntu
Desktop
This bug was fixed in the package mutter - 3.38.1-2ubuntu1
---
mutter (3.38.1-2ubuntu1) groovy; urgency=medium
* Merge with debian, including various upstream fixes. Remaining changes:
- debian/gbp.conf: update upstream branch to point to ubuntu/master
-
I don't know if you need more confirmations, but upgrading to mutter +
libmitter from groovy-proposed fixed my chromium problem too.
(The only weird bit was how I was unconsensually logged out during the
upgrade, but that could've been plymouth or some other package.)
--
You received this bug
I can also confirm that after installing libmutter-7-0 from groovy-
proposed, 3 snaps that wouldn't run before now run (chromium, keepassxc,
vlc).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Updating to groovy-proposed libmutter-7-0, mutter, and mutter-common
fixed the display issues with the Irfanview (WINE) snap. Woo!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
geez,
That's a common mistake... When we ask people to test a mutter update we
actually mean 'libmutter' that's used by gnome-shell.
** Also affects: mutter (Ubuntu Hirsute)
Importance: High
Status: In Progress
** Also affects: snapd (Ubuntu Hirsute)
Importance: High
Status:
As geez did above, I installed libmutter-7-0, mutter, and mutter-common
from groovy-proposed. Zoom now opens and seems to run fine, which is
the snap that, for me, previously did not open. There seems to be a
draw issue that I have never had before though. When I close the
application, the
The bug affects me, too. I just installed the three above mentioned
mutter packages (libmutter-7-0 mutter mutter-common) and now Chromium is
working again. Thanks for the fix!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in
Seeing as the issue was solved for two other people, I had another go -
this time explicitly installing all mutter-related packages from
-proposed (and not just 'mutter'):
$ aptitude upgrade libmutter-7-0 mutter mutter-common
Lo and behold, the socket showed up:
$ sudo ss -xlp | grep Xwayland
I was running libmutter-7-0 3.38.1-1ubuntu1. I could reproduce the
initial bug of not being able to launch Chromium from the snap. After
upgrading to 3.38.1-2ubuntu1, now I can launch it fine.
Additionally, ss shows that Xwayland is listening on the abstract socket
too.
laney@nightingale> ss
Sounds like more votes/testers are required.
** Tags removed: verification-failed-groovy
** Tags added: verification-needed-groovy
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
I have the updated mutter package (3.38.1-2ubuntu1) and chromium snap is
working fine again.
Open sockets:
u_str LISTEN 0 1 @/tmp/.X11-unix/X0
64514* 0 users:(("Xwayland",pid=4667,fd=4))
Other relevant info I forgot:
- xeyes runs fine
- sockets:
$ ss -xlp | grep Xwayland
u_str LISTEN 0 1 /tmp/.X11-unix/X0 53665* 0
users:(("Xwayland",pid=2539,fd=4))
u_str LISTEN 0 1 /tmp/.X11-unix/X1 53666* 0
I have tested the package, and tested with several snaps including
Chromium.
```
wesley@wesley-desktop:~$ snap run spotify
Warning: GTK2 does not support Wayland!
Gtk-Message: 09:18:25.239: Failed to load module "gail"
Gtk-Message: 09:18:25.239: Failed to load module "atk-bridge"
(spotify:3046):
Hello Martin, or anyone else affected,
Accepted mutter into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/3.38.1-2ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
I've updated the description with the SRU bug template. I think this
includes all the relevant info?
** Description changed:
- I'm trying to run chromium installed via snap in Ubuntu 20.10 when
- running Ubuntu Wayland session. Unfortunately, chromium wouldn't start:
+ [Impact]
- > chromium
The snapd side of this fix is baking in
https://github.com/snapcore/snapd/pull/9530
** Changed in: snapd
Status: Confirmed => In Progress
** Changed in: snapd
Assignee: (unassigned) => Zygmunt Krynicki (zyga)
--
You received this bug notification because you are a member of Ubuntu
missing SRU description
--
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:
Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X
display)
To manage
** Changed in: mutter (Ubuntu)
Status: Fix Committed => In Progress
** Changed in: mutter (Ubuntu Groovy)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
I've just upgraded to groovy and hit this bug. For now I'm using socat
as a workaround:
socat abstract-listen:/tmp/.X11-unix/X0,reuseaddr,fork
unix:/tmp/.X11-unix/X0
This works, but is rather slow (and probably also opens a security hole
on multiuser machines).
--
You received this bug
Fix committed upstream to mutter 3.38.2, although still no fix on master
(mutter 40).
** Changed in: mutter (Ubuntu)
Status: Confirmed => Fix Committed
** Tags added: fixed-in-3.38.2 fixed-upstream
** Changed in: snapd (Ubuntu)
Status: Confirmed => Won't Fix
** Also affects:
I had a go at fixing this in
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 -- taking
the patches from that MR and applying them to the Groovy mutter source
package gave me a Wayland session that supported X11 snaps again.
It is probably worth waiting for a review from upstream
** Summary changed:
- [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)
--
You received this bug notification because you are a
34 matches
Mail list logo
