https://bugs.kde.org/show_bug.cgi?id=366125
Kai Uwe Broulik <k...@privat.broulik.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit| |http://commits.kde.org/powe
| |rdevil/48c3dca61d7cb808c904
| |a3a3659b2cd36fba1866
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
Version Fixed In| |5.7.4
--- Comment #13 from Kai Uwe Broulik <k...@privat.broulik.de> ---
Git commit 48c3dca61d7cb808c904a3a3659b2cd36fba1866 by Kai Uwe Broulik.
Committed on 10/08/2016 at 07:32.
Pushed by broulik into branch 'Plasma/5.7'.
Don't unconditionally emit buttonPressed on profile load
A button press (technically the "lid closed" event is also a button press)
should
always be some consicious action triggered by the user. By emitting this signal
unconditionally on profile load (ie. whenever changing an activity or
(un)plugging AC)
the session might always lock or suspend when this happens.
If and only if a profile would really like to take some action or set some
state
depending on the lid state on profile load - which none do, the handle button
press action should only react on explicit button presses anyway - it can still
ask the backend for isLidClosed in its onProfileLoad method.
FIXED-IN: 5.7.4
Differential Revision: https://phabricator.kde.org/D2325
M +0 -5 daemon/powerdevilcore.cpp
http://commits.kde.org/powerdevil/48c3dca61d7cb808c904a3a3659b2cd36fba1866
--
You are receiving this mail because:
You are watching all bug changes.
