IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
<mgorny> it seems that udev-git is b0rked while tag '173' works fine for me
<mgorny> the rule in question is:
<mgorny> also, with >173 persistent-net rules seem to get constantly recreated
for same devices
<kay> mgorny: logic bug. we only sort the keys in an index, but we don't care
about the index when reading the list, which doesn't work too well for
the rules file list where we depend on the order
This keyboard have 16 "multimedia" keys plus a "4-way turbo scroll pad" which
is essentially a round up/down/left/right button. Unfortunately most of these
keys emit non-standard scancodes in a range 495-508 which does not make any
sense. I tried to remap those to the best of my knowledge.
Note the keyboard comes up as two event devices, second one is multimedia
keys, so I ended up adding ENV{ID_USB_INTERFACE_NUM}=="01" to avoid
unnecessary initialization of the "main" keyboard.
On a ThinkPad X220 there is a microphone mute button which generates
ACPI event "ibm/hotkey HKEY 00000080 0000101b". As there is no key like
"micmute", map it to prog2.
Prefer reading keymaps from /etc/udev/keymaps/ so that it's easy to just
locally fix a key or two by copying the existing keymap file from
/lib/udev/keymaps/. This works similarly to udev rules.
http://bugs.debian.org/556045
On Tue, Aug 2, 2011 at 10:56, Thomas Bächler <thomas@archlinux.org> wrote:
> Commit c49df20758 prevented udev from
> creating broken symlinks for bluetooth hid devices. Unfortunately,
> it also removed the ID_INPUT=1 and ID_INPUT_{KEY,MOUSE}=1 properties
> from those devices. Xorg relies on these properties for cold- and
> hotplugging of input devices.
Skip event devices which don't have ID_INPUT_KEY set, to avoid running the long
list of rules more than necessary.
Note that we don't limit ourselves to ID_INPUT_KEYBOARD, as we might want to
fix extra buttons on e. g. fancy mouses or tablet screens, too.
