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.
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.