Bug 391995 - Inhibition handling is illogical
Summary: Inhibition handling is illogical
Status: RESOLVED FIXED
Alias: None
Product: Powerdevil
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-18 12:52 UTC by Dmitry
Modified: 2018-10-10 09:08 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 5.13.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry 2018-03-18 12:52:26 UTC
Inhibition from org.freedesktop.PowerManagement.Inhibit and org.freedesktop.ScreenSaver are handled pretty much the same way with preventing both sleep/suspend and screen power saving/screen locking. 
But that's absolutely illogical as far as powerdevil supports differentiation between these two types of wakelocks (e.g. on laptop lid close when external monitor is present).
So intentions for developers using these inhibitions are absolutely clear, just take a look at chromium (chromium/services/device/wake_lock/power_save_blocker/power_save_blocker_x11.cc:282) or ktorrent (ktorrent/ktorrent/pref/generalpref.ui, ktorrent/ktorrent/core.cpp:972) sources. 

This behaviour makes system keep screen on when no one app really needs it, like chromium/vavaldi/other forks playing audio (not video) or ktorrent downloading something.

It appears at least in KDE Neon, Fedora 26 and OpenSUSE Tumbleweed with 5.10 up to latest Plasma versions.
Comment 1 Kai Uwe Broulik 2018-10-10 09:08:59 UTC
Was fixed in Plasma 5.13