Black Screen and Cursor on System resume

Support Graphics & Display
1

Hello,

Recently with I have been having some problems with KDE when resuming and suspending my desktop. At one point it was every now and then that it would happen but now its seems to be more often and now its every suspend and resume that this problem occurs.

So when I wake my machine up from A resume, I’m presented with A black screen and A moveable cursor. I’m not sure what dose it or why but I so far have tried Kernel 5.7 and 5.8 and Nvidia-440 and Nvidia-450 drivers and it has not resolved the problem. I have also tried A fresh re-install but the problem still remains.

2

:+1: Welcome to Manjaro! :+1:

Please read this:

and post some more information so we can see what’s really going on. Now we know the symptom of the disease, but we need some more probing to know where the origin lies…

:innocent:

P.S. If you enter a bit more details in your profile, we can also see which Desktop Environment you’re using, which CPU/GPU you have, …

3

I have the same issue. Happens sometimes after waking from Hibernate, but not every time. My config:

System:    Kernel: 5.4.62-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: KDE Plasma 5.19.5 tk: Qt 5.15.0 
wm: kwin_x11 dm: SDDM Distro: Manjaro Linux 
Machine:   Type: Desktop System: Micro-Star product: MS-7A33 v: 2.0 serial: <filter> 
Mobo: MSI model: X370 GAMING PRO (MS-7A33) v: 2.0 serial: <filter> UEFI: American Megatrends v: 4.G0 
date: 01/22/2019 
Battery:   Device-1: hidpp_battery_0 model: Logitech MX Ergo Multi-Device Trackball serial: <filter> 
charge: 55% (should be ignored) rechargeable: yes status: Discharging 
Memory:    RAM: total: 15.65 GiB used: 11.85 GiB (75.7%) 
RAM Report: permissions: Unable to run dmidecode. Root privileges required. 
CPU:       Topology: 8-Core model: AMD Ryzen 7 1700 bits: 64 type: MT MCP arch: Zen rev: 1 L2 cache: 4096 KiB bogomips: 96018 
Speed: 3198 MHz min/max: 1550/3000 MHz boost: enabled Core speeds (MHz): 1: 3199 2: 3199 3: 3190 4: 3190 5: 3199 
6: 3199 7: 3149 8: 3149 9: 3180 10: 3180 11: 3197 12: 3197 13: 3194 14: 3194 15: 3199 16: 3199 
Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1 bmi2 bpext clflush clflushopt clzero cmov 
cmp_legacy constant_tsc cpb cpuid cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid f16c flushbyasid fma fpu 
fsgsbase fxsr fxsr_opt ht hw_pstate ibpb irperf lahf_lm lbrv lm mca mce misalignsse mmx mmxext monitor movbe msr 
mtrr mwaitx nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae pat pausefilter pclmulqdq pdpe1gb 
perfctr_core perfctr_llc perfctr_nb pfthreshold pge pni popcnt pse pse36 rdrand rdseed rdtscp rep_good sep sev 
sha_ni skinit smap smca sme smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 succor svm svm_lock syscall tce topoext 
tsc tsc_scale v_vmsave_vmload vgif vmcb_clean vme vmmcall wdt xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves 
Graphics:  Device-1: NVIDIA GP108 [GeForce GT 1030] vendor: Micro-Star MSI driver: nvidia v: 440.100 bus ID: 26:00.0 
chip ID: 10de:1d01 
Display: x11 server: X.Org 1.20.8 compositor: kwin_x11 driver: nvidia resolution: 1920x1200~60Hz s-dpi: 93 
OpenGL: renderer: GeForce GT 1030/PCIe/SSE2 v: 4.6.0 NVIDIA 440.100 direct render: Yes 
Audio:     Device-1: NVIDIA GP108 High Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 26:00.1 
chip ID: 10de:0fb8 
Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel 
bus ID: 28:00.3 chip ID: 1022:1457 
Sound Server: ALSA v: k5.4.62-1-MANJARO 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI driver: r8169 v: kernel 
port: f000 bus ID: 21:00.0 chip ID: 10ec:8168 
IF: enp33s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
IP v4: <filter> type: dynamic noprefixroute scope: global broadcast: <filter> 
IP v6: <filter> type: noprefixroute scope: link 
WAN IP: <filter> 
Drives:    Local Storage: total: 3.64 TiB used: 482.13 GiB (12.9%) 
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB size: 465.76 GiB speed: 31.6 Gb/s lanes: 4 
serial: <filter> rev: 1B2QEXM7 scheme: GPT 
ID-2: /dev/sda vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB speed: 6.0 Gb/s serial: <filter> rev: 3B6Q 
scheme: GPT 
ID-3: /dev/sdb vendor: Samsung model: HD103SJ size: 931.51 GiB speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> 
rev: 0001 scheme: GPT 
ID-4: /dev/sdh vendor: Samsung model: HD203WI size: 1.82 TiB speed: 3.0 Gb/s rotation: 5400 rpm serial: <filter> 
rev: 0003 scheme: MBR 
Optical-1: /dev/sr0 vendor: HL-DT-ST model: BD-RE BH08LS20 rev: 2.00 dev-links: cdrom 
Features: speed: 40 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram state: running 
RAID:      Message: No RAID data was found. 
Partition: ID-1: / size: 440.20 GiB used: 157.97 GiB (35.9%) fs: ext4 dev: /dev/sda2 label: N/A 
uuid: <filter> 
ID-2: /boot/efi size: 299.4 MiB used: 280 KiB (0.1%) fs: vfat dev: /dev/sda1 label: N/A uuid: <filter> 
ID-3: /run/media/nurunet/Backup Linux size: 915.89 GiB used: 324.05 GiB (35.4%) fs: ext4 dev: /dev/sdb1 
label: Backup Linux uuid: <filter> 
Swap:      ID-1: swap-1 type: partition size: 17.22 GiB used: 113.0 MiB (0.6%) priority: -2 dev: /dev/sda3 label: N/A
uuid: <filter>
Unmounted: ID-1: /dev/nvme0n1p1 size: 499.0 MiB fs: ntfs label: Recovery uuid: uuid: <filter>
ID-2: /dev/nvme0n1p2 size: 100.0 MiB fs: vfat label: N/A uuid: uuid: <filter>
ID-3: /dev/nvme0n1p3 size: 16.0 MiB fs: <superuser/root required> label: N/A uuid: N/A
ID-4: /dev/nvme0n1p4 size: 465.16 GiB fs: ntfs label: Windows 10 uuid: uuid: <filter>
ID-5: /dev/sdh1 size: 1.82 TiB fs: ntfs label: Backup Windows uuid: uuid: <filter>
USB:       Hub: 1-0:1 info: Full speed (or root) Hub ports: 14 rev: 2.0 speed: 480 Mb/s chip ID: uuid: <filter>
Device-1: 1-9:2 info: STMicro Solo 4.0.0 type: HID driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s
chip ID: 0483:a2ca serial: <filter>
Device-2: 1-10:3 info: Genesys Logic Multislot Card Reader/Writer type: Mass Storage driver: usb-storage
interfaces: 1 rev: 2.0 speed: 480 Mb/s chip ID: 05e3:0716 serial: <filter>
Hub: 2-0:1 info: Full speed (or root) Hub ports: 8 rev: 3.1 speed: 10 Gb/s chip ID: 1d6b:0003
Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002
Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 speed: 10 Gb/s chip ID: 1d6b:0003
Hub: 5-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002
Hub: 5-3:2 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s chip ID: 05e3:0608
Device-1: 5-3.2:3 info: Itron iONE type: Keyboard,HID driver: hid-generic,usbhid interfaces: 2 rev: 2.0
speed: 12 Mb/s chip ID: 195d:2029
Device-2: 5-3.3:4 info: Logitech Unifying Receiver type: Keyboard,Mouse,HID driver: logitech-djreceiver,usbhid
interfaces: 3 rev: 2.0 speed: 12 Mb/s chip ID: 046d:c52b
Hub: 6-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.0 speed: 5 Gb/s chip ID: 1d6b:0003
Sensors:   System Temperatures: cpu: 62.0 C mobo: N/A gpu: nvidia temp: 40 C
Fan Speeds (RPM): N/A
Info:      Processes: 391 Uptime: 17m Init: systemd v: 246 Compilers: gcc: 10.2.0 Packages: 1552 pacman: 1541 snap: 11
Shell: Zsh v: 5.8 running in: yakuake inxi: 3.1.05

