Black Screen with Cursor after Waking from Sleep

I have noticed that this is a problem which gets often talked about, and I have seen posts from even 2020 talking about it, but I have noticed they often end up with a solution that doesn’t work for me, or an user saying “it’s a bug that they’re gonna fix soon”, or technical details that I am unable to understand …

But the issue I’m having is basically still the same: I have an nvidia GPU (which seems to be related to the problem), I am running plasma with x11. Whenever I put my computer to sleep, or whenever it does it automatically, the computer will be put into a state where, if I wake it up, it’ll greet me with just a black screen and a cursor, and the only way to get out of it is turning off my computer via the power button.

I have tried a handful of methods to solve this, but I know that I have no idea of what I am doing, and the last time I tried messing with the nvidia drivers I had to re-install my OS, so I’m trying to be as careful as possible.

Any help or guidance would be very appreciated, thank you in advance.

First, welcome to the forum.

Last night I installed EndeavourOS on a new Lenovo ThinkPad P14s Gen 5 AMD (no nvidia) and having the same exact issue. When I close the lid, or manually put it to sleep, I get a black screen with cursor. Can’t switch TTY to reboot or do anything else.

I had to enable REIBUS as it’s the only way I can safely reboot it.

This isn’t isolated to nvidia.

1 Like

As mentioned here, enabling the REISUB feature (for example using the Welcome app) helps so that you can reboot without using the power button after a freeze (and put your drive at risk) .

At work, search for my posts about the Archwiki, nVidia tips and tricks.

You need to enable a few services and point resume to an area of disk that is big enough.

I’m sorry but, I’m not sure what that is, or what it’s for? Could you explain?

You can search for word REISUB here on this forum and find the article by Kresimir describing it.
It is a kernel feature.

1 Like

This was definitely a workaround that works, and I have to thank you a lot for this, but do you know if there is a way to stop this issue from happening, instead of having to REISUB every time?

I don’t have any computers with Nvidia and it happens on them all. AMD, Intel both have this exact problem, it isn’t an nvidia issue.

My response was for @tab who reported having nvidia. I’m not sure in your case with AMD. Did you install with the option for hibernation? I think you can set this up still. That may make a difference so that it has a resume function?

Edit: I do have a lenovo Thinkbook with AMD and I don’t think it has this problem but i can’t say for sure as I don’t tend to use it that way. It’s either on or off. But i could check it when i get a chance.

Hi @ricklinux…yeah, I know you were talking to @tab but wanted to add that it happens on AMD and Intel so it’s not a Nvidia issue. I installed with swap without hibernation as I never hibernate, only sleep. Was there another option somewhere during the install as that’s all I seen about hibernation?

No… Also i just checked my lenovo Thinkbook and it doesn’t have hibernation mode enabled either. I have no issues with closing the lid for a long time and then opening it and it comes back to the login screen. I also tried sleep mode from the menu and it works also.

Edit: Have you checked settings in the Bios?

Edit: My hardware is Ryzen 5 5500U Thinkbook

Thanks for checking, yes I checked the bios and there isn’t any settings for sleep. It’s odd, it comes and goes. It won’t work for a while, then it will work fine, then it will stop working again. Happens on all my thinkpads running EndeavourOS.

I’ll keep watching and hopefully someone will find a solution one day. Appreciate your help, thanks.

1 Like

Also just wanted you to know. My EOS install is default. I don’t have anything special installed or settings changed or any packages related to power. I only have some packages that i install for normal use.

Minor progress…?
While trying to start plasma from the command line, I have recently found out that pressing ctrl+alt+f1,f2,f3 in random order (ending with ctrl-alt-f2 in my latest experiment) brings me back up to the login page. When logging in, weirdly, the plasma panel does not work, until, after waiting some time, my whatsapp opens up automatically, makes the windows glitch out, and then stuff goes back to normal.
I wonder what this could mean?