Bad hotkeys on Laptop Asus F3

Bug #211922 reported by Francisco T.
2
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Daniel Hahler

Bug Description

Some special keys doesn't work correctly in kubuntu.

My laptop is a:
ASUSTeK Computer Inc.
F3F
1.0

Now testing on Kubuntu intrepid beta:
Linux portatil 2.6.27-7-generic #1 SMP Fri Oct 17 22:24:21 UTC 2008 i686 GNU/Linux

From hardy, asus-laptop detects my laptop correctly:
[ 41.380148] asus-laptop: Asus Laptop Support version 0.42
[ 41.380479] asus-laptop: F3F model detected

I will explain each key:

FIVE SPECIAL KEYS:
- hotkey ATKD 00000051 0000000d: Webbrowser worked but Bug #217504 ?

- hotkey ATKD 0000008a 00000007: Nothing happens.

- hotkey ATKD 0000006b 00000010: Worked? Bug #217504 ? Touchpad enable/disable. (Fix: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/199682/comments/6)

- hotkey ATKD 0000005c 00000009: Didn't work? Bug #217504 ?. Executed wrong action "/etc/acpi/lockbtn.sh". Better to change CPU policy (Wish: Bug #268290) or maps to XF86F2x?

- hotkey ATKD 00000095 00000008: Media button. Work with fix in attachment (comment 8)

WIFI SLIDE BUTTON:
- hotkey ATKD 00000081 00000002: Wifi off. Work but nothing happens with the wifi-led.
- hotkey ATKD 00000080 00000003: Wifi on. (idem)

FN KEYS:
FN+F1 Suspend: Work, but wifi-scan is broken after wakeup.
FN+F2 Wifi: Work. Led turn on/off and acpid execute "/etc/acpi/asus-wireless.sh" "hotkey ATKD 0000005d 00000009"
FN+F3 Mail: Work.
FN+F4 Webrowser: Work? Bug #217504 ?
FN+F5 Bright down: Work.
FN+F6 Bright up: Work.
FN+F7 On/off LCD: Work.
FN+F8 LCD/TV: Not test
FN+F9 Touchpad: Acpi: "hotkey ATKD 0000006b 00000013" (Fix: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/199682/comments/6)
FN+F10 Sound on/off: Work, 160 XF86AudioMute.
FN+F11 Audio down: Work,174 XF86AudioLowerVolume
FN+F12 Audio up: Work, 176 XF86AudioRaiseVolume

FN+Up Stop: Work, 164 XF86AudioStop (Regression in kubuntu 8.10 beta: Bug #284577)
FN+Down Play/pause: Work, 162 XF86AudioPause
FN+Left Previous; Work, 144 XF86AudioPrev
FN+Right Next: Work, 153 XF86AudioNext

FN+Space CPU Policy, Doesn't work. Same as special key. "hotkey ATKD 0000005c 0000000b"

Xev detect only:
236 XF86Mail
160 XF86AudioMute
174 XF86AudioLowerVolume
176 XF86AudioRaiseVolume
164 XF86AudioStop
144 XF86AudioPrev
162 XF86AudioPause
153 XF86AudioNext

Revision history for this message
Francisco T. (leviatan1) wrote :
Revision history for this message
Francisco T. (leviatan1) wrote :
Revision history for this message
Francisco T. (leviatan1) wrote :
Revision history for this message
Francisco T. (leviatan1) wrote :
Revision history for this message
Francisco T. (leviatan1) wrote :
Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Daniel Hahler (blueyed) wrote :

Thank you for your bug report and the additional info you've provided.
I'm marking it as duplicate of bug 217504, which is about acpi_fakekey failing/being ignored, which gets called from the acpi-support scripts.

Changed in linux:
assignee: ubuntu-kernel-team → blueyed
status: Triaged → Invalid
Revision history for this message
Francisco T. (leviatan1) wrote :

Maybe some keys doesn't work in hardy and intrepid beta because bug #217504. For example web button.

I'm waiting the fix relaesed to continue checking some special keys.

Revision history for this message
Francisco T. (leviatan1) wrote :

Add /etc/acpi/events/asus-media

and now, with the media key I get:
KeyRelease event, serial 34, synthetic NO, window 0x2e00001,
    root 0x7b, subw 0x0, time 3187468, (320,-102), root:(325,456),
    state 0x0, keycode 234 (keysym 0x1008ff32, XF86AudioMedia), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

I can already assign the media key to amarok, for example.

Francisco T. (leviatan1)
description: updated
Francisco T. (leviatan1)
description: updated
description: updated
Francisco T. (leviatan1)
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.