[Wayland-bugs] [Bug 104091] kernel: Touchpad not recognized as clickpad, HP Stream 11 d077nr

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=104091

Peter Hutterer  changed:

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |NOTOURBUG

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 104101] Cursor does not move when starting touch from side of touchpad. HP Stream 11-d077nr

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=104101

--- Comment #12 from Peter Hutterer  ---
timeout is 200ms, see tp_palm_detect_move_out_of_edge() in the source. That
seems fast enough for quick swipes.

as of 1.9.1, the edges are a maximum of 8mm, provided the touchpad dimensions
are correct. the theory goes that after 8mm we *should* be able to detect a
palm based on other data, e.g. pressure or touch size. not that this is
reliable on all touchpads yet, but one can hope.

> In your opinion, how large should such a motion be to 'un-palm' the touch 
> which
> started and hung out for too long in an exclusion zone? (i.e. if someone found
> time to add such an enhancement :)

honestly, I don't know. It's a lot of trial and error until you eventually find
something that seems to work. That's the best answer I can give you here, your
guess is as good as mine.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 103960] libinput trackpad zoom too sensitive

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=103960

--- Comment #3 from Peter Hutterer  ---
> If I swipe a bit harder and faster and then later on press ctrl key, all of 
> the apps suddenly combine the delayed scroll weight roll and ctrl key press 
> as brand new ctrl key plus scroll event.

that is a long-standing issue with the synaptics driver, but not with libinput.
libinput doesn't do kinetic scrolling, any scroll event that happens after
finger release is emulated in the client. Are you sure you're on libinput here?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 104101] Cursor does not move when starting touch from side of touchpad. HP Stream 11-d077nr

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=104101

--- Comment #11 from Jamie Macdonald  ---
Out of curiosity, how long is that timeout? it seems I have to be *really* fast
to get the cursor to move when I've started in the exclusion area. I feel like
if the timeout were higher, I wouldn't run into this issue as much.

In your opinion, how large should such a motion be to 'un-palm' the touch which
started and hung out for too long in an exclusion zone? (i.e. if someone found
time to add such an enhancement :)

Finally, it seems that my left and right exclusion zones take up about 10mm on
either side, so more like 10% of the touchpad which is more than what the
expected behaviour on the linked page describes, no? - is this expected or
configurable?

Thanks for your knowledge (:

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 104087] SMART Board Pen not supported

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=104087

--- Comment #4 from Peter Hutterer  ---
hmm, I replayed the events here and there's heaps of stuff coming out of
libinput and it matches the evemu recording. Try it yourself with sudo libinput
debug-events.

so I'm not sure what is going on here. How many device nodes are exposed by the
smart board? The xinput output suggests it's 6 in total? How do those device
nodes look with evemu-record?

And fwiw, if evemu-record doesn't see events, then the issue is in the kernel.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 103960] libinput trackpad zoom too sensitive

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=103960

--- Comment #2 from Mikko Rapeli  ---
Hmm. Both web and file browsers suffer from this on my Xfce desktop. It feels
the same on a number applications: from Thunar to Nautilus to Firefox to
Chromium.

All behave in same so I suspect the input SW stack is the same and libinput is
somewhere there too.

As a user it feels like something is adding an invisible weight to the scroll
motion and this keeps weight keeps rolling after the movement on trackbad had
ended. If I swipe a bit harder and faster and then later on press ctrl key, all
of the apps suddenly combine the delayed scroll weight roll and ctrl key press
as brand new ctrl key plus scroll event.

But they are not the same input gesture. They are separate. There a few tens if
not hundreds of milliseconds between stopping scroll movement on track pad to
when ctrl is pressed.

I think something in the SW stack, maybe libinput, could separate these two
gestures. Or maybe there is way to change the weight of the virtual scroll ball
to reduce the fly wheel effect where it keeps going long after my finger lifted
from trackpad.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 104101] Cursor does not move when starting touch from side of touchpad. HP Stream 11-d077nr

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=104101

--- Comment #10 from Peter Hutterer  ---
speed is *one* metric for palm detection, but doesn't apply in this case. Here
it's a simple timeout, not the movement speed itself. IOW if you move out of
the area quickly enough, we assume this was a real movement. This is needed
because large left<->right movements frequently start with a finger in the edge
area.

Palms often move around a bit but less so than a finger, hence the timeout - if
it stays within the edge for long enough we assume it's a palm.

There's room for improvement as usual, e.g. we should have a maximum motion
towards the center at which we should un-palm the touch again. But no-one's
found the time to work on that yet.

Also, it's always hard to compare to macos - the apple touchpads are *very*
good, if I'd have to write libinput so it only works for those life would be a
lot easier :)

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs