I fully agree this bug is valid and needs to be fixed. I only disagree with Sebastian's selection of High importance in the bigger picture.
"cannot open display" either means it's an X app and XOpenDisplay failed (Xwayland isn't running because mutter failed to start). Or it means it's a native Wayland client and it can't start because mutter failed to start. Either way, "cannot open display" is an expected error that's a side-effect of this bug (mutter failed to start). But it's not the cause of this bug and not relevant. I have some older hardware laying around that might experience this or similar issues. So I'll try to get to testing it out before we're too far into the new year. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
