Created attachment 182020 [details] logs-zip ## Summary This happens intermittently and I am not sure why. About one in ten times when resuming from suspend, KDE Plasma on Wayland shows a black screen with a visible and movable cursor and backlight. Restarting Plasma (`kwin_wayland --replace` and `plasmashell --replace`) brings up the login screen, but the desktop session is lost. No GPU panic, kernel oops, or obvious coredump is generated. ## System Information - Operating System: Arch Linux - KDE Plasma Version: 6.3.5 - KDE Frameworks Version: 6.14.0 - Qt Version: 6.9.0 - Kernel Version: 6.14.9-arch1-1 (64-bit) - Graphics Platform: Wayland - Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz - Memory: 23.2 GiB of RAM - Graphics Processor: Intel® Iris® Xe Graphics - Manufacturer: LENOVO - Product Name: 20W5S61M00 - System Version: ThinkPad T15 Gen 2i - All packages up to date as of 2025-05-31 - GPU drivers: i915 in use, xe module present but not used ## Steps to Reproduce (it occurs intermittently, about 1 in 10 times) 1. Start Plasma Wayland session. 2. Suspend the laptop (close lid or run `systemctl suspend`). 3. Resume from suspend. 4. Observe: black screen, backlight on, cursor visible and movable, but no desktop. 5. Switch to TTY (Ctrl+Alt+F3), run: ```sh DISPLAY=:0 XDG_SESSION_TYPE=wayland /usr/bin/kwin_wayland --replace & DISPLAY=:0 /usr/bin/plasmashell --replace & ``` 6. Plasma restarts, but user is dumped to login screen (SDDM). ## What Happens - Black screen with backlight and cursor after resume. - Desktop environment is unresponsive. - Restarting Plasma returns to login screen, session is lost. ## What Should Happen - Desktop should restore correctly after resume, with all windows and session state intact. ## Logs Please find attached zip file containing logs to 2 events as described above. Here is the script I have used to collect the relevant logs: #!/bin/bash TS=$(date +"%Y-%m-%d_%H-%M-%S") OUTDIR="$HOME/suspend-debug-logs/$TS" mkdir -p "$OUTDIR" echo "Collecting logs to $OUTDIR ..." sudo dmesg > "$OUTDIR/dmesg_after_resume.txt" sudo journalctl -b -n 1000 > "$OUTDIR/journalctl_last1000.txt" sudo journalctl --user -n 1000 > "$OUTDIR/journalctl_user_after_resume.txt" lsmod > "$OUTDIR/lsmod.txt" lspci -nnk > "$OUTDIR/lspci.txt" ps auxf > "$OUTDIR/ps_auxf.txt" loginctl session-status > "$OUTDIR/loginctl_session_status.txt" loginctl list-sessions > "$OUTDIR/loginctl_list_sessions.txt" who > "$OUTDIR/who.txt" coredumpctl list > "$OUTDIR/coredumpctl_list.txt" loginctl show-session $(loginctl | grep "$(whoami)" | awk '{print $1}') > "$OUTDIR/loginctl_show_session.txt" loginctl user-status > "$OUTDIR/loginctl_user_status.txt" cat /proc/driver/rtc > "$OUTDIR/rtc.txt" 2>/dev/null || true echo "Done! Logs collected in: $OUTDIR" echo "You can now upload this folder for further analysis." ## Additional Info - No evidence of GPU, compositor, or kernel crash in logs. - i915 is loaded, xe module is present but not used. - Problem persists across multiple kernel and Plasma updates. - System is a ThinkPad T15 Gen 2i (LENOVO 20W5S61M00). - No external monitors in use. - If more info or specific log extracts are needed, I can provide them. --- **Thank you for your help! Let me know if more info is needed.**
After step 3, was the screen locker involved at all? Or have you disabled screen locking? Could be Bug 494262. Would be great to get confirmation about whether it happens in the Plasma 6.4 beta (or the final release in about two weeks).
(In reply to Nate Graham from comment #1) > After step 3, was the screen locker involved at all? Or have you disabled > screen locking? > > Could be Bug 494262. Would be great to get confirmation about whether it > happens in the Plasma 6.4 beta (or the final release in about two weeks). Hi Nate, thanks for your help. I have the screen locker enabled but I do not see it after resume. Only black screen with cursor. I can still pause / play music with hotkey so it seems the system is still running fine in the background. It would be great if resolved in the update! its really frustrating as it is intermittent and difficult to reproduce and find the problem. Appreciate your help. Let me know if I can provide anything else
When this happens, can you switch to another TTY (e.g. with Ctrl+Alt+F4), log in, and see if the screen locker process is running with `ps -e | grep -i kscreenlocker`? Then while in that TTY, if you run `sudo loginctl unlock-sessions` and enter your password, can you switch back to the TTY with your normal session (e.g. with Ctrl+Alt+F1, Ctrl+Alt+F2, or Ctrl+Alt+F) and see your normal desktop?
(In reply to Nate Graham from comment #3) > When this happens, can you switch to another TTY (e.g. with Ctrl+Alt+F4), > log in, and see if the screen locker process is running with `ps -e | grep > -i kscreenlocker`? > > Then while in that TTY, if you run `sudo loginctl unlock-sessions` and enter > your password, can you switch back to the TTY with your normal session (e.g. > with Ctrl+Alt+F1, Ctrl+Alt+F2, or Ctrl+Alt+F) and see your normal desktop? Sure I will do that when it happens again and report back. May take a little while as I gotta wait for it to happen as I can't reproduce.
Ok it happened again so I could test your requests. (In reply to herms123 from comment #4) > (In reply to Nate Graham from comment #3) > > When this happens, can you switch to another TTY (e.g. with Ctrl+Alt+F4), > > log in, and see if the screen locker process is running with `ps -e | grep > > -i kscreenlocker`? > > > > Then while in that TTY, if you run `sudo loginctl unlock-sessions` and enter > > your password, can you switch back to the TTY with your normal session (e.g. > > with Ctrl+Alt+F1, Ctrl+Alt+F2, or Ctrl+Alt+F) and see your normal desktop? > > Sure I will do that when it happens again and report back. May take a little > while as I gotta wait for it to happen as I can't reproduce. (In reply to Nate Graham from comment #3) > When this happens, can you switch to another TTY (e.g. with Ctrl+Alt+F4), > log in, and see if the screen locker process is running with `ps -e | grep > -i kscreenlocker`? > > Then while in that TTY, if you run `sudo loginctl unlock-sessions` and enter > your password, can you switch back to the TTY with your normal session (e.g. > with Ctrl+Alt+F1, Ctrl+Alt+F2, or Ctrl+Alt+F) and see your normal desktop? Ok it happened again finally. Been very stable. Output of `ps -e | grep -i kscreenlocker' : 13162 ? 00:00:00 kscreenlocker_g Unfortunately after `sudo loginctl unlock-sessions` the result is still the same. Still black screen with cursor when I switch back to the tty. I still need to run: 'DISPLAY=:0 XDG_SESSION_TYPE=wayland /usr/bin/kwin_wayland --replace & DISPLAY=:0 /usr/bin/plasmashell --replace &' Or reboot Let me know if you need anything further. Hopefully future updates resolve it but its not very regular right now at least.
Thanks, that's very helpful. Sounds almost identical to Bug 494262. Are you using multiple screens? Also, if you have the ability to test the Plasma 6.4 beta, would you be able to see if it ever still happens there? If not, you can wait until Plasma 6.4.0 is released in a little over a week.
(In reply to Nate Graham from comment #6) > Thanks, that's very helpful. Sounds almost identical to Bug 494262. Are you > using multiple screens? Also, if you have the ability to test the Plasma 6.4 > beta, would you be able to see if it ever still happens there? If not, you > can wait until Plasma 6.4.0 is released in a little over a week. No additional screens, only the native laptop screen. Sorry I don't have time to try out the beta right now. I will check after the update thanks.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
Unfortunately I can confirm that I continue to get this behavior on the new plasma 6.4
I'm now seeing this bug on two systems in fedora since 6.4.1 on resume. Jul 01 01:59:05 kernel: kscreenlocker_g[21849]: segfault at f2c ip 00007f21f834219d sp 00007ffcae3d0da0 error 4 in libLayerShellQtInterface.so.6.4.1[319d,7f21f833f000+7000] likely on CPU 3 (core 3, socket 0) Jul 01 01:59:05 kernel: Code: be 02 00 00 00 4c 89 e7 31 c0 e8 2e da ff ff 49 83 7e 10 00 0f 85 8b 00 00 00 49 8b 87 b0 01 00 00 48 85 c0 74 32 4c 8b 63 18 <4c> 8b 70 18 44 8b 6d a8 4c 89 e7 e8 53 d9 ff ff 48 83 ec 08 31 d2
This exact issue or very similar is happening to me on a desktop PC. When I turn off the screen and then come back and turn it on again I very often get a black screen with only the mouse pointer shown. There is no way out of this situation, only hard reset. It happens around 30-50% of the time. All this started around 1-2 weeks ago after a major upgrade on my Arch system. It seems to be related to https://bugs.kde.org/show_bug.cgi?id=453557 - Operating System: Arch Linux - KDE Plasma Version: 6.4.2 - KDE Frameworks Version: 6.15.0 - Qt Version: 6.9.1 - Kernel Version: 6.15.5-arch1-1 (64-bit) - Graphics Platform: Wayland - Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor - Memory: 64 GiB of RAM (62,7 GiB usable) - Graphics Processor: NVIDIA GeForce RTX 3060 - Manufacturer: Micro-Star International Co., Ltd. - Product Name: MS-7B79 - System Version: 1.0 - All packages up to date as of 2025-07-09 - GPU drivers: nvidia
(In reply to gilstrack from comment #11) > This exact issue or very similar is happening to me on a desktop PC. When I > turn off the screen and then come back and turn it on again I very often get > a black screen with only the mouse pointer shown. There is no way out of > this situation, only hard reset. It happens around 30-50% of the time. All > this started around 1-2 weeks ago after a major upgrade on my Arch system. > It seems to be related to https://bugs.kde.org/show_bug.cgi?id=453557 > > - Operating System: Arch Linux > - KDE Plasma Version: 6.4.2 > - KDE Frameworks Version: 6.15.0 > - Qt Version: 6.9.1 > - Kernel Version: 6.15.5-arch1-1 (64-bit) > - Graphics Platform: Wayland > - Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor > - Memory: 64 GiB of RAM (62,7 GiB usable) > - Graphics Processor: NVIDIA GeForce RTX 3060 > - Manufacturer: Micro-Star International Co., Ltd. > - Product Name: MS-7B79 > - System Version: 1.0 > - All packages up to date as of 2025-07-09 > - GPU drivers: nvidia The screen is an LG OLED TV, connected via HDMI.
Can anyone who was previously able to reproduce this issue still reproduce it in Plasma 6.4.5, Plasma 6.5 beta, or current git master?
(In reply to Nate Graham from comment #13) > Can anyone who was previously able to reproduce this issue still reproduce > it in Plasma 6.4.5, Plasma 6.5 beta, or current git master? No ain't seen it in a while Fedora 43 RPMS.