From: Florian Mickler <florian@mickler.org>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: linux-kernel@vger.kernel.org, mjg@redhat.com,
dmitry.torokhov@gmail.com, linux-input@vger.kernel.org
Subject: Re: multi-media key "mute" no longer recognized
Date: Fri, 24 Feb 2012 00:08:26 +0100 [thread overview]
Message-ID: <20120224000826.05039158@schatten> (raw)
In-Reply-To: <201201231152.25344.toralf.foerster@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
Let's try to cc some people...
On Mon, 23 Jan 2012 11:52:24 +0100
Toralf Förster <toralf.foerster@gmx.de> wrote:
> With kernel 3.1.10 I could mute my system by pressing the appropriate
> multimedia button either at my ThinkPad or at my external keyboard.
> With 3.2.1 this doesn't work anymore although the button itself is recognized
> when pressed (checked with xev).
>
> Now I'm wondering where to start to debug ?
>
In https://bugzilla.kernel.org/show_bug.cgi?id=42685 Toralf wrote:
> > with xev I get only one small diff related to "serial":
> >
> > tfoerste@n22 ~ $ tail -v mute-3.*
> > ==> mute-3.0.21 <==
> > KeyRelease event, serial 33, synthetic NO, window 0x4600001,
> > root 0xc3, subw 0x0, time 293494, (1260,275), root:(1262,298),
> > state 0x0, keycode 121 (keysym 0x1008ff12, XF86AudioMute), same_screen YES,
> > XLookupString gives 0 bytes:
> > XFilterEvent returns: False
> >
> >
> > ==> mute-3.2.6 <==
> > KeyRelease event, serial 32, synthetic NO, window 0x3a00001,
> > root 0xc3, subw 0x0, time 3424766, (-1217,745), root:(74,768),
> > state 0x0, keycode 121 (keysym 0x1008ff12, XF86AudioMute), same_screen YES,
> > XLookupString gives 0 bytes:
> > XFilterEvent returns: False
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
parent reply other threads:[~2012-02-23 23:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <201201231152.25344.toralf.foerster@gmx.de>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120224000826.05039158@schatten \
--to=florian@mickler.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=toralf.foerster@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).