Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#16397 - Screen blanks when no activity screensaver is disabled or inhibited
Attached to Project:
Arch Linux
Opened by Artiom Molchanov (artiom) - Tuesday, 29 September 2009, 20:40 GMT
Last edited by Jan de Groot (JGC) - Saturday, 21 November 2009, 18:34 GMT
Opened by Artiom Molchanov (artiom) - Tuesday, 29 September 2009, 20:40 GMT
Last edited by Jan de Groot (JGC) - Saturday, 21 November 2009, 18:34 GMT
|
DetailsDescription:
I deactivated display sleep under System->Prefs->Power Managment and deactivated the screensaver under Sys->Prefs->Screensaver. Still, after about 15-20minutes of watching a movie without touching the mouse or keyboard, the screen just blanks, my monitor says 'NO SIGNAL' and shuts off. Additional info: * package version(s) gnome-screensaver 2.26.1-1 gnome-power-manager 2.26.3-1 xset -q: DPMS (Energy Star): Standby: 0 Suspend: 0 Off: 0 DPMS is Enabled Monitor is On This bug was already resolved on ubuntu: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/66257 Steps to reproduce: 1. Desactivate screensaver 2. Don't use the computer during 20-30 munites 3. Screen turns off |
This task depends upon
Closed by Jan de Groot (JGC)
Saturday, 21 November 2009, 18:34 GMT
Reason for closing: Fixed
Additional comments about closing: Assuming fixed.
Saturday, 21 November 2009, 18:34 GMT
Reason for closing: Fixed
Additional comments about closing: Assuming fixed.
Comment by Jan de Groot (JGC) -
Sunday, 08 November 2009, 21:01 GMT
Is this still an issue with 2.28.x?