https://bugs.freedesktop.org/show_bug.cgi?id=103572
--- Comment #54 from Daniel van Vugt ---
There's really no need to be afraid of 20 as the down threshold. This is a very
high quality piece of equipment with no apparent hardware jitter. It's also a
peripheral
https://bugs.freedesktop.org/show_bug.cgi?id=103572
--- Comment #50 from Daniel van Vugt ---
That might be true, but I'm not looking at this any more. I just tested 20:10
as was suggested.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=103572
--- Comment #52 from Daniel van Vugt ---
Sorry. I'll get back to this tomorrow if it's not already done.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=103572
--- Comment #49 from Peter Hutterer ---
> not reported as "down" when finger is still down
Are we talking about accidental releases here? Because that's better fixed by
by just having a higher range, e.g. 60:10. Or
https://bugs.freedesktop.org/show_bug.cgi?id=103572
--- Comment #51 from Peter Hutterer ---
Sigh. Maximilian, can you please test this with 60:10, thanks.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=105908
--- Comment #12 from Peter Hutterer ---
right, the main problem we have with evemu is that it can only record a single
device at a time (and your version of evemu is... old). libinput git master has
a libinput record
https://bugs.freedesktop.org/show_bug.cgi?id=103572
--- Comment #55 from Maximilian Böhm ---
Just compared 60:20 and 20:10: Go with 20:10. Makes a noticeably difference in
‚initial thrust‘ and accuracy.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=105094
--- Comment #7 from eyen...@gmail.com ---
This behaviour didn't happen again so I couldn't provide more information. I'll
reopen it if it happens again and I have output from libinput debug-events
--verbose.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=103572
--- Comment #53 from zi...@hmt.im ---
I'd be willing to test too but I'm not quite sure how to try out the different
settings. Is there a howto somewhere?
The new settings are way better than before (initial bug report vs now) but
when I go
https://bugs.freedesktop.org/show_bug.cgi?id=106036
--- Comment #2 from peter.ganzh...@gmail.com ---
Thanks for caring about this.
I had a look at the libinput source (
https://github.com/wayland-project/libinput ) but quite honestly I was not able
to locate the file where model-specific quirks
https://bugs.freedesktop.org/show_bug.cgi?id=103749
Davide Depau changed:
What|Removed |Added
Assignee|wayland-bugs@lists.freedesk |dav...@depau.eu
https://bugs.freedesktop.org/show_bug.cgi?id=106109
Bug ID: 106109
Summary: Touchpad and Trackpoint locked together
Product: Wayland
Version: unspecified
Hardware: x86-64 (AMD64)
OS: All
Status: NEW
https://bugs.freedesktop.org/show_bug.cgi?id=105908
--- Comment #14 from Peter Hutterer ---
fwiw, all the libinput tools create their own context, so they don't care
what X driver is in use.
I was expecting a line like this in the output:
event17 - palm: dwt
https://bugs.freedesktop.org/show_bug.cgi?id=105908
--- Comment #13 from naj...@posteo.net ---
> What's the initial output of libinput debug-events --verbose, before any
> events
It's as follows, though at present I have the synaptic driver installed and
running. (Previously, whenever I have
https://bugs.freedesktop.org/show_bug.cgi?id=106109
Peter Hutterer changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=106113
Bug ID: 106113
Summary: libinput loses track and completely stops responding
during two-finger scrolling
Product: Wayland
Version: unspecified
Hardware: Other
16 matches
Mail list logo