Closed z0rc closed 3 years ago
I just realized, that my issue might not be easily reproducible with any mouse, as I'm using mouse with high polling rate of 1000 Hz.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the bug After deprecation of
--device
option and introduction of filters fusuma and libinput-debug-events consume a lot of CPU on mouse movements.To Reproduce Steps to reproduce the behavior:
Expected behavior CPU usage should remain minimum.
Versions
Additional context Effectively it's resurrection of #77. At introduction
fusuma --device
option was propagated tolibinput-debug-events
command line option, which make libinput to report events from single device. In contrary filter option doesn't have effect onlibinput-debug-events
command line options. On my system running filter with trackpad name results in a lot of wasted cpu cycles, where libinput-debug-events reports a lot of events from other devices (mouse is the most noisy) and fusuma just filters them out.I'm aware about
But this is another problem, as it expects kernel path, which isn't really constant (it can change depending whether laptop booted with our without dock). Ideally I'd like to have option where I can specify device name (like in filter), then it would be translated to kernel path and executed
libinput-debug-events --device=<kernel path>
.