[Powerdevil] [Bug 340427] PowerDevil should only inhibit systemd on active sessions

[Oded Arbel]

https://bugs.kde.org/show_bug.cgi?id=340427

Oded Arbel  changed:

   What|Removed |Added

 CC||o...@geek.co.il

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 340427] PowerDevil should only inhibit systemd on active sessions

[Natalie Clarius]

https://bugs.kde.org/show_bug.cgi?id=340427

Natalie Clarius  changed:

   What|Removed |Added

 CC||natalie_clar...@yahoo.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 340427] PowerDevil should only inhibit systemd on active sessions

[Pedro V]

https://bugs.kde.org/show_bug.cgi?id=340427

Pedro V  changed:

   What|Removed |Added

 CC||voidpointertonull+bugskdeor
   ||g...@gmail.com

--- Comment #3 from Pedro V  ---
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 watching all bug changes.

[Powerdevil] [Bug 340427] PowerDevil should only inhibit systemd on active sessions

[soredake]

https://bugs.kde.org/show_bug.cgi?id=340427

soredake  changed:

   What|Removed |Added

 CC||ndrzj1...@relay.firefox.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 340427] PowerDevil should only inhibit systemd on active sessions

[Josef Kufner]

https://bugs.kde.org/show_bug.cgi?id=340427

Josef Kufner  changed:

   What|Removed |Added

 CC||j...@frozen-doe.net

--- Comment #2 from Josef Kufner  ---
This would also solve problems with suspend button not working on lock screen.
When locked, Powerdevil should release inhibit on buttons too and let
systemd-logind (or acpid or other system service) handle the situation.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 340427] PowerDevil should only inhibit systemd on active sessions

[Lucas Yamanishi via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340427

Lucas Yamanishi  changed:

   What|Removed |Added

 CC||lucas.yamani...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.