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

Maciej J . Woloszyk <matof...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |matof...@gmail.com

--- Comment #9 from Maciej J . Woloszyk <matof...@gmail.com> ---
I've just came here searching for resolution of my problem - it's not as severe
as system corruption but it's really annoying,,,
I was trying to set-up automatic screen locking in KDE - it wasn't locking
properly after the timeout. After some search I found the reason - it's Chrome
inhibiting power management with "WebRTC has active PeerConnections". Yes - I
have an app active that uses WebRTC, but locking the screen manually doesn't
harm the app - after unlock connection is still intact and everything works
fine. So it would be great if the suppression from being possible at all had
some grading for it - like "suppress inhibition for screen lock", "suppress
inhibition for all cases" etc.

But I'll take even simple "suppress inhibition from this one app" :)

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

Reply via email to