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