Red Hat Bugzilla – Bug 565757
after a day or so powerdevil is unable to manage screen powersaving
Last modified: 2010-02-27 21:18:41 EST
Description of problem:
n my netbook I have my screensaver to kick in 14 minutes require a password in
I set powerdevil to manage screen powersaving
in Profiles I set (Performance and Powersaving) the Screen tab to:
Suspend after 16 minutes
Power off after 17 minutes
at first powerdevil works correctly suspending and powering off the screen
I go back to the computer type the password but
after few times of:
-the computer idle for 14 minutes
-type the password
(sometimes after 24 hours of using the computer in the above cycle) the screen don't suspend nor
power off instead the screensaver remains
so when I notice which the screensaver remains, I switch profiles to
powersaving and going back to perfomance, and powerdevil is able to manage the
screen again for a few times more, but some time after the screensaver remains
so my workaround is when I will know which I leave the machine for a while,
before I leaveI switch the profiles to powersaving and back to performance to
be sure which powerdevil will manage the screen powersaving
Version-Release number of selected component (if applicable):
always , only give a day to be sure to happes
Steps to Reproduce:
1.set the powerdevil profiles as above in the description
2. wait to the computer be idle and poweroff the screen
4. work with the computer some time
5. go to step 2.
after a while the screen saver will remain and the screen will not power off
power off the screen always which the computer is idle for more of 17 minutes
I filled a bug in https://bugs.kde.org/show_bug.cgi?id=226758 too
Thanks for taking to time to report this upstream. We will monitor the upstream report for a resolution.
Steven M. Parrish
KDE & Packagekit Triager
Fedora Bugzappers volunteer triage team
Please don't close the regressions on our kde-4.4 (or qt46) tracker as UPSTREAM, we'd really like to track those particular bugs in Fedora.
This isn't necessarily a regression nor reproducible (yet).
I think I'm seeing this as well.
Thank you for taking the time to report this issue to us. As we decided this issue is not a blocker for our 4.4 update and as this bug is already reported upstream, we are going to close it as UPSTREAM.
We will continue to track the issue in the centralized upstream bug tracker,
and will review any bug fixes that become available for consideration in future
Thank you for the bug report.