https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #73 from Peter Hutterer ---
did you run the libinput measure trackpoint-range property yet?
--
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailin
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #72 from Chow Loong Jin ---
I found the trackpoint speed unbearably slow too even when maxed out, so I
recompiled with TRACKPOINT_DEFAULT_MAX_DELTA bumped up to 120, and it feels a
lot better. Perhaps 60 is too conservative, or a twea
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #71 from Peter Hutterer ---
it's part of 1.9.0/ did you set the trackpoint range property correctly?
--
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bu
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #70 from jonas@thiem.email ---
What version should this be part of?
I use Fedora 27 with libinput 1.9.0 and again at maxed out mouse speed the
trackpoint is back to almost unbearably slow unlike with the experimental
branch I tested
https://bugs.freedesktop.org/show_bug.cgi?id=91369
Bug 91369 depends on bug 100982, which changed state.
Bug 100982 Summary: Ship the POINTINGSTICK_CONST_ACCEL hwdb instead of systemd
https://bugs.freedesktop.org/show_bug.cgi?id=100982
What|Removed |Added
--
https://bugs.freedesktop.org/show_bug.cgi?id=91369
Peter Hutterer changed:
What|Removed |Added
Status|NEEDINFO|RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #68 from jonas@thiem.email ---
I just tried building the latest wip/trackpoint-accel-v5 to check it out but it
doesn't build for me on Fedora 26:
-bash-4.4$ ninja -C builddir/
ninja: Entering directory `builddir/'
[50/138] Linking ta
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #67 from Amos Bird ---
hmm, I got this error
libinput error: event19 - libinput error: Lite-On Technology Corp. ThinkPad USB
Keyboard with TrackPoint: libinput error: trackpoint range property is present
but invalid, using 20 instead
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #66 from Iiro Laiho ---
I tried the v4 and v5 repositories of the new libinput branch. I have
LIBINPUT_ATTR_TRACKPOINT_RANGE=15 and it shows at the output of "sudo udevadm
test /sys/class/input/event1" command. The cursor speed is sti
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #65 from Iiro Laiho ---
I tried the v4 and v5 repositories of the new libinput branch. I have
POINTINGSTICK_CONST_ACCEL=2
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=91369
Peter Hutterer changed:
What|Removed |Added
CC||jwrdego...@fedoraproject.or
https://bugs.freedesktop.org/show_bug.cgi?id=91369
Bug 91369 depends on bug 90988, which changed state.
Bug 90988 Summary: libinput: Re-examine pointingstick accel profile
https://bugs.freedesktop.org/show_bug.cgi?id=90988
What|Removed |Added
---
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #63 from Peter Hutterer ---
And another commit on top of that branch, check that you have "filter: apply
the same factor to x and y" before testing please. Mostly happy with this but
I'm not 100% sure about the range yet, the slow one
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #62 from Peter Hutterer ---
Ok, some updates pushed to:
https://github.com/whot/libinput/tree/wip/trackpoint-accel-v4
This one ramps up quicker but still provides precision on slow movements.
Please give it a test, thanks.
--
You a
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #61 from Peter Hutterer ---
jonas: this attribute is supposed to describe the hardware capabilities, don't
try to use it as a configuration thing. It won't work, or have may some adverse
side effects. Thanks for testing though, I'll t
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #60 from jonas@thiem.email ---
Created attachment 131542
--> https://bugs.freedesktop.org/attachment.cgi?id=131542&action=edit
evdev-record output collected for the TrackPoint (Thinkpad Yoga 260)
I experimented around a bit more: I
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #59 from jonas@thiem.email ---
I just compiled libinput with the latest trackpoint-accel-v2 and it is a
tremendous improvement!
I use it with this hwdb entry right now and maxed out mouse speed in GNOME:
evdev:name:* Elantech
Track
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #58 from Peter Hutterer ---
Kai-Heng: I'll double-check the scrolling, it shouldn't be scaled and thus not
be too fast. Thanks for testing!
Alexey: yes, this is the bug you're looking for. See comment 48.
Charles: You can get the re
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #57 from Justin Wong ---
Hi there,
My laptop is Dell Latitude E7440. I've compiled the trackpoint-accel-v2 branch,
and the LIBINPUT_ATTR_TRACKPOINT_RANGE is [-15, 15].
Now my trackpoint speed is finally fast enough. However, I foun
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #56 from Charles Plessy ---
(In reply to Peter Hutterer from comment #53)
> anyone?
Thanks a lot for the instructions on how to test your new code. I compiled and
ran analyze-trackpoint, and got ranges around 25 or 30.
For testing
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #55 from alexey polusov ---
Hello guys. I have Dell Latitude 5470 running ubuntu 16.04.
And I have the exact same problem:
I am unable to achieve acceptable results with all the different knobs that are
available. If I tune down acce
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #54 from Kai-Heng Feng ---
Sorry for the late reply.
Subjectively, I think 50 is quite good.
But trackpoint scrolling is way too fast. Do I miss some additional settings?
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #53 from Peter Hutterer ---
anyone?
--
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.
https://bugs.freedesktop.org/show_bug.cgi?id=91369
Peter Hutterer changed:
What|Removed |Added
CC||segfa...@imap.cc
--- Comment #52 from P
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #51 from Peter Hutterer ---
Take the bigger one until we have separate x/y ranges, so 50 in your case.
--
You are receiving this mail because:
You are the assignee for the bug.___
wayland-
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #50 from Kai-Heng Feng ---
Just tried 'libinput analyze-trackpoint' on Dell Precision 7510, the first
histogram (x) spans through -50 to 50, the second one (y) spans through -40 to
40.
What LIBINPUT_ATTR_TRACKPOINT_RANGE should I use
https://bugs.freedesktop.org/show_bug.cgi?id=91369
Peter Hutterer changed:
What|Removed |Added
CC||charles-debian-nospam@pless
https://bugs.freedesktop.org/show_bug.cgi?id=91369
Peter Hutterer changed:
What|Removed |Added
Status|REOPENED|NEEDINFO
--- Comment #48 from Peter Hut
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #47 from Iiro Laiho ---
My laptop is a Dell Latitude E6320. It was in the filename but maybe I should
have been more clear. Defining that POINTINGSTICK_SENSITIVITY parameter on the
local HWDB does not have any noticeable effect. Also,
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #46 from Peter Hutterer ---
It is, but I don't know what laptop you have and it may just fix the issue for
you or others. Unfortunately, the evemu version you're using is 3 years old and
doesn't give me that information (I'm thus assu
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #45 from Iiro Laiho ---
I am not sure but I recall it is some kind of hardware-side tuning value that
is communicated to the MCU of the pointing stick. It is available on some
IBM/Lenovo devices but not on most other ones.
--
You ar
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #44 from Peter Hutterer ---
uhm, another thing I just noticed - does anyone use the
POINTINGSTICK_SENSITIVITY value? It doesn't show up in the udevadm output and
that is very likely the reason why the trackpoint is so slow. the sensi
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #43 from Iiro Laiho ---
Yes, on my machine the pointing stick's reading seems to maximize at 15, no
matter how hard I push it.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #42 from Peter Hutterer ---
First analysis here. The range differs greatly. Pressing hard on the trackpoint
I have here (which most of libinput's accel is tested against) I can easily get
into the 30+ range for REL_X/Y. Both recording
https://bugs.freedesktop.org/show_bug.cgi?id=91369
Peter Hutterer changed:
What|Removed |Added
Depends on||100982
Referenced Bugs:
https://bugs.
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #41 from Iiro Laiho ---
Created attachment 131277
--> https://bugs.freedesktop.org/attachment.cgi?id=131277&action=edit
My recordings
Here are my slow, medium and fast recordings. Two samples of each.
--
You are receiving this ma
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #40 from Peter Hutterer ---
on that note, I don't even have evemu recordings to debug this...
Please attach three separate recordings, each about 2-3 seconds long, with
evemu-record:
* slow pointer motion with light pressure
* mediu
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #39 from Peter Hutterer ---
(In reply to jonas@thiem.email from comment #37)
> Is my only chance for a workaround to recompile libinput myself? Also, it
> would be nice if this bug was prioritized since it can actual health effects
>
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #38 from jonas@thiem.email ---
I forgot to mention, for some reason the hwdb is actually applied to the
scrolling speed of the trackpoint, but not to the actual movement speed itself
when not scrolling. (just in case that info helps y
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #37 from jonas@thiem.email ---
Ubuntu 17.04 with libinput 1.6.3 on a Thinkpad Yoga 260,
POINTINGSTICK_CONST_ACCEL is ignored.
The trackpoint is WAY too slow per default. I have been using this laptop for a
while under linux with maxi
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #36 from hakaa ---
Same as liro,
I have a Dell E5470
The CONST_ACCEL does show up, but has no effect on the trackpoint/pointstick:
sudo udevadm info /dev/input/event9
P: /devices/platform/i8042/serio1/input/input11/event9
N: input/
https://bugs.freedesktop.org/show_bug.cgi?id=91369
Iiro Laiho changed:
What|Removed |Added
CC||ilmai...@openmailbox.org
--- Comment #35 fr
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #34 from Peter Hutterer ---
don't get too hooked up on the dpi factor, that naming comes from mice that
have actual DPI. A trackpoint works differently, so if there is a different
base factor that we need (e.g. convert it back to a co
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #33 from Justin Wong ---
> by feel mostly. and the fact that this accel method was largely aimed at
> mice and the number of 200dpi mice is so low we don't really need to care
> about them. and of course the obvious reason: it was rel
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #32 from Peter Hutterer ---
(In reply to Justin Wong from comment #31)
> > no. the hwdb is not a configuration system, it's a system to store
> > hw-specific properties.
>
> You mean that you wanna hard code for DELL D520 5150 E430
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #31 from Justin Wong ---
> no. the hwdb is not a configuration system, it's a system to store
> hw-specific properties.
You mean that you wanna hard code for DELL D520 5150 E4300 E6400 E6420 E6410
D810 E7440, and Thinkpad T420 T430
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #30 from Peter Hutterer ---
(In reply to Justin Wong from comment #28)
> The only thing that my patch did is mutiplies incline and dpi_factor, in my
> case, I made incline = incline * 3.
The main question here is: is this a general r
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #29 from Dominic ---
Let me chime in here... I am using a Thinkpad x230 and the trackpoint *still*
feels too slow (set to maximum speed in Gnome, that is). I'd like to have a bit
of choice here,too. :)
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #28 from Justin Wong ---
> E: POINTINGSTICK_CONST_ACCEL=3
> this means we're treating it like a 333 dpi device which has a bit of
Yes, It's behaving like 333 dpi.
> the incline is the same but it should kick in a lot sooner than be
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #27 from Peter Hutterer ---
E: POINTINGSTICK_CONST_ACCEL=3
this means we're treating it like a 333 dpi device which has a bit of a
different acceleration, see
http://wayland.freedesktop.org/libinput/doc/latest/pointer-acceleration.htm
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #26 from Justin Wong ---
I have to say that libinput know I have a low-DPI device as I've been debugging
the code. The point is, the calculated (or adaptive) accel is unacceptablely
slow.
The point is the calculation equation, or co
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #25 from Justin Wong ---
udevadmin info outputs:
```
P: /devices/platform/i8042/serio1/input/input18/event16
N: input/event16
S: input/by-path/platform-i8042-serio-1-event-mouse
E: DEVLINKS=/dev/input/by-path/platform-i8042-serio-1-ev
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #24 from Peter Hutterer ---
fwiw, there was only one accel fix between 1.0 and 1.1 and that affected the
Lenovo x230 device only. what's more likely is that you updated systemd which
contains the hwdb to 'normalize' pointing stick spe
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #23 from Justin Wong ---
Each time libinput releases a new version, I would checkout the code and apply
my patch:
--- a/src/filter.c
+++ b/src/filter.c
@@ -720,7 +720,7 @@ trackpoint_accel_profile(struct motion_filter *filter,
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #22 from Justin Wong ---
Hi, happy to see the relase of libinput 1.1, and my trackpoint got even slower.
Any updates about this issue?
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #21 from Justin Wong ---
Good, thx!
--
You are receiving this mail because:
You are the assignee for the bug.
___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
http://lists.
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #20 from Peter Hutterer ---
yeah, but not for 1.0. The code is in place now to easier add device-specific
pointer accelerations without affecting others, but the actual implementation
will have to wait until 1.1 or 1.2.
--
You are r
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #19 from Justin Wong ---
Hi, version 0.21 and 0.99.1 still has this issue, is there any plan to change
the behavior in future versions?
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #18 from Peter Hutterer ---
Created attachment 117471
--> https://bugs.freedesktop.org/attachment.cgi?id=117471&action=edit
rendering of the acceleration function
this is your acceleration function in comparison to the linear one.
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #17 from Justin Wong ---
Yes, this branch restored old speed but lost presision.
Could you test `s2 = 1 + (speed_in - threshold)*incline/dpi_factor` in
`pointer_accel_profile_linear_low_dpi`? I got both speed and precision in my
lapt
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #16 from Peter Hutterer ---
https://github.com/whot/libinput/tree/wip/trackpoint-accel
this should restore the old trackpoint speed/behaviour and serve as a starting
point for actual trackpoint-specific accel handling. I'll be rebasin
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #15 from Peter Hutterer ---
not all trackpoints are the same, so it's hard to get a one size fits all. the
trackpoint on my lenovo t440 here has a [-30,30] range for example and dropping
pointer acceleration (i.e. constant factor 1) i
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #14 from Justin Wong ---
by modifiying `s2 = 1 + (speed_in - threshold)*incline/dpi_factor`, I got a
reasonable speed and precision.
I wonder have you ever tested trackpoint accel? Here 's2' increases too slow,
and factor is dominat
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #13 from Justin Wong ---
simply letting `pointer_accel_profile_linear` return 1 does not make pointer
natural, returning 2~4 got an acceptable speed.
evemu-record returned EV_REL / REL_X and EV_REL / REL_Y is within [-15, 15]
--
Yo
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #12 from Peter Hutterer ---
pointer_accel_profile_linear is what we used before 0.19, so given the same
CONST_ACCEL value that should give you the same movement as before. the only
other change is commit 6ea69c2b3d18ea39 but I doubt y
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #11 from Justin Wong ---
pointer_accel_profile_linear ends up a slow pointer. I guess this bug isn't
elsewhere. Does `pointer_accel_profile_linear_low_dpi` run frequently to
determine dpi factor, or run once setting up the device? I g
https://bugs.freedesktop.org/show_bug.cgi?id=91369
Peter Hutterer changed:
What|Removed |Added
Depends on||90988
--- Comment #10 from Peter Hutter
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #9 from Justin Wong ---
By modifying `pointer_accel_profile_linear_low_dpi` to directly returning
max_accel, I got a good speed. The problem should be here. :)
--
You are receiving this mail because:
You are the assignee for the bug
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #8 from Peter Hutterer ---
Could be a fallout from 3928f32281, what happens if you change evdev_init_accel
to always pick the normal accel?
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #7 from Justin Wong ---
83028604513641e9bd7c8ad7c864d52c8f313d62 is the first bad commit, you were
right.
It seems there is still another bug.
I added a `log_info` of device DPI before `evdev_device_create` returns,
83028604513641e
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #6 from Peter Hutterer ---
can you do me a favour and bisect then to find the commit that broke it? thanks
--
You are receiving this mail because:
You are the assignee for the bug.
___
way
https://bugs.freedesktop.org/show_bug.cgi?id=91369
Justin Wong changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Version|unspecified
https://bugs.freedesktop.org/show_bug.cgi?id=91369
Peter Hutterer changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #3 from Peter Hutterer ---
confirmed, introduced in 83028604513641e9bd7c8ad7c864d52c8f313d62
--
You are receiving this mail because:
You are the assignee for the bug.
___
wayland-bugs mail
https://bugs.freedesktop.org/show_bug.cgi?id=91369
--- Comment #2 from Justin Wong ---
evtest reports:
```
Input driver version is 1.0.1
Input device ID: bus 0x11 vendor 0x2 product 0x8 version 0x310
Input device name: "AlpsPS/2 ALPS DualPoint Stick"
Supported events:
Event type 0 (EV_SYN)
Ev
https://bugs.freedesktop.org/show_bug.cgi?id=91369
Peter Hutterer changed:
What|Removed |Added
CC||peter.hutte...@who-t.net
--- Comment #1
https://bugs.freedesktop.org/show_bug.cgi?id=91369
Justin Wong changed:
What|Removed |Added
Priority|medium |high
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=91369
Bug ID: 91369
Summary: Libinput 0.19 and 0.20 ignore
POINTINGSTICK_CONST_ACCEL
Product: Wayland
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All
78 matches
Mail list logo
