SUMMARY When shutting down/restarting using the KDE UI and very fastly closing the lid, which is supposed to put the laptop to sleep, opening the lid will show us a screen with the symbols "^@". The laptop wont be in sleep mode nor have restarted. It is unrecoverable and has to be shut off by holding down the power button. STEPS TO REPRODUCE 1. Press the KDE menu icon 2. Select either restart of shutdown (Prefer shutdown) 3. When the 30 seconds for confirmation start counting. bring the laptop close to being closed to be ready 4. Press enter and the moment the UI registers that action and closes the 30 seconds window (Just to be sure), close the lid fast 5. Wait a couple of seconds without opening the lid (Just to be sure) OBSERVED RESULT The screen opens with a black background, with "^@" written, and unresponsive EXPECTED RESULT A proper shutdown or restart SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 42 KDE Plasma Version: 6.4.1 KDE Frameworks Version: 6.15.0 Qt Version: 6.9.1 ADDITIONAL INFORMATION Thinkpad T490 with Wifi 5 card, integrated. Kernel: 6.14.9-300.fc42.x86_64 Wayland
Cannot reproduce the issue on my Fedora 42 machine. It could be a hardware-specific power management issue. I also notice you're using an older kernel. I'm currently on 6.15.7. Can you try that one too and see if it works better?
I use Aurora and thus the newest kernel isnt available. I havent been able to find a single distro that ships the latest kernel + KDE for a usb. Is there something I am missing?
Arch, OpenSUSE Tumbleweed, and Fedora spring to mind.
I tried to do the same for sleep on the newest kernel that fedora can provide and I couldnt replicate it, this time at least. But I did replicate the shutdown freeze, getting a screen with "^@^@^@^@^@". My kernel version is 6.15.9.201. Also, it happens when I am in the KDE environment, and not on the log in screen.
On my Fedora machine, I also see "^@^@^@^@^@", but then it shuts a down properly as long as I don't close the lid too soon. If I do, it triggers Bug 417502. This is with Kernel 6.15.8 though. At this point it feels like a kernel or distro configuration bug; I'd recommend taking it up with the Fedora folks.