You are not logged in.
Pages: 1
T400s, it works well always...
With recent update, mute keys don't work at all.
Offline
Volume events are now caught by ACPI but not handled appropriately. Confirm this by taking a look at /var/log/messages.log as you press the volume up/down/mute buttons.
If ACPI indeed reports no action is defined, you can add these cases to your /etc/acpi/handler.sh as a quick fix.
Or create a separate ACPI sound handler for this as is shown in this wiki https://wiki.archlinux.org/index.php/Talk:MacBookPro
button/volumeup)
case "$2" in
VOLUP)
logger 'Volume raised'
amixer -c 0 set Master 1+ unmute
;;
*)
logger "ACPI action undefined: $2"
;;
esac
;;
button/mute)
case "$2" in
MUTE)
if amixer -c 0 get Master | grep -q off
then
logger 'Audio unmuted'
amixer -c 0 set Master unmute
amixer -c 0 set PCM unmute
else
logger 'Audio muted'
amixer -c 0 set Master mute
fi
;;
*)
logger "ACPI action undefined: $2"
;;
esac
;;
button/volumedown)
case "$2" in
VOLDN)
logger 'Volume lowered'
amixer -c 0 set Master 1- unmute
;;
*)
logger "ACPI action undefined: $2"
;;
esac
;;Offline
Having this issue too with my X220. Quick question, I use Gnome, and I read that ACPID and Gnome don't necessarily mix as Gnome does its own ACPI handling. Is this still the case, or is there a Gnome specific solution I should look at?
Like the OP, the volume button has always worked out of the box for me without any tweaking, and xev correctly identifies the buttons when they are pressed.
Offline
The same issue here, T400 as well. Not only volume mute, but all Fn+Fx keys are not working either. I unawared of this until it embrassed me a little bit when I tried to do some projections after the update, and that was in front of several CS professors...
Archlinux x86_64 on Thinkpad T400
Intel X4500MHD / ATI HD3470 Graphics, 2G RAM, 160G HD
Offline
Another option is xbindkeys. I had a lot of trouble using ACPI for volume control buttons; muting in particular did not want to work with it. xbindkeys didn't seem to have a problem with it. I did a little research and I don't think it should conflict with Gnome at all. It looks like others have recommended the same solution for this problem on other websites as well.
Offline
I've got Thinkpad T400 with all recent updates. My mute button works perfectly fine but I handle it via VolumeIcon. Works great for me in openbox.
Offline
I got the same problem too
Oct 23 16:15:04 SuperBo-PC logger: ACPI group/action undefined: button/volumeup / VOLUP
Oct 23 16:15:05 SuperBo-PC logger: ACPI group/action undefined: button/volumedown / VOLDN
Oct 23 16:15:06 SuperBo-PC logger: ACPI group/action undefined: cd/play / CDPLAY
Oct 23 16:15:06 SuperBo-PC logger: ACPI group/action undefined: cd/prev / CDPREV
Oct 23 16:15:07 SuperBo-PC logger: ACPI group/action undefined: cd/next / CDNEXT
Oct 23 16:15:55 SuperBo-PC logger: ACPI group/action undefined: cd/next / CDNEXT
Anyone have suggestion to fix it?
My toogle touchpad key dont work anymore, how to fix?
Last edited by SuperBo (2012-10-23 09:29:26)
Offline
I thought I was the only one having this issue, thank god I'm not.
Acer Aspire 5377z
2012-10-23T08:33:46-05:00 Prometheus logger: ACPI group/action undefined: button/volumeup / VOLUP
2012-10-23T08:33:47-05:00 Prometheus logger: ACPI group/action undefined: button/volumedown / VOLDN
2012-10-23T08:33:49-05:00 Prometheus logger: ACPI group/action undefined: cd/play / CDPLAY
2012-10-23T08:33:49-05:00 Prometheus logger: ACPI group/action undefined: cd/stop / CDSTOP
2012-10-23T08:33:49-05:00 Prometheus logger: ACPI group/action undefined: cd/prev / CDPREV
2012-10-23T08:33:50-05:00 Prometheus logger: ACPI group/action undefined: cd/next / CDNEXT
Offline
Having this issue too with my X220. Quick question, I use Gnome, and I read that ACPID and Gnome don't necessarily mix as Gnome does its own ACPI handling. Is this still the case, or is there a Gnome specific solution I should look at?
Like the OP, the volume button has always worked out of the box for me without any tweaking, and xev correctly identifies the buttons when they are pressed.
I have no idea. I'm using GNOME as well, and the solution I posted above works for me. Although I'm very content with the solution, I still consider the behaviour it fixes as a bug and I hope it gets a proper solution.
Offline
Since ran into other input issues, such as the PrtScr button not working. My volume keys resumed operation after performing the downgrades described in this article.
Offline
Same problem X220:
Logs from journalctl:
ACPI group/action undefined: button/mute / MUTE
ACPI group/action undefined: button/volumedown / VOLDN
ACPI group/action undefined: button/volumeup / VOLUP
ACPI group/action undefined: video/brightnessup / BRTUP
ACPI group/action undefined: video/brightnessdown / BRTDN
Although, I can still use Fn + PgUp/PgDn to adjust the brightness. But the brightness state applet doesn't work.
Also, the mute button actually works, but no appearance.
Offline
Pages: 1