Bug 722745 - Screen brightness settings does not have any effect on iMac 12.2 27inch [NEEDINFO]
Summary: Screen brightness settings does not have any effect on iMac 12.2 27inch
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: backlight
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-17 09:31 UTC by Andreas Tunek
Modified: 2014-03-10 14:39 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 773589 (view as bug list)
Environment:
Last Closed: 2014-03-10 14:39:51 UTC
Type: ---
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)

Description Andreas Tunek 2011-07-17 09:31:38 UTC
When you adjust the screen brightness, either in gnome or using the brightness
keys on the keyboard, the sliders change but there is no difference on the
actual brightness of the screen

HW: 2011 27 inch iMac, smolt:
http://www.smolts.org/client/show/pub_d9693c43-4ee8-4a8c-82a8-5332c6481f4d

I am using Refit to boot into Fedora.

Comment 1 Andreas Tunek 2011-08-05 17:41:12 UTC
Still happens in 2.6.40....

Comment 2 Josh Boyer 2012-06-06 16:07:44 UTC
There was a lot of work put into making F17 more usable on Apple hardware.  Have you tried installing F17 to see if it improves things?

Comment 3 Basil Mohamed Gohar 2012-06-18 17:59:30 UTC
I've installed Fedora 17 on a 27-inch iMac and the brightness is not adjustable from the Gnome 3 Brightness and Lock settings menu at all.

Comment 4 Andreas Tunek 2012-09-13 18:58:21 UTC
Still happens in RC3, but it seems to remember the last screen brightness set by MacOSX now which makes the computer much more useable.

Comment 5 Andreas Tunek 2012-11-13 12:14:03 UTC
Same problems in Beta TC8.

Comment 6 Josh Boyer 2013-04-12 17:03:53 UTC
Is this still happening with 3.8.x?

Comment 7 Andreas Tunek 2013-05-25 20:29:43 UTC
Tested on beta.

Comment 8 Josh Boyer 2013-09-18 20:32:46 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.11.1-200.fc19.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 9 Andreas Tunek 2013-09-25 13:43:50 UTC
Same results on F20 Alpha.

Comment 10 Mike Ruckman 2013-10-25 14:44:09 UTC
I have the same issue on a Lenovo W530 running F20 Beta TC5.

Comment 11 Andreas Tunek 2013-10-26 10:13:14 UTC
You should probably open a new since since the HW is different.

Comment 12 Mike Ruckman 2013-11-03 06:33:06 UTC
Submitted bug 1026054

Comment 13 Justin M. Forbes 2014-01-03 22:08:26 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.12.6-200.fc19.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20.

If you experience different issues, please open a new bug report for those.

Comment 14 Justin M. Forbes 2014-03-10 14:39:51 UTC
*********** MASS BUG UPDATE **************

This bug has been in a needinfo state for more than 1 month and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 19, please feel free to reopen the bug and provide the additional information requested.


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