[Pkg-acpi-devel] Bug#738611: acpid: Mic mute button not recognized on Thinkpad again

Lingzhu Xiang xianglingzhu at gmail.com
Wed Feb 12 04:29:26 UTC 2014

On Tue, Feb 11, 2014 at 10:44 PM, Ted Felix <ted at tedfelix.com> wrote:
> On 02/11/2014 10:21 PM, Lingzhu Xiang wrote:
>> I would suggest translating F20 backto MICMUTE.
>   The problem with this is that one day in the future, someone will need F20
> for something else.  And we'll have to either break those who use it for
> micmute, or we cannot meet this new requirement.

If now acpid users change rules to handle button/f20 for mic muting,
and in the future udev maps something else to f20 in your case, then
those rules will break again. If acpid maintains sane semantics then
users don't need to worry about this.

>   Will you be able to do what you need to do if you receive a button/f20
> event?  Can you explain in more detail exactly how you will be using this
> event?  Will you be using it via acpid config files?  Or will you be
> connecting to the acpid socket?  Or something else?

I can. Currently I override udev keymaps to map the micmute as micmute
and handle it with a acpid rule. I don't use gnome-settings-daemon,
but this way breaks it.

I originally thought this should really be a regression and a bad
workaround in udev, but apparently non-gnome users are minority.

>   Based on the particulars, I have a number of alternative solutions that
> should solve your current issue and future-proof acpid at the same time.

I can certainly help with my individual problem but I just wanted to
report about the regression from
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701206 (archived,
couldn't post).

> Ted.
> PS: I'm having trouble sending email to bugs.debian.org.  If you could quote
> my entire email in your response, that would at least get it into the bug
> report.  Thanks.

More information about the Pkg-acpi-devel mailing list