Up until rebooting this morning, I used to be able to use the Fn+<button> combinations just fine with rawhide. Now, FN+Home, FN+End don't adjust the backlight level. This is pretty annoying, because I also can't dim the backlight through any of the gnome-* apps either. What changed and how the hell to I get rid of it?
josh
On Sun, 21 Oct 2007 14:40:08 -0500 Josh Boyer jwboyer@jdub.homelinux.org wrote:
Up until rebooting this morning, I used to be able to use the Fn+<button> combinations just fine with rawhide. Now, FN+Home, FN+End don't adjust the backlight level. This is pretty annoying, because I also can't dim the backlight through any of the gnome-* apps either. What changed and how the hell to I get rid of it?
Oh, and my FN+F5 combo hasn't worked for the bluetooth switch in a while. Grr.
josh
On Sun, 2007-10-21 at 15:48 -0500, Josh Boyer wrote:
On Sun, 21 Oct 2007 14:40:08 -0500 Josh Boyer jwboyer@jdub.homelinux.org wrote:
Up until rebooting this morning, I used to be able to use the Fn+<button> combinations just fine with rawhide. Now, FN+Home, FN+End don't adjust the backlight level. This is pretty annoying, because I also can't dim the backlight through any of the gnome-* apps either. What changed and how the hell to I get rid of it?
Oh, and my FN+F5 combo hasn't worked for the bluetooth switch in a while. Grr.
Read the list more carefully, it's been pointed out it's a kernel bug, although no one posted a bug link.
On Mon, 22 Oct 2007 01:44:04 +0100 Bastien Nocera bnocera@redhat.com wrote:
On Sun, 2007-10-21 at 15:48 -0500, Josh Boyer wrote:
On Sun, 21 Oct 2007 14:40:08 -0500 Josh Boyer jwboyer@jdub.homelinux.org wrote:
Up until rebooting this morning, I used to be able to use the Fn+<button> combinations just fine with rawhide. Now, FN+Home, FN+End don't adjust the backlight level. This is pretty annoying, because I also can't dim the backlight through any of the gnome-* apps either. What changed and how the hell to I get rid of it?
Oh, and my FN+F5 combo hasn't worked for the bluetooth switch in a while. Grr.
Read the list more carefully, it's been pointed out it's a kernel bug, although no one posted a bug link.
I know that. I was pretending I didn't. Forgive my frustration.
josh