Bug 721362 - screen does not dim (powersave profile) when on battery ubtil profile toggled
Summary: screen does not dim (powersave profile) when on battery ubtil profile toggled
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase-workspace
Version: 15
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-14 11:39 UTC by gene c
Modified: 2011-11-17 12:53 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-17 12:31:10 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description gene c 2011-07-14 11:39:59 UTC 
Description of problem: When on battery - the screen does not dim unless I toggle the power profile to performance and back to powersave by hand


Version-Release number of selected component (if applicable): kdebase-4.6.3-1.fc15.x86_64



How reproducible: alwasys


Steps to Reproduce:
1. Unplug laptop
2. click on power applet - it seems to be in powersave - but screen has not dimmed - using power applet change to performance - and then back to powersave - screen dims
3.not sure if sleeping and waking laptop (lid close) is involved
  
Actual results: screen remains at 100%


Expected results: screen should dim to powersave level




Additional info:
Comment 1 Lukáš Tinkl 2011-11-17 12:31:10 UTC 
Please try to reproduce with the latest version and reopen if the problem still persists.
Comment 2 gene c 2011-11-17 12:43:30 UTC 
Thanks - will do - to be clear - what is the version in which it is fixed ?
Comment 3 Lukáš Tinkl 2011-11-17 12:46:44 UTC 
Update to the latest kdebase-workspace and see, I remember fixing this some time ago
Comment 4 gene c 2011-11-17 12:53:38 UTC 
Ok - tested using kdebase-workspace-4.6.5-5.fc15.x86_64

Indeed the problem seems to be gone. 

Thanks!

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