Description of problem: monitor not put to sleep Version-Release number of selected component (if applicable): fedora 11 How reproducible: every time Steps to Reproduce: 1. monitor to go to sleep after 10 mins of inactivity 2. 3. Actual results: does not happen Expected results: monitor turns blank but stays alive Additional info:
I have the same problem since upgrading to f11. I am only just reading up on it. Apparently power management interaction with screen saver has changed - switching *off* screensaver (i.e. *not* to activate screensaver when idle) may help. I am going to try this now.
(In reply to comment #1) > I have the same problem since upgrading to f11. I am only just reading up on > it. Apparently power management interaction with screen saver has changed - > switching *off* screensaver (i.e. *not* to activate screensaver when idle) may > help. I am going to try this now. I tried this. Monitor goes to sleep. But screen is not locked on resume(does not ask for password)
well, my LCD doesn't blank any more... so f12 has a regression vs f11. (my LCD blanks and backlight switched off under f11).
I can confirm this bug under a fully updated (2009-07-06) Fedora 11. Screensaver set to blank and lock screen after 5 minutes, display set to sleep after 6 minutes. The display always stay active and never goes to sleep.
After installing the latest updates this problem was solved today (2009-11-09). I no longer see this bug.
(In reply to comment #5) > After installing the latest updates this problem was solved today (2009-11-09). > I no longer see this bug. Are you talking about upgrading to F12 or just the latest F11 updates? AFAIK it is still a problem here.
(In reply to comment #6) > Are you talking about upgrading to F12 or just the latest F11 updates? AFAIK it > is still a problem here. Just the F11 updates. I upgraded my i586 F10 box to F11 to test an unrelated bug. I did not see this problem on the i586 box. This got me wondering. So, Logged into my x86_64 box and executed yum clean all and yum update. After a reboot, I don't see this problem. Also, I checked the Activate screensaver when computer is idle option.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
upgrading to f12 (x86_64) and the LCD is put to sleep.. problem seems to have gone with f12. (RS690/ati driver, laptop LCD)
I can confirm this bug is solved on my end. Fully updated Fedora 12 as of 7 February 2010.
Problem is still present on my F12 installation.
Thank you for taking the time to report this bug. Updates to this package have been released since it was first reported. If you have time to update the package and re-test, please do so and report the results here. You can obtain the updated package by typing 'yum update' or using the graphical updater, Software Update.
(In reply to comment #12) > Thank you for taking the time to report this bug. Updates to this package have > been released since it was first reported. If you have time to update the > package and re-test, please do so and report the results here. You can obtain > the updated package by typing 'yum update' or using the graphical updater, > Software Update. have upgraded to Fedora 13 and the problem still persists..
lyengar, can you provide more informations on your setup, like the configuration of your desktop (GNOME, KDE, etc) and, for example, the configuration of Gnome Screensaver if you use it. Thanks!
I'm seeing this in F13 as well. I'm using the same gnome configuration I was in F11 and F12 (I've carried my home with me). I'm running GNOME, and don't have anything unusual in my setup (that I know of). Even if I disable the screensaver, the screens don't blank. % gconftool-2 -a /apps/gnome-screensaver lock_enabled = true idle_activation_enabled = true cycle_delay = 10 status_message_enabled = true mode = blank-only lock_dialog_theme = default user_switch_enabled = true idle_delay = 10 logout_delay = 120 power_management_delay = 30 embedded_keyboard_enabled = false logout_enabled = false embedded_keyboard_command = logout_command = themes = [] lock_delay = 0 % gconftool-2 -a /apps/gnome-power-manager/timeout sleep_display_ac = 300 sleep_computer_battery = 0 sleep_computer_ac = 0 sleep_display_battery = 600 sleep_computer_ups = 0 sleep_display_ups = 600 Let me know what else I can provide. Thanks.
(In reply to comment #14) > lyengar, can you provide more informations on your setup, like the > configuration of your desktop (GNOME, KDE, etc) and, for example, the > configuration of Gnome Screensaver if you use it. > > > Thanks! Using GNOME here. Just upgraded to 2.6.34.53 kernel % gconftool-2 -a /apps/gnome-screensaver lock_enabled = true idle_activation_enabled = true cycle_delay = 10 status_message_enabled = true mode = single lock_dialog_theme = default user_switch_enabled = true idle_delay = 10 logout_delay = 120 power_management_delay = 30 embedded_keyboard_enabled = false logout_enabled = false embedded_keyboard_command = logout_command = themes = [blank-only] lock_delay = 0 % gconftool-2 -a /apps/gnome-power-manager/timeout sleep_display_ac = 600 sleep_computer_ac = 0 sleep_computer_battery = 0 sleep_display_battery = 600 sleep_computer_ups = 0 sleep_display_ups = 600
Sorry kernel version is 2.6.34.6-54.fc13.i686 NOT 2.6.34.53 Thanks, Sundar
It seems I only see this bug when my laptop lid is closed and I'm using my two external monitors. If I open the lid (even though nothing is being displayed), the screens go to sleep. I looked at the source, how to fix this isn't totally obvious to me though.
It's very weird because I have mostly the same settings as you : $ gconftool-2 -a /apps/gnome-screensaver lock_enabled = true idle_activation_enabled = true cycle_delay = 10 status_message_enabled = true mode = blank-only lock_dialog_theme = default user_switch_enabled = true idle_delay = 10 logout_delay = 120 power_management_delay = 30 embedded_keyboard_enabled = false logout_enabled = false embedded_keyboard_command = logout_command = themes = [] lock_delay = 0 $ gconftool-2 -a /apps/gnome-power-manager/timeout sleep_display_ac = 300 sleep_computer_battery = 0 sleep_computer_ac = 0 sleep_display_battery = 300 sleep_computer_ups = 0 sleep_display_ups = 600 This is on my Thinkpad T61 and everything work well. Just to test, I revert my Dell Mini from Rawhide to F-13 and configure everything with the same settings. Now, I hit this bug sometimes (not always!)... I will try to figure out from where it can come.
(In reply to comment #19) > > This is on my Thinkpad T61 and everything work well. Just to test, I revert my > Dell Mini from Rawhide to F-13 and configure everything with the same settings. > Now, I hit this bug sometimes (not always!)... > > I will try to figure out from where it can come. Jean-Francois, Here is what I've notice the last few times. First time Login after reboot. Monitor NOT put to sleep. Subsequent Logins monitor put to sleep after desired interval. I hope this is the same experienced by you, when you say sometimes.. Thanks,
(In reply to comment #20) > Jean-Francois, > > Here is what I've notice the last few times. > > First time Login after reboot. Monitor NOT put to sleep. > > Subsequent Logins monitor put to sleep after desired interval. > > I hope this is the same experienced by you, when you say sometimes.. > > Thanks, When I say subsequent logins, I meant from the screensaver state. Thx.
Here is what came from testing in my setup : After the first GDM login, the screensaver (Blank screensaver) kicks in after 4 minutes (my configuration) and locks the screen. But the screen never power off, it stays at the blank screensaver. If I unlock my screensaver and return to my desktop, after another 4 minutes, the screensaver kicks in and locks the screen. After another minute (again, my configuration), the screen power off correctly. From after the second time, everything work as expected. So, the bug seems to be present only at the first cycle.
I am not sure this related. However, I would like to log it here. If I keep Filezilla-client open. the screensaver fails to turn on. Filezilla client version is 3.3.3-1.fc13.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I'm also seeing this issue in F13; this bug should be updated. Using "xset dpms force off" powers down the display properly, but gnome-power-manager will not. This issue has been ongoing since F11. I can provide any other necessary configuration information to help with diagnosing this issue... error@underground ~ $ gconftool-2 -a /apps/gnome-power-manager/timeout sleep_display_ac = 600 sleep_computer_battery = 0 sleep_computer_ac = 0 sleep_display_battery = 600 sleep_computer_ups = 0 sleep_display_ups = 60 error@underground ~ $ gconftool-2 -a /apps/gnome-screensaver lock_enabled = true idle_activation_enabled = true cycle_delay = 10 status_message_enabled = true mode = blank-only lock_dialog_theme = default user_switch_enabled = true idle_delay = 10 logout_delay = 120 power_management_delay = 30 embedded_keyboard_enabled = false logout_enabled = false embedded_keyboard_command = logout_command = themes = [] lock_delay = 0 error@underground ~ $
Just upgraded to F14. This issue continues to exist. In fact, It is NOT limited to the first Screensaver cycle as described in comment 22 anymore. It continues to subsequent power cycles.
Just upgraded to F14 and this issue isn't occurring for me anymore. I think it would be safe to call this one intermittent.
You need to either use F15 or F16 to get this fix. Please re-open if it still happens in newer releases. Thanks.