You are not logged in.
I have checked work of power management in KDE 5 and GNOME. All works as it should work. I used chromium as an instrument of investigation.
At first I set 1 minute as duration after that the screen turns off, then watched a movie on youtube. When video was being played the screen was on. When video was paused the screen turned off after 1 minute. I've observed the same behaving in GNOME, but in GNOME on wayland power management works without paying attention on what chromium is doing or chromium doesn't report what it is doing to the power manager. In other words the screen turns off. Also I found out gnome power management depends on GDM and does not work without it. Moreover I checked how power management works in XFCE and MATE. It does not work as it works in GNOME and KDE, the screen turns off while watching something on youtube.
Then I began to think how to bring that functionality to awesome wm which sometimes I use. Maybe there are ready solutions? I became interested in to do a ready solution which will work in all desktop environments, window managers and Wayland compositors. Do you have any ideas? Now I am trying to comprehend how it works in GNOME & KDE. It looks like it has been integrated very deeply and can't be used separately from them. Well. I need some advise what should be done.
P.S. I am a little surprised because I used to be a user of awesome for a long time and didn't know about how well power management is in GNOME & KDE.
P.P.S I am not an English native speaker therefore this text might have lots of mistakes. Sorry.
Offline
There's that "dbus" stuff and the freedesktop.org project. I found this here: http://people.freedesktop.org/~hadess/i … /re01.html. That text says it's a draft and I can't find the real specification, but you can browse these things on a running system with a dbus browser tool, like for example d-feet or qdbusviewer. I'm running Gnome right now, and I can see those "Inhibit" and "UnInhibit" methods for org.freedesktop.ScreenSaver over here.
I'm guessing that's the messages that video players use to keep the screen from turning off, and your program probably can register itself as a target for those messages. I don't know how to do that in a program.
For an example about how to find out the last time when the user used the mouse or keyboard, you can look at the source code for a program named "xprintidle".
Last edited by Ropid (2015-10-19 01:24:43)
Offline
Thank you. I will begin with this.
Offline