| Summary: | Closing laptop lid too quickly after pressing power button executes lid close action, not power button action | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | John van Spaandonk <jwork123nl> |
| Component: | Power management & brightness | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | jwork123nl, kde, nate, postix, ugur.alekperov, unruh |
| Priority: | NOR | Keywords: | usability |
| Version First Reported In: | 6.2.4 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
John van Spaandonk
2020-02-12 16:12:56 UTC
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 *** |