https://bugs.kde.org/show_bug.cgi?id=340427
Pedro V <voidpointertonull+bugskde...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |voidpointertonull+bugskdeor
| |g...@gmail.com
--- Comment #3 from Pedro V <voidpointertonull+bugskde...@gmail.com> ---
I wonder if the specific described issue is still a problem. Without two
sessions, both the "Sleep" button and closing the lid works for me without
having to authenticate.
Bug 390634 (and related bugs mentioned there) suggest that related behavior was
changed since this issue got reported.
However I'd piggyback on this issue because even if the specific described
situation is not a problem anymore, the fundamental issue still exists, and Bug
328336 getting merged here suggests that we should consider the issue in the
title, not just the specific situation in the first comment.
In my case playing a video and locking the screen still leaves the video
playback's power management inhibition active, so even though the video can't
be seen, the screen never turns off which is a power waste now, but more and
more likely to be a source of OLED burn-in as OLED monitors are getting cheaper
(a significant change in the monitor market is expected next year).
The issue isn't straight-forward though as a session which still exists can be
quite active from some perspectives, so I can see shutdown/sleep/hibernation
inhibition making sense in cases like long running programs (video rendering,
AI/ML training) not wanting to be interrupted despite not having user
interactivity, but the mentioned screen power management inhibition in the case
of not even having anything visible from a session surely doesn't make sense.
--
You are receiving this mail because:
You are the assignee for the bug.
