From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.4; Linux) KHTML/3.4.1 (like Gecko)
Description of problem:
I am running Fedora 4 on a laptop. Under klaptop, I have checked the option
to use a blank screensaver when running on battery. Under Desktop setup, I
have picked some random screensaver (it can be any particular screensaver) to
start after 5 minutes.
When I INITIALLY perform the above set-up, the screensaver behaves as it
should: the non-blank screensaver starts after 5 minutes (or when I click the
"lock session" applet) while the laptop is plugged in; when I unplug it, the
blank screensaver starts when it should.
However, these setting seem to be forgotten after I restart the cmputer and
log back into KDE. The non-blank screensaver gets turned on, regardless of
whether the computer is plugged in or not.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Konfigure klaptop to use blank screensaver when running on battery.
2. Pick a screensaver (.e.g. "clock"); set it to start after X minutes.
3. Plug in computer; wait X min or lock session --> "clock" screensaver starts
4. Unplug computer; wait X min or lock session --> "blank" screensaver starts
5. Reboot; log back into KDE
6. Repeat step 4. (alternatively, boot on battery)
Actual Results: "Clock" screensaver starts.
Expected Results: "Blank" screensaver should start.
Ideally I would like the screen to simply turn off when running on battery
(the blank screensaver simply projects a uniform color of the user's choice
while leaving the backlight on). However, there is no way, under klaptop, to
set different timings for screen power management based on power status.
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
Fedora Core 4 is no longer maintained.
Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.