Bug 1047108 - monitor is not turned off
Summary: monitor is not turned off
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xscreensaver
Version: 20
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Mamoru TASAKA
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-29 06:16 UTC by Michal Minar
Modified: 2014-01-24 07:37 UTC (History)
3 users (show)

Fixed In Version: xscreensaver-5.26-2.fc20
Clone Of:
Environment:
Last Closed: 2014-01-15 06:11:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
config file (7.61 KB, text/plain)
2013-12-29 06:16 UTC, Michal Minar
no flags Details
xorg log (60.28 KB, text/plain)
2013-12-29 06:17 UTC, Michal Minar
no flags Details

Description Michal Minar 2013-12-29 06:16:00 UTC
Created attachment 842927 [details]
config file

Description of problem:
  Although DPMS is supported by both of my monitors, screensaver refuses to turn them off when blanking. It seems that screensaver does not recognize that powermanagement is supported. In config dialog, under Advanced -> Display Power Management, the Power Management Enabled is not grayed out. But if I toggle it on, it will be turned off again on next launch. Nevertheless the "Quick Power-off in Blank Only Mode" options is always on without any effect.

Version-Release number of selected component (if applicable):
  xscreensaver-base-5.26-1.fc20.x86_64

How reproducible:
  ALWAYS

Steps to Reproduce:
1. configure xscreensaver to "Blank Screen Only" with some timeout and "Quick Power-off"
2. lock the screen or wait until it's locked after idle timeout

Actual results:
  Monitors are blanked.

Expected results:
  Monitors are turned off.

Additional info:
  The same happens with only one of them active (laptop or external monitor) -- enabled/disabled with xrandr.

Comment 1 Michal Minar 2013-12-29 06:17:28 UTC
Created attachment 842928 [details]
xorg log

Comment 2 Mamoru TASAKA 2013-12-29 16:24:30 UTC
Would you choose any non-zero value for "Off After ... minutes", then
toggle in both "Power Management Enabled" and "Quick Power-off in
Blank Only Mode", and try again?

Comment 3 Michal Minar 2013-12-29 18:43:28 UTC
It works! Setting the value to anything positive does the trick ..

Thanks Mamoru. I should have tried it myself. It just did not occur to me.
I'm closing it.

Comment 4 Mamoru TASAKA 2014-01-13 13:24:24 UTC
While I am now waiting for upstream's reply, reading the code I think this behavoir is not intended. I will change xscreensaver's behavior so that xscreensaver accepts quick-off mode even when DPMS power-off timeout is set to 0.

Comment 5 Michal Minar 2014-01-13 13:28:54 UTC
That would definitely make sense. Big thanks!

Comment 6 Fedora Update System 2014-01-13 13:35:49 UTC
xscreensaver-5.26-2.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/xscreensaver-5.26-2.fc20

Comment 7 Fedora Update System 2014-01-13 13:36:07 UTC
xscreensaver-5.26-2.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/xscreensaver-5.26-2.fc19

Comment 8 Fedora Update System 2014-01-14 08:35:16 UTC
Package xscreensaver-5.26-2.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing xscreensaver-5.26-2.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-0722/xscreensaver-5.26-2.fc20
then log in and leave karma (feedback).

Comment 9 Fedora Update System 2014-01-15 06:11:05 UTC
xscreensaver-5.26-2.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2014-01-24 07:37:47 UTC
xscreensaver-5.26-2.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.