Not sure if dmesg helps, but journalctl -p3 -b -1 gives me this:

-- Logs begin at Sun 2020-06-28 18:00:05 CEST, end at Thu 2020-09-10 10:57:57 CEST. --
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:20 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:23 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:26 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:29 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:32 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:35 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:38 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:41 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:44 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:47 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:50 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:53 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:56 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:59 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:62 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:63 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:66 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:69 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:72 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:75 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:78 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:81 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro systemd-udevd[438]: /etc/udev/rules.d/70-u2f.rules:84 Unknown group 'plugdev', ignoring
Sep 09 23:13:16 nurunet-manjaro kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled
Sep 09 23:13:46 nurunet-manjaro kwin_x11[9110]: kwin_core: Compositing is not possible
Sep 09 23:13:48 nurunet-manjaro python[9412]: backintime (nurunet/1): ERROR: Back In Time is not configured!
Sep 09 23:36:53 nurunet-manjaro systemd-coredump[27168]: Process 18341 (rosetta_4.20_x8) of user 966 dumped core.

Stack trace of thread 18341:
#0  0x0000000000000000 n/a (n/a + 0x0)
Sep 10 10:30:53 nurunet-manjaro kernel: Uhhuh. NMI received for unknown reason 3c on CPU 0.
Sep 10 10:30:53 nurunet-manjaro kernel: Do you have a strange power saving mode enabled?
Sep 10 10:30:53 nurunet-manjaro kernel: Dazed and confused, but trying to continue
Sep 10 10:32:45 nurunet-manjaro systemd-coredump[28882]: Process 15966 (rosetta_4.20_x8) of user 966 dumped core.

