Drop Asus volume control from acpi-support

Bug #286339 reported by Reza Mohammadi
6
Affects Status Importance Assigned to Milestone
acpi-support (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: hal-info

$ lsb_release -rd
Description: Ubuntu 8.04.1
Release: 8.04

Computer Model: Sony VAIO VGN-S660

With hal-info [20080317+git20080318-1ubuntu4] I hadn't this problem, but the new version [20081001-0ubuntu1~hardy1] has made some problems:

When I press the mute key combination (Fn+F2) the function is triggered twice, so for an instant the audio goes mute and then it come back. Also the volume control key combinations (Fn+F3 and Fn+F4) change the volume 2 steps at once.

Here is the output of xev when I press the mute key combination on my system:

KeyPress event, serial 29, synthetic NO, window 0x3c00001,
    root 0x1a6, subw 0x0, time 6926641, (252,-49), root:(257,0),
    state 0x0, keycode 160 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 29, synthetic NO, window 0x3c00001,
    root 0x1a6, subw 0x0, time 6926641, (252,-49), root:(257,0),
    state 0x0, keycode 160 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 29, synthetic NO, window 0x3c00001,
    root 0x1a6, subw 0x0, time 6926714, (252,-49), root:(257,0),
    state 0x0, keycode 160 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 29, synthetic NO, window 0x3c00001,
    root 0x1a6, subw 0x0, time 6926714, (252,-49), root:(257,0),
    state 0x0, keycode 160 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

But when I press one of the brightness control key combinations, it acts normally (not displayed correctly by the gnome the-thing-which-shows-how-bright-is-your-monitor, but its not a problem; before the update, there was not any gnome the-thing... :P). There are just a pair of KeyPress-KeyRelease for each of those combinations.

Revision history for this message
mestre.adamastor (mestre.adamastor) wrote :

I'm using a Vaio SZ2HP and I have exactly the same problem (though I don't really know what triggered it.
In my case, the problem was solved by following the instructions in:
http://www.pihhan.info/sony/sony-hotkeys.html

In particular, all I did was:

1) lshal | grep 'system.hardware.product'
2) edit /usr/share/hal/fdi/information/10freedesktop/30-keymap-module-sony-laptop.fdi
3) add the string to the list of models (In my case it was 'VGN-SZ2HP_B')
4) sudo /etc/init.d/hal restart

and it was working.
The attachment contains the fix for my problem.

Revision history for this message
Martin Pitt (pitti) wrote :

ugrandamastor, I committed your fix upstream.

Revision history for this message
Martin Pitt (pitti) wrote :

Reza, can you confirm that your keys work again if you downgrade to the previous version?

cd /tmp/
wget http://archive.ubuntu.com/ubuntu/pool/main/h/hal-info/hal-info_20080317+git20080318-1ubuntu4_all.deb
sudo dpkg -i hal-info_20080317+git20080318-1ubuntu4_all.deb

Please do this, reboot, and then do "lshal > /tmp/hal-old.txt"; attach /tmp/hal-old.txt here.

Changed in hal-info:
status: New → Incomplete
assignee: nobody → pitti
Revision history for this message
Reza Mohammadi (remohammadi) wrote :

I've downgraded and restarted and the keys work, and the hal-old.txt is attached.

Details:
I have set keyboard shortcuts for volume management in my gnome preferences:
  Volume Mute: 0xa0
  Volume down: 0xae
  Volume up: 0xb0
As I mentioned before, the brightness control keys work, but gnome doesn't show the gauge when the brightness of the monitor is changing.
(When my laptop had its battery, the gauge used to show itself every time the laptop was switched between battery and AC power; but the brightness didn't used to change based on the power supply status :D
I can't verify it now :( )

Revision history for this message
Martin Pitt (pitti) wrote :

OK, thanks. Please upgrade to the latest intrepid-proposed hal-info again, download this file, and install it with

  sudo cp 30-keymap-module-sony-laptop.fdi /usr/share/hal/fdi/information/10freedesktop/

Then please reboot. Does that fix the keymap for you?

Revision history for this message
Martin Pitt (pitti) wrote :
Revision history for this message
Reza Mohammadi (remohammadi) wrote :

No, It didn't.
I was trying to fix it by editing that file. The original file should be ok! I finally downgraded to that old package :P

Martin Pitt (pitti)
Changed in hal-info:
status: Incomplete → New
Revision history for this message
Francesco Marella (francesco-marella) wrote :

$ lsb_release -a
Distributor ID: Ubuntu
Description: Ubuntu karmic (development branch)
Release: 9.10
Codename: karmic

my laptop: Asus A6jc, removing acpi-support fix this issue

Revision history for this message
Martin Pitt (pitti) wrote :

Seems acpi-support must stop handling the volume control buttons, they are properly converted to key events now.

summary: - After hal-info update, the volume control buttons send every event twice
+ Drop Asus volume control from acpi-support
affects: hal-info (Ubuntu) → acpi-support (Ubuntu)
Changed in acpi-support (Ubuntu):
assignee: Martin Pitt (pitti) → nobody
status: New → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package acpi-support - 0.123

---------------
acpi-support (0.123) karmic; urgency=low

  * events/asus-volume-{up,down,mute}: drop, these are handled in the kernel
    input layer now. LP: #286339.

 -- Steve Langasek <email address hidden> Sun, 17 May 2009 19:10:16 -0700

Changed in acpi-support (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Eric Drechsel (ericdrex) wrote :

I'm experiencing the same behavior (each event registered twice) with a panasonic laptop, due to the new panasonic_laptop kernel module. Issue is resolved similarly for panasonic laptops by removing /etc/acpi/events/panasonic-[mute,volume-down,volume-up]

Note that the kernel module isn't automatically loaded, at least for me, so that should be resolved before applying this fix.

summary: - Drop Asus volume control from acpi-support
+ Drop Asus/panasonic volume control from acpi-support
Changed in acpi-support (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Steve Langasek (vorlon) wrote :

Please open a separate bug report for this issue.

summary: - Drop Asus/panasonic volume control from acpi-support
+ Drop Asus volume control from acpi-support
Changed in acpi-support (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Steve Langasek (vorlon) wrote :

Note that the panasonic-laptop module declares the following aliases in karmic:

alias: acpi*:MAT0019:*
alias: acpi*:MAT0018:*
alias: acpi*:MAT0013:*
alias: acpi*:MAT0012:*

If these don't match your laptop, you should file a report against the 'linux' package with the output of ls /sys/bus/acpi/devices/ on your system.

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.