Sometimes when I wake my laptop up from sleep by simply opening the lid the screen will show my desktop for about a second then go completely black-- like the display stopped functioning or nothing’s being rendered to it. Temporary fix is to reboot. Anyone know why this is happening and how to fix? Thanks.
What do you have your power button set to do to get this to work in /etc/systemd/logind.conf? I tried setting the power button to hibernate instead of sleep HandlePowerKey=hibernate HandlePowerKeyLongPress=poweroff but get the same issue and am unable to get my display working again unless I hard shutdown with a long powerbutton press or by memorizing the keystrokes to open my terminal and type sudo shutdown now
I haven’t touched logind.conf, so I’m assuming the default settings are being used. I must also say, I haven’t been experiencing this issue for a while now
I can’t add much value to this topic, but just voicing that I also had this behavior some time ago on windows 11 and Ubuntu 23. It randomly went away probably 6+months ago. But after doing a BIOS reset (couldn’t remember my password, it was set when there was the archaic 10 character requirement) and updating the BIOS and drivers for my AMD 7840 the behavior has returned. I haven’t tried much yet, but I had the Chris Titus performance profile enabled for windows 11 and have since disabled that to see if it helps. It still seems to randomly not be able to wake from sleep, and when it happens no amount of power button presses fixes it. I have to restart the machine.
Hi, also jumping in to say that I am experiencing this issue frequently enough to the point that it’s becoming unbearable.
It happens at least twice a week where I’m in the middle of a work day and will close my lid for a few seconds only to find that the computer can’t wake up correctly. It will wake up for a few seconds and then the screen goes black, and it takes ~20 seconds to be able to wake up again. At this point I have to type in my password / authenticate with my fingerprint again to get back in (not log in again, just un-suspend I guess), only to go right back to sleep after a few more seconds.
So yeah, the only solution is to hard reset, which causes me to lose track of everything I had open / was working on.
For reference, this was happening on Fedora 42 and now also on 43. I’m on an AMD Ryzen 300 series chip, laptop is barely a month old but this has been happening since I got it.
Just happened to me again… there’s a post on the Fedora forums from awhile back with someone having the same issue and saying they had to change the refresh rate of their screen as a temporary fix:
Forget what I said about changing the resolution fixing it. Guess I just got lucky earlier.
Nothing seems to fix it other than a hard reset, and no logs are produced when running journalctl -f to view what’s happening in real time.
The only thing that seems slightly relevant might be systemd which I know nothing about. This only happens after putting the computer to sleep and waking it back up, so maybe there’s something there…..
Never mind - if @GG_S was also having this issue on Windows, then it probably has nothing to do with systemd or even Linux.
Relinking this post for reference… this person says they are on a Slimbook Executive with an Intel i7-13000H. So the issue also seems to be agnostic of device.
Is anyone else having this issue? I’m at a loss.