Blank screen with mouse cursor after wake from sleep

Desktop Environments Plasma
1

Hi. I’m experiencing the same problem described here. Basically when the laptop wakes from sleep there’s a blank screen with the cursor, I can move it and can press Ctrl-Alt-F2 to go to TTY2 and reboot. However, the solution in that thread isn’t applicable to my situation as I don’t have an nvidia card. It started happening today after a general update with pacman -Syu. Last time I updated before was 30 Oct.

$ inxi -z
CPU: 8-core AMD Ryzen 7 4800H with Radeon Graphics (-MT MCP-)
speed/min/max: 1399/1400/2900 MHz Kernel: 6.0.8-arch1-1 x86_64 Up: 23m
Mem: 4089.2/63720.9 MiB (6.4%) Storage: 1.82 TiB (21.9% used) Procs: 319
Shell: Bash inxi: 3.3.23
$ inxi -zG
Graphics:
  Device-1: AMD Renoir driver: amdgpu v: kernel
  Device-2: Chicony HD Webcam type: USB driver: uvcvideo
  Display: x11 server: X.Org v: 21.1.4 driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu
    resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6 Mesa 22.2.3 renderer: AMD Radeon Graphics (renoir LLVM
    14.0.6 DRM 3.48 6.0.8-arch1-1)
2

I don’t know how to make the code block contractible.

3

Does this happen if you use the lts kernel?

4

Reporting back that hibernating the system instead of sleeping works without problems.

I’m installing linux-lts to check whether that helps.

1 Like
5

The problem doesn’t happen with the lts kernel.

6

Scratch that. The problem is still there, be it linux-lts or linux.

1 Like
7

I have exactly the same problem. I’m also on AMD (Ryzen 9 5900HX).

I might try to switch to linux-lts but I’m not sure how to make sure the system uses the lts kernal…

For now I’ll try hibernating in stead of sleeping.

8

Hey @thatent, I’m now on the 6.0.9 kernel and haven’t been experiencing the issue recently. Hope that helps.

1 Like
9

That one needs to go into my list of favorite quotes.

Although the thread’s headline already inspired me big time; like what I see when waking up…

1 Like
10

The problem was still there with kernel version 6.0.9. It’s difficult to tell if the problem has gone away for good because it’s intermittent, it doesn’t happen every time. Now I updated the linux kernel to 6.0.12. Let’s see if that helps, though I’m under the impression that the problem isn’t just related to the kernel but also to KDE or SDDM.

I’m looking at the journalctl output from last boot, where the problem did occur, and don’t see anything unsual after opening the lid (ie waking from sleep) and before rebooting from tty2.

$ journalctl --no-hostname --pager-end -b -1
...
Dec 10 15:39:34 systemd-logind[519]: Lid closed.
Dec 10 15:39:40 systemd-logind[519]: Lid opened.
Dec 10 15:39:54 systemd-logind[519]: Power key pressed short.
Dec 10 15:40:02 systemd[1]: Started Getty on tty2.
Dec 10 15:40:02 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty2 comm="systemd" exe=">
Dec 10 15:40:02 kernel: audit: type=1130 audit(1670697602.064:193): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=get>
Dec 10 15:40:13 systemd[1]: Received SIGINT.
Dec 10 15:40:13 systemd[1]: Activating special unit System Reboot...
...
11

I’m having the same issue, it started a couple of weeks ago and still occurs on the 6.5.3 kernel. It’s intermittent.

 $ inxi -z
 CPU: dual core Intel Core i5-6300U (-MT MCP-) speed/min/max: 800/400/3000 MHz
 Kernel: 6.5.3-arch1-1 x86_64 Up: 8m Mem: 2.91/15.48 GiB (18.8%)
 Storage: 931.51 GiB (63.7% used) Procs: 210 Shell: Sudo inxi: 3.3.29
 $ inxi -zG
 Graphics:
   Device-1: Intel Skylake GT2 [HD Graphics 520] driver: i915 v: kernel
   Device-2: Bison ThinkPad P50 Integrated Camera driver: uvcvideo type: USB
   Display: x11 server: X.Org v: 21.1.8 driver: X: loaded: modesetting
dri: iris gpu: i915 resolution: 1920x1080~60Hz
   API: OpenGL v: 4.6 Mesa 23.1.7-arch1.1 renderer: Mesa Intel HD Graphics
520 (SKL GT2)`
12

I have an open KDE bug report for this, because it was driving me nuts: https://bugs.kde.org/show_bug.cgi?id=475605

I am using Nvidia, but given that there is an AMD version of this thread, I’m willing to assume that Nvidia is not the root cause of this particular problem.