Before it happened only occasionally, now it seems consistent: after some time the system is locked and suspended I cannot seem to wake it up with any input; I try to digit on the keyboard or click with the mouse, even tapping the shutdown button (which I know doesn’t shuts the system of, rather usually displays the sessions commands), but nothing happens. The only thing that’s left for me — that I know of — is forcing the shutdown.
This is my system:
Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1
Kernel Version: 6.17.12-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-2400 CPU @ 3.10GHz
Memory: 16 GiB of RAM (15.4 GiB usable)
Graphics Processor: llvmpipe
Manufacturer: LENOVO
Product Name: 7052A9G
System Version: ThinkCentre M91p
I think I can reproduce the issue by suspending the system and waiting for some time:
The system suspends after 15 minutes of inactivity
The screen shuts off after 10 minutes of inactivity, but when Plasma is locked it only waits for 1 minute.
I don’t know precisely if the problem is the screen not lighting up or the system not being waken up, but my monitor stays in stand-by when I try to wake the system up, so I think it’s the suspension.
Now it woke up successfully. I may need to try letting it going into suspension without locking it first, but I would be grateful if someone could tell me some way of keeping a trace of what happens — a trace that won’t disappear if I have to shut it forcefully
you can use sudo journalctl -b -1 to look at what happened right before it went into suspend (from the last boot), but that won’t tell you anything about what happened when you tried to wake it.
i’ve ended up just using a script that calls sudo systemctl suspend rather than rely on the GUI controls in plasma as they seem fragile and i’m still on plasma 5… would have hoped it got sorted by now for plasma 6.
I’m definitely not an expert, but I’ve had some success with switching TTY when debugging these kinds of problems. In itself it doesn’t fix the underlying problem, but it is helpful to be able to log in and view logs in order to troubleshoot further.
Perhaps you can try that to figure out if the system itself is actually powered on or not?
To switch TTY, I use: CTRL+ALT+F3.
If the screen powers on and displays a login prompt in the terminal, then you’ll know that the system is definitely powered on.
I believe you can switch back to the “original” TTY by simply using CTRL+ALT+F1.
Thanks. This is a tower pc, not a laptop, therefore I’m on an external keyboard. I see that inxi requires lots of packages for perl. Do you think we can obtain the same information with some built-in command?