Upgrading xf86-input-libinput from 0.19.* to 0.20.* broke wireless keyboard for me (the keyboard works in tty1-tty6, but it does not work in X sessions). Downgrading back to 0.19 fixes the problem. The behavior is deterministic in that 0.19 always works and 0.20 always doesn't. I'm using Arch. There are no suspicious entries in journalctl when plugging the the keyboard under the broken version (0.20). Thoughts? (The issue is no longer critical for me, but I guess solving it may be helpful to others.)
This bug on Arch bugtracker: https://bugs.archlinux.org/task/51262?project=1&cat%5B0%5D=2&string=xf86-input-libinput
Is it really just the xorg driver or is it a sideeffect of a libinput update that was pulled in? Can you attach the evemu-describe output for your keyboard, and the output from libinput-list-devices, thanks.
Peter, thanks for your response. Output of evemu-describe (taken while using the working version xf86-input-libinput): /dev/input/event1: A4TECH USB Device Output from libinput-list-devices: ``` Device: A4TECH USB Device Kernel: /dev/input/event1 Group: 1 Seat: seat0, default Capabilities: keyboard pointer Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock: n/a Left-handed: n/a Nat.scrolling: disabled Middle emulation: n/a Calibration: identity matrix Scroll methods: none Click methods: none Disable-w-typing: n/a Accel profiles: n/a Rotation: n/a ```
https://gist.github.com/vn971/50e7b90602aaa44dbf8145e37a5bbc9d
Sorry, I didn't understand evemu-describe output at all. The full one is pasted above (github gist URL).
Created attachment 127150 [details] device.evemu please don't link to external pastebins/github/etc., they have independent life cycles and tend to disappear when you need them most
(In reply to n1dr+cmbugsfreedesktop@yandex.com from comment #5) > Sorry, I didn't understand evemu-describe output at all. The full one is > pasted above (github gist URL). http://who-t.blogspot.co.at/2016/09/understanding-evdev.html has an explanation that should help. I'm still on holidays for a few more days and probably won't get to it until after
also, do you see events when you run sudo libinput-debug-events?
Sorry, this was a typo, I meant to say that I didn't understand the output _at first_.. Anyway, thanks again. I didn't figure out how to attach a file at first. Thanks. Will be waiting for any updates then. These 2 events happen when I plug in the keyboard under the working version of xf86-input-libinput: ` -event1 DEVICE_ADDED A4TECH USB Device seat0 default group8 cap:kp scroll-nat calib -event2 DEVICE_ADDED A4TECH USB Device seat0 default group8 cap:p left scroll-nat scroll-button `
you don't get any events when you type on it?
I do, I get events on key presses and mouse movements (when under the package version that works).
testing with this evemu recording, I can send events through the device and they appear as expected. so I'm not sure where the events are lost here. (In reply to n1dr+cmbugsfreedesktop@yandex.com from comment #11) > I do, I get events on key presses and mouse movements (when under the > package version that works). libinput is independent of xf86-input-libinput. do you get events out of libinput when X doesn't work?
also, do you have an xorg.log by any chance?
I'm truly sorry for the bug tracking quality, I've been on a long vacation since raising the ticked and have a different computer now. Also, there was an another upgrade of xf86-input-libinput shortly thereafter, and the same wireless keyboard works on the new computer. Will have to close the current ticket for lack of information. Sorry again..
ok thanks, I'll close this bug for now but please reopen it when that issue comes back.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.