New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monitor DPMS power-saving not working #3590

Open
tasket opened this Issue Feb 14, 2018 · 5 comments

Comments

Projects
None yet
4 participants
@tasket

tasket commented Feb 14, 2018

Qubes OS version:

R4.0-rc4


Steps to reproduce the behavior:

In xfce4-power-manager-settings adjust the display to suspend and/or power off after a set time, then wait.

Expected behavior:

As with R3.2, monitor goes into standby/suspend/low power mode.

Actual behavior:

Monitor display is blanked, but remains fully powered-on.

General notes:

This may be related to the fact that I used KDE on R3.2, and now I use Xfce on R4.0.


Related issues:

Maybe issue #2212

@taradiddles

This comment has been minimized.

Show comment
Hide comment
@taradiddles

taradiddles Feb 15, 2018

FWIW I've had the same problem since I began to use Qubes (aroud R3.0rcX), and like you I have the same problem with R4.0rc{3,4}. I used Xfce in R3.x so maybe Xfce's power manager is the culprit.

When sitting around the laptop doing other stuff I've noticed that the monitor would turn off but would then wake up after a few seconds and stay blank, without any user interaction.

Maybe double check that xscreensaver has its power management settings off.
(which makes me think that I'll try to disable Xfce's screen power management and enable xscreensaver's and see what happens).

FWIW I've had the same problem since I began to use Qubes (aroud R3.0rcX), and like you I have the same problem with R4.0rc{3,4}. I used Xfce in R3.x so maybe Xfce's power manager is the culprit.

When sitting around the laptop doing other stuff I've noticed that the monitor would turn off but would then wake up after a few seconds and stay blank, without any user interaction.

Maybe double check that xscreensaver has its power management settings off.
(which makes me think that I'll try to disable Xfce's screen power management and enable xscreensaver's and see what happens).

@schnurentwickler

This comment has been minimized.

Show comment
Hide comment
@schnurentwickler

schnurentwickler Feb 16, 2018

I got this issue as well since Q3.2.
Same bug already posted with similar behavior: https://unix.stackexchange.com/questions/4466/screen-turns-on-automatically-xset-dpms-force-off
My workaround after some research is to turn off xfce4-power-management stuff in System Tools -> Session and startup because it seems buggy. I am using the xorg displaycommand: xset s SECONDS (or xset s on / off) and it works very well.
But the xfce4 lockscreen does not work anymore for standby / lid-close.

I do not care about this chaotic window manager smacking, because a (soon) new qubes control center (...) handles display dpms and VM (video/fullscreen/notify) activity - working as an overlay with wayland hopefully.

schnurentwickler commented Feb 16, 2018

I got this issue as well since Q3.2.
Same bug already posted with similar behavior: https://unix.stackexchange.com/questions/4466/screen-turns-on-automatically-xset-dpms-force-off
My workaround after some research is to turn off xfce4-power-management stuff in System Tools -> Session and startup because it seems buggy. I am using the xorg displaycommand: xset s SECONDS (or xset s on / off) and it works very well.
But the xfce4 lockscreen does not work anymore for standby / lid-close.

I do not care about this chaotic window manager smacking, because a (soon) new qubes control center (...) handles display dpms and VM (video/fullscreen/notify) activity - working as an overlay with wayland hopefully.

@taradiddles

This comment has been minimized.

Show comment
Hide comment
@taradiddles

taradiddles Feb 16, 2018

But the xfce4 lockscreen does not work anymore for standby / lid-close.

Systemd manages lid events (among others) until an app like xfce's power manager "takes over". If you don't have xfce's power manager running you should be able to set HandleLidSwitch=lock in /etc/systemd/logind.conf. (see man logind.conf).
For standby a pre-suspend script that would run xcrensaver-command -lock should do the trick.
Not tested though...

But the xfce4 lockscreen does not work anymore for standby / lid-close.

Systemd manages lid events (among others) until an app like xfce's power manager "takes over". If you don't have xfce's power manager running you should be able to set HandleLidSwitch=lock in /etc/systemd/logind.conf. (see man logind.conf).
For standby a pre-suspend script that would run xcrensaver-command -lock should do the trick.
Not tested though...

@taradiddles

This comment has been minimized.

Show comment
Hide comment
@taradiddles

taradiddles Feb 28, 2018

For info dpms works as expected with xfce power manager's display settings disabled and xscreensaver's enabled (which should be identical to xset commands). The drawback for laptops is that there aren't different timeouts when on battery or AC. A workaround is to change the timeout with xset commands upon ac/bat events.

For info dpms works as expected with xfce power manager's display settings disabled and xscreensaver's enabled (which should be identical to xset commands). The drawback for laptops is that there aren't different timeouts when on battery or AC. A workaround is to change the timeout with xset commands upon ac/bat events.

@schnurentwickler

This comment has been minimized.

Show comment
Hide comment
@schnurentwickler

schnurentwickler May 20, 2018

If it is for the milestone 4.0 and future based releases: Avoid any Desktop Manager dependencies.
Qubes is far more robust and lesser bugged if the settings for dom0' system is set via configuration files.
Even if qubes is soon cloud based and/or remote using is possible, the user still needs a device to use qubes. And this device should be configured as simple as possible.
Xcfe (and most other window manager) are too much for qubes. Configuration is a pain.

If it is for the milestone 4.0 and future based releases: Avoid any Desktop Manager dependencies.
Qubes is far more robust and lesser bugged if the settings for dom0' system is set via configuration files.
Even if qubes is soon cloud based and/or remote using is possible, the user still needs a device to use qubes. And this device should be configured as simple as possible.
Xcfe (and most other window manager) are too much for qubes. Configuration is a pain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment