I have a PC with AMD Ryzen 7 5700G CPU, no nvidia graphic, and using wayland…
Randomly, I get a black screen when resuming from suspend my PC in the morning. I can open a tty by pressing Ctrl-Alt-F5, then log as root, and look at loginctl output and get something like that :
SESSION UID USER SEAT LEADER CLASS TTY IDLE SINCE
11 0 root seat0 59364 user-early tty5 no -
12 0 root - 59504 manager-early - no -
3 1000 pascal seat0 2357 user tty2 no -
4 1000 pascal - 2528 manager - no -
4 sessions listed.
From here, I type loginctl activate 3, and then I get the mouse cursor, but it is still tty screen displayed. I can use my multimedia “Play” key, and music starts… So the session is still alive, but I cannot access it (as I can understand).
At this step, I have to go back to tty5 and reboot system. Once rebooted, I cannot find something relevant in the logs.
My question is about any other command I could use from tty to get my previous session back ? Any idea ?
The only thing I can see is the thousands of lines at the end of the log. avril 30 09:24:45 pascal-eos gnome-shell[2675]: [Smart Auto Move NG] _handleTimeoutSync() skipped: screen shield active or session locked
They come from a Gnome extension “Smart Auto Move NG” that allows to save desktop windows (position, size, and workspace). I thought it was not related to the problem (being a consequence and not the cause), but the number of lines every second is so high (thousands of lines every second)… It may need some action !
So I have disabled that extension for now. I will check now if issue is still present, and will update that post accordingly.
Quick update : The extension problem was a known defect, and is fixed with latest version. Which is now installed.
I will check again now, and if issue is still present, I will continue investigations focusing on Gnome extensions (deactivate all) to make sure issue is not coming from that side.
After one week using new version for “Smart Auto Move NG” extension (v59), which fix the issue with logs, everything works now as expected, and I have no more issue when resuming from suspend.
From that experience, when having such issue, I will now remember to disable all Gnome extensions and see what happens. The same good practice as for Firefox…
I should also have been more accurate when looking at logs, extension was the cause and not a consequence…