Stack trace of thread 15966:
#0  0x0000000000000000 n/a (n/a + 0x0)
lines 13-38/38 (END)
4

“Sometimes” are the worst issues to be able to diagnose remotely :sob: , so instead of trying to go back-and-forth 100 times, I’m going to point you to the kernel team’s debugging page:

https://www.kernel.org/doc/html/latest/power/basic-pm-debugging.html

because the output of your journalctl are just the errors and we don’t know if your kernel crashed because of the hibernation or because of the wakeup or something else entirely…

If you get stuck in the debugging above, feel free to shout and if you would find a solution, please post about it and then mark a solution like this:
Solution
so that the next person that has the exact same problem you just had will benefit from your post as well as your question will now be in the “solved” status.

:wink:

5

The short version:
I’m staying away from the 450 series and am back to the 440 series.

The long version:
Ok, so I did a fresh reinstall, switched some kernels and drivers around and pinned it to some issues.
I figured it is the NVIDIA driver 450 that dose not play nice with the lock screen / greeter when the machine suspends. I’m able to view my desktop one more again once I unlock the screen through the KDE connect app, so the solution is to use the 440 driver (the GPU in question is a Titan RTX) so unless a better 450 series nVidia driver patch comes along, 440 will due.

6

Nope: I’m still on the 440 series too and will only move over to the new series when all the bugs are ironed out by other people… Newest <> Best!

:wink:

7

I have the same problem, nvidia gtx 1060, 450xx driver. I have to kill kscreenlocker_greet to be able to login. Kinda sucks. Also, system settings gets a black left pannel, can’t use it unless I relog.

8

If the solution here doesn’t work for you, please open a new topic and link to this topic if it provides background information.

:+1:

9

Same here. It doesn’t matter if I use 440xx or 450xx drivers.

10

Re-iterating what I said before:

:man_shrugging:

1 Like
11