Black screen when choosing Wayland session

[bradleypariah]

So, I still have this issue: Holding down volume buttons ends current session

People on Reddit are suggesting it's this X11 bug: https://gitlab.freedesktop.org/xorg/.../-/issues/1261

Supposedly the fix was already merged six months ago, but I still have the problem, so will LTS users not get it? I really don't understand how to follow their conversations, or how to patch their fixes into my machine (or if that would just break something else).

So, others have suggested logging into Wayland for the time being.

For me, logging into Wayland is a crapshoot. 95% of the time, after entering my password, my monitor loses sync, and I'm stuck staring at a black screen until I reboot. If I hit the key combination to log out, I hear my chosen end-session chime, so I think Wayland is loading correctly, albeit at such a high (or low) resolution that my monitor can't find it. I'm really not sure though.

I do know that if I successfully log into Wayland, and I walk out of the room later, and power saving puts my monitor to sleep, I'll run into the same issue again when I return. Wiggle the mouse, tap spacebar, whatever, the monitor keeps saying "HDMI1 / Searching..." forever.

[GreyGeek]

https://askubuntu.com/questions/1234...20-04-problems

[bradleypariah]

https://askubuntu.com/questions/1234...20-04-problems

Thanks for the suggestion. I went ahead and tried that, but it made no difference. I was doubtful. Not sure that's the same problem. Those people are reporting that they are unable to boot due to CPU trouble.

My issue is that the resolution to my monitor is out of range after I put in my password.
X11 session works fine, but I have to put up with the volume button bug.

Is there a way to force a specific Wayland resolution & refresh rate before the session starts?

[GreyGeek]

https://ubuntuhandbook.org/index.php...-wayland-xorg/

https://askubuntu.com/questions/1404...rates-on-exter

[bradleypariah]

https://ubuntuhandbook.org/index.php...-wayland-xorg/

https://askubuntu.com/questions/1404...rates-on-exter

I think that first link has done it! Your Google-Fu is better than mine, because I searched for basically that article's name plus or minus a couple words, and I didn't see it.

Welp, I've only logged in once, but this is progress for sure. I'll test drive Wayland for the time being, and hopefully be able to stick to it. If not, I guess I'll have to figure out the volume-button-logout thing some other time. Thanks for your help!

[GreyGeek]

I think that first link has done it! Your Google-Fu is better than mine ...

https://www.kubuntuforums.net/forum/.../72413-dorking

[bradleypariah]

Sadly, these fixes appear to have only worked once. Now that I shut down my PC overnight, and tried to boot up and log back into Wayland this morning, my monitor cannot find a signal after entering my password. I do not get to see my splash screen (which is set to the default "Breeze" one).

I don't know if the session is failing to launch, or if it's defaulting to a resolution that is out of range. I had to hit my PC's reset button, and opt to log back into X11, so now it's only a matter of time before I get logged out for trying to adjust my volume. This is really frustrating.

Every time I Google my problem, everyone else's experience isn't quite like mine. Most results for "black screen after logging into Wayland" are about people having a blank desktop, with a mouse cursor, and they're able to drop to a terminal. I can't do that, because I can't see anything.

[Snowhog]

and they're able to drop to a terminal. I can't do that, because I can't see anything.

And pressing Ctrl+Alt+Fx (x = 1 through 7) doesn't bring you to a TTY session screen?

[bradleypariah]

And pressing Ctrl+Alt+Fx (x = 1 through 7) doesn't bring you to a TTY session screen?

As soon as I hit Enter after entering my password, my monitor says, "HDMI1 / Searching..."
I went ahead and tried those key combinations, and if they work, I can't tell because I cannot see it. Monitor continues to search for a signal until I force reset, then log back into X11.