[Intrepid] On DELL Inspiron 9400 some Fn+keys don't work (instead creates a tight loop of KeyPress/KeyRelease events in xev)

[wolfie2x]

Fn+Volume Up(PgUp)/Volume Down(PgDn) works.

Fn+Wifi(F2) - doesn't work. No OSD; LED doesn't light; no entries in syslog.
xev output shows a tight loop of KeyPress/KeyRelease events.
If Fn+Wifi is pressed after clicking on the desktop, top shows nautilus taking about 10% cpu. clicking on some window stops it.

Fn+battery(F3) - doesn't work; No OSD.
same tight loop of xev output as above,

Fn+Brightness Up(Up Arrow)/Brightness Down (Down Arrow) - partially works but buggy.
When keys are pressed even only once, OSD appears and the brightness increases/decreases continuously (along with the indicator bar), until it's max/min (like the keys are stuck). Afterwards the desktop simply doesn't work properly; windows can't be moved; console doesn't get the focus when clicked; keyboard doesn't work. Logging out and back in again brings things back to normal.
no tight loop shown in xev (maybe because the OSD appears).
sudo /usr/bin/acpi_fakekey 224 (or 225) works properly.

possibly related bug reports:
https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/272292
https://bugs.launchpad.net/ubuntu/+bug/281421

xev output files attached.

All of these worked fine on Hardy.

Ubuntu 8.10 Intrepid
Linux wolfie-laptop 2.6.27-7-generic #1 SMP Wed Oct 22 00:29:18 UTC 2008 i686 GNU/Linux
system is fully up-to-date as of 23-Oct-08

wolfie:~$ lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10

wolfie:~$ sudo dmidecode -s system-manufacturer
Dell Inc.
wolfie:~$ sudo dmidecode -s system-product-name
MP061
wolfie:~$ sudo dmidecode -s system-version
Not Specified

[wolfie2x (wolfie2x)]

problem still persists after todays updates. (26-Oct-08)

[ShackJack (shackjack)]

I can verify a similar problem on a Dell Inspiron e1505:

Using the Fn Brightness controls (Fn Arrow Up/Down) causes X not to register keystrokes in programs, and ceases OSD of volume/brightness events (OSD for battery WiFi et al never worked - not sure it's supposed to?). Also submenus and right-clicks cease to work.

Toggling to Terminal and back to GUI (Ctrl-Alt F1/F7) restores keyboard/clicking functionality.

[ShackJack (shackjack)]

Just wanted to add that my Intrepid install was an RC1 upgrade from Hardy (vs. a fresh install). I have the nagging suspicion that a fresh install would miraculously correct the problem, but will leave as is in case you need any additional data...

[wolfie2x (wolfie2x)]

after todays updates (1-Nov-08) the screen brightness OSD is gone, but the brightness does change. The desktop doesn't get screwed anymore like it used to. However now the xev output shows the tight loop for screen brightness up/down also.
Once in a tight loop, brining up the volume OSD stops the loop.

[ShackJack (shackjack)]

My system (Dell e1505) still loses X keyboard input (except for CTRL-ALT-etc...) after adjusting brightness with Fn-Brightness keys...

(Though the brightness panel ap makes a nice workaround for now)

[klerfayt (klerfayt-deactivatedaccount)]

I've same problem.
Fn+VolumeUp or Fn+VolumeDown acts crazy turning volume all the way down or up, Fn+Mute doesn't work unless I press Ctrl-Alt-F1 and Ctrl-Alt-F7.
Discovered that pressing Ctrl-Alt-F1 and Ctrl-Alt-F7 makes desktop usable again - can click on menus, drag windows and type (Fn volume keys disable these activities).
I copied over my xorg.conf with the one I use in kubuntu 7.10, but no change still same problems.
Also I cannot use PgUp or PgDn keys in warsow console (it's a game), neither do arrow keys up and down work (this is useful for repeating commands).
I've tried to change keyboard layout to "us" in gnome applet, doesn't change anything.

ubuntu intrepid ibex 8.10; laptop mitac 8050qda

[Saivann Carignan (oxmosys)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 285323, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.