Bug 505782

Summary:	gnome-power-manager incorrectly adjusts display backlight levels on MacBook Pro 4,1
Product:	[Fedora] Fedora	Reporter:	Stewart Adam <s.adam>
Component:	gnome-power-manager	Assignee:	Richard Hughes <richard>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	12	CC:	richard
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-12-05 06:51:20 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Stewart Adam 2009-06-13 19:41:54 UTC

Description of problem:
Although the mbp_nvidia_bl module is loaded and works correctly, attempting to change the display brightness will always result in the backlight being set to the lowest level (0). This results in the display being turned on but with no backlight, rendering the screen unreadable.

Reloading the mbp_nvidia_bl module is a temporary workaround as it resets the display brightness to the maximum value (15) when it is loaded.

Version-Release number of selected component (if applicable):
gnome-power-manager-2.26.1-3.fc11.x86_64

hal-0.5.12-26.20090226git.fc11.x86_64
kernel-2.6.29.4-167.fc11.x86_6


How reproducible:
Always

Steps to Reproduce:
1. Start Fedora and login
2. Press the backlight up/down (F1/F2) keys.

Actual results:
Display is set to minimum brightness (display is on but backlight is turned off)

Expected results:
The display brightness adjusts according to the key pressed

Additional info:
This can also be trigged by connecting/removing the power cord.

The mbp_nvidia_bl module itself is working correctly, as adjusting the backlight via "echo X > /sys/devices/virtual/backlight/mbp_backlight/brightness" works.

Comment 1 Bug Zapper 2009-11-16 10:11:31 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2010-11-04 11:07:15 UTC

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2010-12-05 06:51:20 UTC

Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.