[Powerdevil] [Bug 369129] Powerdevil does not provide a way to inhibit screen saving
https://bugs.kde.org/show_bug.cgi?id=369129 --- Comment #5 from Manuel Amador (Rudd-O) <rud...@rudd-o.com> --- We should tackle the problem with KDE first, as KDE moves faster than GNOME and has a long history of innovating in this space (Solid). A KDE-only / Powerdevil-only solution is adequate for the first iteration of the PulseAudio side of things. Later on, we can ask the Power Manager folks to adopt the same inhibition policy. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 369129] Powerdevil does not provide a way to inhibit screen saving
https://bugs.kde.org/show_bug.cgi?id=369129 --- Comment #4 from Manuel Amador (Rudd-O) <rud...@rudd-o.com> --- I don't think things further up the stack have the necessary information to make an informed decision. The "sound card" of HDMI outs and the video cards powering them appear as different PCI devices in many cases. Those layers up the stack also do not know how to report back to Powerdevil "well, the reason we are not shutting the screen off, is because HDMI audio is active", primarily because it is stuff like Powerdevil which is in charge of policy and setting the right DPMS configuration bits on the X server (I assume something similar happens in Wayland). However, if Powerdevil provided an inhibitor (class) that would explicitly inhibit DPMS — but nothing else, not the screensaver, not screenlock in the screensaver, not suspend, not hibernate — then a plugin at the PulseAudio level of the stack can talk to Powerdevil and use that inhibitor class whenever there is an active HDMI audio stream, which is something that PulseAudio is perfectly positioned to know about. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 369129] Powerdevil does not provide a way to inhibit screen saving
https://bugs.kde.org/show_bug.cgi?id=369129 Manuel Amador (Rudd-O) <rud...@rudd-o.com> changed: What|Removed |Added CC||rud...@rudd-o.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 369129] Powerdevil does not provide a way to inhibit screen saving
https://bugs.kde.org/show_bug.cgi?id=369129 --- Comment #1 from Manuel Amador (Rudd-O) <rud...@rudd-o.com> --- The relevant PA thread is this one: https://lists.freedesktop.org/archives/pulseaudio-discuss/2016-September/026910.html -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 369129] New: Powerdevil does not provide a way to inhibit screen saving
https://bugs.kde.org/show_bug.cgi?id=369129 Bug ID: 369129 Summary: Powerdevil does not provide a way to inhibit screen saving Product: Powerdevil Version: 5.7.3 Platform: Other OS: other Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: rud...@rudd-o.com The D-Bus interface in Powerdevil (specifically the inhibitor interface) does not provide a working way that will let me inhibit screen saving (BUT, importantly, NOT the screen locker). What I am looking for is a D-Bus call that will let me inhibit DPMS power save on all screens of the session, while allowing the screen saver to kick in and display itself (even if it's the blank screen saver), and the screen locker to activate. I know I can tell the screen locker to inhibit itself, but that is the opposite of what I want, and furthermore does not prevent DPMS standby from kicking in. This is important because I am writing a PulseAudio policy module that will prevent screen blanking on HDMI devices when HDMI audio out is being used (DPMS standby kills the audio stream as soon as it kicks in). Thanks. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
