https://bugzilla.novell.com/show_bug.cgi?id=386541 User ma@sernet.de added comment https://bugzilla.novell.com/show_bug.cgi?id=386541#c2 Michael Adam <ma@sernet.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ma@sernet.de --- Comment #2 from Michael Adam <ma@sernet.de> 2008-05-06 02:52:05 MST --- Same problem here. Not sure if it is a gnome or an X problem, though. I am using gnome from factory repos with the x64_64 architecture on an x61s. Problem description: The brightness keys (Fn+Home/End) do not work properly. An OSD pops up but behaves strangely: As the progress bar proceeds, the brightness of the display stays the same, but once the max is reached, pressing Fn+Home repeatedly starts an oscillating behaviour: The OSD bar jumps between 50% and 100% and so does the brightness. Similar phenomenon for Fn+End - bar oscillating between 0% and 50%. The gnome brightness panel applet is working correctly though! Previously, in 10.3, this oscillating behaviour did not happen. But the bar ran from 0% to 100% twice - starting over at 0% once 100% was reached the first time. This seems to be related to the fact that the thinkpad acpi seems to have 15 brightness steps instead of 7. (Previously, in 10.3, the brightness applet only provided 7 steps, now this seems to have been fixed: the brightness applet provides all 15 steps.) nirvana:~ # cat /sys/class/backlight/acpi_video1/brightness 15 nirvana:~ here is something strange: nirvana:~ # cat /proc/acpi/video/VID1/LCD0/brightness levels: 100 100 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 100 current: 100 nirvana:~ # the brightness apple walks all steps from 20 (0) to 100 (15). the Fn-Keys oscillate between 20(0) and 55(7) at the low end and between 55(0) and 100(15) at the high end. In the middle they stick at 55(7). Cheers - Michael -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=386541 User ma@sernet.de added comment https://bugzilla.novell.com/show_bug.cgi?id=386541#c4 --- Comment #4 from Michael Adam <ma@sernet.de> 2008-05-06 02:55:44 MST --- Created an attachment (id=212568) --> (https://bugzilla.novell.com/attachment.cgi?id=212568) /etc/X11/xorg.conf (sax-generated) my xorg.conf -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=386541 User ma@sernet.de added comment https://bugzilla.novell.com/show_bug.cgi?id=386541#c6 --- Comment #6 from Michael Adam <ma@sernet.de> 2008-05-06 03:24:42 MST --- Sure. That is why I did not tag the "provides the needed info". My info might be useful anyways... :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=386541 User ma@sernet.de added comment https://bugzilla.novell.com/show_bug.cgi?id=386541#c8 --- Comment #8 from Michael Adam <ma@sernet.de> 2008-05-06 07:36:28 MST --- There is a possibly related bug from 10.3: Bug #308264. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=386541 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=386541#c10 Thomas Renninger <trenn@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |DUPLICATE --- Comment #10 from Thomas Renninger <trenn@novell.com> 2008-05-06 10:48:14 MST --- *** This bug has been marked as a duplicate of bug 308264 *** https://bugzilla.novell.com/show_bug.cgi?id=308264 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.