[Wayland-bugs] [Bug 93641] external numpad gets unresponsive when it's simultaneously used with another keyboard

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=93641

--- Comment #8 from Kamil Páral <kparal at redhat.com> ---
I have to add that I've seen several times today the keypad to get stuck (print
the neverending stream of value 2 events, or stop sending any signals) just by
pressing its buttons alone, not combined with the keyboard. So this error can
be reproduced with just the keypad, but it's just not that likely. When I use
my keyboard simultaneously, it makes reproducing this almost instant.

One further thing, I'm not sure if this is related, but it seems weird to me,
that if I listen to just the keypad using evemu-record, and I press NumLock on
keyboard (different device, not listening to that), it prints these events:
E: 3.352170 0011 0000 0000    # EV_LED / LED_NUML             0
E: 3.352170 0000 0000 0000    # ------------ SYN_REPORT (0) ---------- +2641ms
E: 4.520290 0011 0000 0001    # EV_LED / LED_NUML             1
E: 4.520290 0000 0000 0000    # ------------ SYN_REPORT (0) ---------- +1168ms
However, if I press NumLock on they keypad itself, it generates no events.
Maybe unrelated, maybe even expected. Just mentioning.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-bugs/attachments/20160121/875d2f47/attachment-0001.html>