Xwayland is serving display ":0" and legacy X apps can use it just fine (like xterm, xeyes, xclock, bitmap). So that means the problem is probably the chromium binary. And since that's just a symlink to /usr/bin/snap this appears to be a snapd bug. Maybe.
-- 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 wayland won't start 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
