Bug 461539 - screen goes black even with setting saying "on all the time"
screen goes black even with setting saying "on all the time"
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: gnome-power-manager (Show other bugs)
rawhide
x86_64 Linux
medium Severity low
: ---
: ---
Assigned To: David Zeuthen
Fedora Extras Quality Assurance
:
Depends On:
Blocks: F10DesktopTarget
  Show dependency treegraph
 
Reported: 2008-09-08 18:01 EDT by Tom Horsley
Modified: 2008-10-03 14:57 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-10-03 14:57:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tom Horsley 2008-09-08 18:01:59 EDT
Description of problem:

In System > Preferences > Look & Feel > Screensaver (a gnome session),
I have idle time set to 2 hours,
I have unchecked Activate Screensaver and Lock screen
In Power Management I have
Put computer to sleep set to never
Put display to sleep set to never

Nevertheless, I start a long yum update, come back in about 15 minutes, and
find the screen has blanked and I have to wiggle the mouse for a minute
or so to get a picture back and see how far the update has gotten.

Version-Release number of selected component (if applicable):
gnome-power-manager-2.23.91-1.fc10.x86_64

How reproducible:
every time I leave it alone for a while

Steps to Reproduce:
1.see above
2.
3.
  
Actual results:
blank screen

Expected results:
leave display active

Additional info:
Comment 1 Tom Horsley 2008-10-03 12:50:51 EDT
This seems to be fixed in latest f10 beta. I reinstalled from scratch,
reset my screensaver settings once again to always on, and let
packagekit download the gazillion updates already out there for
rawhide, and when I came back much later, the screen was still visible.
Comment 2 Matthias Clasen 2008-10-03 14:57:14 EDT
Thanks, I'll consider it fixed then.

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