Summary: | Typing blocks external mouse for about a second | ||
---|---|---|---|
Product: | xorg | Reporter: | Nikolaus Rath <Nikolaus> |
Component: | Input/evdev | Assignee: | Peter Hutterer <peter.hutterer> |
Status: | RESOLVED NOTOURBUG | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | normal | ||
Priority: | medium | CC: | peter.hutterer |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | 100345 | ||
Bug Blocks: |
Description
Nikolaus Rath
2017-03-22 18:45:16 UTC
evdev doesn't have any disable-while-typing mechanism and if you say syndaemon isn't running I'm not sure what happens here. Either way syndaemon shouldn't affect USB mice anyway. Run xinput watch-props "device name" on the mouse and the touchpad and see if any of the properties change when you use the keyboard. Both $ xinput watch-props 'ALP000D:00 044E:120C' and $ xinput watch-props 'AlpsPS/2 ALPS GlidePoint' does not show any changes when I type, even if the touchpad clearly becomes blocked. However, at the moment my external mouse is actually no longer blocked. Could this be related to the fact that I only plugged it in later? run evemu-record on the kernel device for the touchpad (and/or mouse) and see if it blocks there too - if so, it's a bug in the kernel. I don't quite understand. You mean the mere act of running 'evemu-record' could prevent the blocking? If not, then what do you mean with "if it blocks there too". $ sudo evemu-record /dev/input/event17 Shows prints something whenever I use the touchpad, but there is no change when I start (or stop) typing on the keyboard, what I meant was: if you look at the touchpad device with evemu, do the events stop when you start typing? If so then the issue is in the hardware or the kernel. If you still see events from the touchpad while typing, then the issue is in userspace somewhere. Ah, got it. Yes, when I am typing (and up to about 1 second after stopping), 'evemu-record' does not show any events for the touchpad. Do you have any suggestion where I could start to track this down in the kernel? It's weird, it very much looks like a deliberate feature... libinput sees the same events as evemu does, so there isn't much we can do. I suspect this is due to the device not being in proper touchpad mode and the firmware implementing some disable-while-typing. Let's track this in bug #100345. |
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.