Back on the subject of this bug, it may be related to changes in the fd
numbers of -listen and -displayfd passed to Xwayland in mutter 3.38. If
that's relevant at all then it's probably still a snapd issue.
** Changed in: mutter (Ubuntu)
Status: In Progress => Invalid
** Changed in: mutter (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
** Summary changed:
- [snap] chromium wayland won't start in Ubuntu 20.10: Unable to open X display
+ [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X
display
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897224
Title:
[snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to
open X display
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897224/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
