[Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
Bug Watch Updater
408903 at bugs.launchpad.net
Tue May 14 01:19:16 UTC 2013
Launchpad has imported 22 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=54171.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
------------------------------------------------------------------------
On 2012-08-28T22:18:47+00:00 James M. Leddy wrote:
Unfortunately, udev and the kernel use a keymap that is out of range of
X for micmute. We should use a key that X can process. Since there is no
F20 key on the thinkpad, which is the only platform I know of that has a
micmute key, we can use that.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/67
------------------------------------------------------------------------
On 2012-08-28T23:54:39+00:00 Sergey V. Udaltsov wrote:
I guess it would be more correct to fix udev/kernel. Isn't that so?
Currently symbols/inet(evdev) is used for all keyboards, so all of them
would use F20 for micmute. I am not very happy about that...
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/68
------------------------------------------------------------------------
On 2012-08-29T15:51:04+00:00 James M. Leddy wrote:
(In reply to comment #1)
> I guess it would be more correct to fix udev/kernel. Isn't that so?
It's already "fixed" in udev/kernel, because udev/kernel can handle
keycodes over 255. However, X11 can't (MICMUTE is out of range), we have
to remap it to something that X11 can use. We've used F21-23 before, so
I assumed that was the best place to put it. I'm open to suggestions.
> Currently symbols/inet(evdev) is used for all keyboards, so all of them would
> use F20 for micmute. I am not very happy about that...
What keyboards have F20? We're already using F21-23 for the touchpad
on/off/toggle buttons, so there is a precedent for this.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/69
------------------------------------------------------------------------
On 2012-08-29T15:55:10+00:00 Bugzilla-x wrote:
Are there physical keyboards with an F20 key?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/70
------------------------------------------------------------------------
On 2012-08-29T16:02:04+00:00 James M. Leddy wrote:
(In reply to comment #3)
Not in common use. The M keyboard only has 12, and the Sun keyboard only has 12. Seems that every PC vendor and certainly every laptop maker only goes up to F12. Even the X Termainal photo from Wikipedia only has up to F12
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/71
------------------------------------------------------------------------
On 2012-08-29T16:47:29+00:00 Alan Coopersmith wrote:
(In reply to comment #4)
> Not in common use. The M keyboard only has 12, and the Sun keyboard only has
> 12. Seems that every PC vendor and certainly every laptop maker only goes up to
> F12. Even the X Termainal photo from Wikipedia only has up to F12
Sun keyboards in the 80's had 35 F-keys - since around 1990 many of those were
relabeled - the left side keys to the SunStop, SunProps, etc and the right side
to the numeric keypad. Those were only found on the old Sun 4 and older
systems, not any UltraSPARC, x86 or AMD64 systems. I think other Unix
workstations from the era had similarly large amounts of F keys for the
CAD/CAM applications of the time, but those fell out of use over the years.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/72
------------------------------------------------------------------------
On 2012-08-29T18:49:05+00:00 Wettstein509 wrote:
> Are there physical keyboards with an F20 key?
Unicomp "terminal" keyboards have 24 function keys, are still
manufactured, and available with USB for use with a PC.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/73
------------------------------------------------------------------------
On 2012-08-29T21:13:15+00:00 Sergey V. Udaltsov wrote:
> Unicomp "terminal" keyboards have 24 function keys, are still manufactured, and
> available with USB for use with a PC.
So, F30?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/74
------------------------------------------------------------------------
On 2012-08-30T14:30:31+00:00 James H. Cloos Jr. wrote:
I wasn’t ready to come out of the woodwork with this, but given this bug
report....
I've started implementing my earlier suggestion to get around X’s 8–bit
keycode limitation by modifying evdev to create one X keyboard device
for each 7–bit block of linux event key codes.
This will make every key available to X, inlcuding the mic mute key,
the zoom key (Fn-SPC), et al.
Not to mention all of the telephone and media-device input keys
(KEY_OK .. KEY_CAMERA_RIGHT).
My plan was/is to get it into shape by the end of this (holiday)
weekend.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/75
------------------------------------------------------------------------
On 2012-08-30T16:00:36+00:00 James M. Leddy wrote:
Wow, okay. That's great news! I can certainly wait a few more months,
thanks for working on it.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/76
------------------------------------------------------------------------
On 2012-08-30T16:01:01+00:00 James M. Leddy wrote:
s/months/days/
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/77
------------------------------------------------------------------------
On 2012-10-30T10:44:32+00:00 James M. Leddy wrote:
Hi James,
I don't think I'm on the relevant mailing lists. Have you posted the
code yet?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/78
------------------------------------------------------------------------
On 2013-03-19T10:44:01+00:00 Ozancag wrote:
What's the status of this?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/83
------------------------------------------------------------------------
On 2013-03-19T13:51:42+00:00 James M. Leddy wrote:
The bug is stagnant. I'm not sure if James Cloos has fixed it in X yet,
but because we're waiting on that proper fix we haven't mapped micmute
to F20 just yet.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/84
------------------------------------------------------------------------
On 2013-04-17T20:38:56+00:00 James M. Leddy wrote:
I've sent another message to the list to see if they would include the
patch. It is not worth holding off on this, even if we do eventually get
around the 8 bit keycode limitation, since while I wasn't looking both
udev and gnome-settings-daemon have standardized on F20 for this key.
https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=5cda26ee
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/89
------------------------------------------------------------------------
On 2013-04-18T21:27:12+00:00 Sergey V. Udaltsov wrote:
I would prefer for James Cloos to fix it properly..
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/90
------------------------------------------------------------------------
On 2013-04-18T22:52:58+00:00 James M. Leddy wrote:
(In reply to comment #1)
> Currently symbols/inet(evdev) is used for all keyboards, so all of them
> would use F20 for micmute. I am not very happy about that...
This doesn't really make sense. Yes, today symbols/inet is used for all
keyboards, but FK20 (code 198) is not mapped to _anything_. If you
actually have a keyboard with an F20 key, it'll be remapped by the
vendor specific keyboard map anyway (eg digital_vndr/lk).
A quick grep reveals that only 3 keyboards even use this key: a VT105,
an ancient DEC keyboard that also requires a special driver, and a
fujitsu keyboard that I can't find any mention of online.
The other approach if people are really big on keeping F20 functionality
around is to map FK20 to F20, and leave gnome-settings-daemon as it is.
This has the downside of making XF86AudioMicMute irrelevent.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/91
------------------------------------------------------------------------
On 2013-04-19T01:13:20+00:00 Peter Hutterer wrote:
quite frankly, I think we should admit defeat and go with the F20 route.
X gaining support for > 255 keycodes is unlikely to ever happen and F20
is as good/bad a key as any.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/92
------------------------------------------------------------------------
On 2013-04-19T15:01:54+00:00 James H. Cloos Jr. wrote:
Anthough I know what needs to be done, and have a preliminary commit for
xkeyboard-config, the changes for xf86-input-evdev will require a block
of time I've not been able to schedule.
I agree that that f20 patch is good for now.
I'll post something on the list about my proposed patches.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/93
------------------------------------------------------------------------
On 2013-04-19T22:03:37+00:00 Sergey V. Udaltsov wrote:
Ok, let's do it with F20. The patch does not apply to git:
$ git am ~/Downloads/mail.google.com
Applying: Add XF86AudioMicMute mappings
error: patch failed: symbols/inet:120
error: symbols/inet: patch does not apply
Patch failed at 0001 Add XF86AudioMicMute mappings
The copy of the patch that failed is found in:
/home/svu/git/xkeyboard-config/.git/rebase-apply/patch
When you have resolved this problem, run "git am --resolved".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/94
------------------------------------------------------------------------
On 2013-05-13T18:10:41+00:00 James M. Leddy wrote:
Created attachment 79265
0001-https-bugs.freedesktop.org-show_bug.cgi-id-54171.patch
Sorry about that, this patch should work.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/95
------------------------------------------------------------------------
On 2013-05-13T18:12:52+00:00 James M. Leddy wrote:
Created attachment 79266
0001-Add-XF86AudioMicMute-mappings.patch
Forgot the title for the last patch. This one is better.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/408903/comments/96
** Changed in: xkeyboard-config
Status: Unknown => Confirmed
** Changed in: xkeyboard-config
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to udev in Ubuntu.
https://bugs.launchpad.net/bugs/408903
Title:
Does not handle microphone mute button (KEY_MICMUTE)
Status in OEM Priority Project:
Triaged
Status in OEM Priority Project precise series:
Confirmed
Status in OEM Priority Project raring series:
Triaged
Status in central project for keyboard configuration:
Confirmed
Status in “gnome-settings-daemon” package in Ubuntu:
Triaged
Status in “udev” package in Ubuntu:
Triaged
Status in “xserver-xorg-input-evdev” package in Ubuntu:
Triaged
Status in “gnome-settings-daemon” source package in Raring:
Triaged
Status in “udev” source package in Raring:
Triaged
Status in “xserver-xorg-input-evdev” source package in Raring:
Triaged
Bug description:
Ubuntu 9.04
Pressing the new microphone mute button does not do anything. It
should toggle the mute on the current capture device and toggle an led
that is part of the button.
acpi_listen output:
ibm/hotkey HKEY 00000080 0000101b
xev output:
MappingNotify event, serial 34, synthetic NO, window 0x0,
request MappingKeyboard, first_keycode 8, count 248
MappingNotify event, serial 34, synthetic NO, window 0x0,
request MappingKeyboard, first_keycode 8, count 247
KeyPress event, serial 34, synthetic NO, window 0x3400001,
root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207),
state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 34, synthetic NO, window 0x3400001,
root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207),
state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/408903/+subscriptions
More information about the foundations-bugs
mailing list