Bug 8174 - cannot adjust screen brightness in kde (battery monitor applet)
Summary: cannot adjust screen brightness in kde (battery monitor applet)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-21 18:54 CET by Drew Edwards
Modified: 2012-12-16 23:01 CET (History)
0 users

See Also:
Source RPM: kdebase4-workspace-4.9.3-1.mga3.src.rpm
CVE:
Status comment:


Attachments

Description Drew Edwards 2012-11-21 18:54:19 CET
Description of problem:

Up-to-date Cauldron installation on lenovo x120e laptop.  Cannot adjust screen brightness via battery monitor applet.  I get a screen display that shows the brightness going up and down but the brightness does not actually change.  In xfce I can adjust screen brightness via an xfce app so this seems kde-specific.

Version-Release number of selected component (if applicable):

Version     : 4.9.3
Release     : 1.mga3


How reproducible:

Click on battery monitor applet, move slider for screen brightness. Brightness does not change.

Steps to Reproduce:
1.
2.
3.
Comment 1 Drew Edwards 2012-11-22 07:55:23 CET
More:  I ran xfdrake again and chose the proprietary driver (fglrx) and after rebooting the screen brightness adjustment in kde worked fine.  I ran xfdrake again, declined the proprietary driver, and after rebooting the screen brightness no longer works.

To summarize: it works with fglrx but it doesn't work with radeon driver.  Brightness adjustment in xfce via panel app works fine with either driver.
Comment 2 Drew Edwards 2012-12-16 23:01:38 CET
This is no longer a problem, do not know when it was fixed as I had been running proprietary driver.  Discovered the fix by accident when some upgrades in cauldron caused the system to default back to radeon driver.

Resolved.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


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