Adding the following rule to
/var/lib/snapd/apparmor/profiles/snap.chromium.chromium and reloading
the profile is enough to fix the problem:
/run/user/[0-9]*/.mutter-Xwaylandauth.* r,
** Description changed:
(initially reported by Laney on IRC)
I upgraded my eoan VM with silo 3762¹ which contains the gnome 3.33.90
update, and after logging out and back into a Wayland session, the
chromium snap fails to start:
- $ chromium
- No protocol specified
- (chrome:1917): Gtk-WARNING **: 16:08:39.262: cannot open display: :0
+ $ chromium
+ No protocol specified
+ (chrome:1917): Gtk-WARNING **: 16:08:39.262: cannot open display: :0
I'm seeing the following denial in the journal:
- name="/run/user/1000/.mutter-Xwaylandauth-5J7F6Z",
+ name="/run/user/1000/.mutter-Xwaylandauth.5J7F6Z",
requested_mask="r", denied_mask="r"
-
- ¹ https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3762/+packages
+ ¹ https://launchpad.net/~ci-train-ppa-
+ service/+archive/ubuntu/3762/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840925
Title:
[snap] chromium doesn't start under Wayland with GNOME 3.33
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1840925/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
