SUMMARY My laptop is set up to power off if I press the power button, and to go to sleep if I close the laptop lid. No screensaver active when the problem occurs. Also no full-screen video. STEPS TO REPRODUCE 1. Press power button to put laptop to sleep 2. Close laptop lid directly after pressing power button 3. that's it! OBSERVED RESULT Laptop goes to sleep (suspend?), apparently erroneously triggered by closing the laptop lid. EXPECTED RESULT The laptop should power off. I asked it to and it should not ignore it and do something else instead. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION This bug has been there for years. It looks like the developers did not test this scenario. No idea if the problem is in Powerdevil or not, feel free to reassign to appropriate component. Also let me know what other info you want!
There's definitely code in Powerdevil that checks if ksmserver is exiting and then ignores the suspend request. Possible that PowerDevil at this point was already killed and then logind takes over and just goes ahead anyway.
On 2020-02-12 17:15, Kai Uwe Broulik wrote: > https://bugs.kde.org/show_bug.cgi?id=417502 > > Kai Uwe Broulik <kde@privat.broulik.de> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |kde@privat.broulik.de > > --- Comment #1 from Kai Uwe Broulik <kde@privat.broulik.de> --- > There's definitely code in Powerdevil that checks if ksmserver is exiting and > then ignores the suspend request. > Possible that PowerDevil at this point was already killed and then logind takes > over and just goes ahead anyway. > I think that powermanagement in particular benefits from a system-wide development view. Too bad I do not have any experience with this. As a first step, is this problem reproducable?
Can confirm in current git master (which will eventually become Plasma 6.5) too.
*** Bug 406287 has been marked as a duplicate of this bug. ***
*** Bug 498593 has been marked as a duplicate of this bug. ***
I digged a bit and found there's a report #189456 from 2009(!) which already described the very same issue. It got closed without a general fix for everyone though.
*** This bug has been marked as a duplicate of bug 189456 ***