No monitor signal after entering login credentials [SOLVED]

Message

Strange_Attractor · Post by **Strange_Attractor** » Tue Feb 17, 2026 5:53 pm

Since a recent update my system has turned completely unusable as I get no monitor signal after entering my login credentials. I use Gnome and GDM is my login manager. This happened after updating my system on February 11, and I have tried updating my system since then (last time today), to see if any update would resolve the issue. I have tried booting an older kernel (several actually, of which all were working fine previously). Any help would be greatly appreciated. I have no idea what info is relevant to provide, but I'll post some down below. Thanks in advance!

emerge --info:

https://pastebin.com/t4a5qTMy

journalctl -b 0 (after SSH:ing to my computer after logging in locally (after when the monitor dies)):

https://pastebin.com/PbujnFLZ

myNameIsNotAvailable... · Tue Feb 17, 2026 6:46 pm

Hello,

Could you post the output of the following command ?

Code: Select all

genlop -l | grep 'Feb 11'

This would give the list of packages updated and would be a good start to find the culprit :D
You may need to install app-portage/genlop !

Strange_Attractor · Post by **Strange_Attractor** » Tue Feb 17, 2026 7:36 pm

myNameIsNotAvailable... wrote:Hello,

Could you post the output of the following command ?
Code: Select all
genlop -l | grep 'Feb 11'
This would give the list of packages updated and would be a good start to find the culprit
You may need to install app-portage/genlop !

From Feb 11:

https://pastebin.com/5wNEXvJd

Feb 12 (I didn't finish updating completely on Feb 11):

https://pastebin.com/mpKj8UBV

myNameIsNotAvailable... · Tue Feb 17, 2026 8:33 pm

After digging a bit more in the logs it appears gnome-shell stops after gnome-evolution starts. Can't tell for sure if it's related.

Have you tried creating a new user and starting a gnome session with this clean new user ?

Could you disable Evolution autostart somehow and see if it still crashes ?

You could try manually running

Code: Select all

gnome-shell

in a bare tty to see how it behaves, too... You may have some interesting logs this way.

After that my best guess is to revert packages to try and fix the issue...

I'dd try reverting mesa first, then gnome-shell. (I recently had a bad experience with mesa 25.3.3 so I may be biased, but in my case reverting to 25.2.8 helped. And it appears you upgraded mesa too in your update).

You can use

Code: Select all

genlop -l | grep 'media-libs/mesa'

to have an history of installed versions.

I think reverting gnome-shell would imply a lot of other package downgrade (probably at least mutter), but I haven't used gnome in a long time.

Strange_Attractor · Post by **Strange_Attractor** » Tue Feb 17, 2026 9:09 pm

myNameIsNotAvailable... wrote: After that my best guess is to revert packages to try and fix the issue...

I'dd try reverting mesa first, then gnome-shell. (I recently had a bad experience with mesa 25.3.3 so I may be biased, but in my case reverting to 25.2.8 helped. And it appears you upgraded mesa too in your update).

I just masked mesa versions above 25.2.8, and it actually worked. The wallpaper disappeared, but other than that everything seems to be working just fine. Thanks a lot!

myNameIsNotAvailable... · Tue Feb 17, 2026 9:30 pm

Nice ! Glad I could help :D :D :D

Should I fill a bug on gentoo bugzilla about recent version of mesa being troublesome ? Mesa 26 was also broken meaning we have little to no hope that further upgrades would solve it...

What GPU are you using ? Mine was NVIDIA but I think I saw AMD in your logs... This implies the issue is not driver-related, not sway, not hyprland not gnome and not kde related but directly Mesa-related ?

Strange_Attractor · Post by **Strange_Attractor** » Tue Feb 17, 2026 10:03 pm

myNameIsNotAvailable... wrote:Nice ! Glad I could help

Should I fill a bug on gentoo bugzilla about recent version of mesa being troublesome ? Mesa 26 was also broken meaning we have little to no hope that further upgrades would solve it...

What GPU are you using ? Mine was NVIDIA but I think I saw AMD in your logs... This implies the issue is not driver-related, not sway, not hyprland not gnome and not kde related but directly Mesa-related ?

Thanks again for the help. It is probably a good idea to file a bug report - I would have done it myself if I would have had an idea of what information would be relevant to submit. You are very welcome to refer to this thread in case you file one. Yes, I use an AMD graphics card (Radeon 6700XT).