Summary: | sensitivity and speed parameters missing for ETPS/2 Elantech TrackPoint | ||
---|---|---|---|
Product: | Wayland | Reporter: | mrcjkb89 <mrcjkb89> |
Component: | libinput | Assignee: | Wayland bug list <wayland-bugs> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | peter.hutterer |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
mrcjkb89@outlook.com
2017-10-18 07:56:05 UTC
Please run the libinput measure-trackpoint-range tool to measure the range of your trackpoint. I can't seem to be able to get the tool started. According to man libinput-measure, the only measurable feature for my device is measusure-touchpad-tap-time (which I also can't execute) 'sudo libinput measure trackpoint-range' should be enough, the tool searches for a trackpoint device automatically. Theat returns 'Failed to execute 'trackpoint-range' (No such file or directory)'. oh, right. you're on 1.8 - that tool was added (together with a new trackpoint acceleration) in 1.9 - grab libinput from git and build it, you can run that tool directly from the built tree. Though given the new accel method, you're better off trying 1.9 first I built verstion 1.9 from the git repo. Now typing 'sudo libinput measure trackpoint-range' returns an exception: Traceback (most recent call last): File "/usr/libexec/libinput/libinput-measure-trackpoint-range", line 29, in <module> import evdev ModuleNotFoundError: No module named 'evdev' you need to install python-evdev (that's the fedora package name, but you get the gist) Ah, I had it confused because the Arch Wiki page on 'evdev' redirects to 'xorg'. The range is around max x: 13 max y: 9 if I operate it normally. I can get both x and y close to 30 if I push hard (so hard that the surrounding keyboard keys are triggered. Update: After a reboot, the trackpoint appears a lot faster. Strange, 'udevadm hwdb --update' alone was not enough. the hwdb update only updates the database used for the next udev run. to get that to apply to a device you need to unplug the device (rather hard with a trackpoint) or retrigger it as outlined in: https://wayland.freedesktop.org/libinput/doc/latest/faq.html#faq_hwdb_changes but if you also update libinput, then you need to restart your session too. A reboot takes care of all of these. That aside, you're on 1.9 now? The trackpoint accel good enough now? Ah, that makes sense :) Yes, I am on 1.9. It's a lot faster than on 1.8. Even higher acceleration would always be nice, but it would probably impair the accuracy. I'm happy with what I have for now :) ok, thanks. closing this bug |
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.