[Wayland-bugs] [Bug 105275] Xorg server crashes with assertion failure: Xorg: ../src/evdev-mt-touchpad-tap.c:1030: tp_tap_handle_state: Assertion `tp->tap.nfingers_down >= 1' failed.
https://bugs.freedesktop.org/show_bug.cgi?id=105275 Aaron Plattnerchanged: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #4 from Aaron Plattner --- Verified that this is fixed now. Closing. -- 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 105258] libinput crashes Xorg with SIGABRT in libinput_event_get_pointer_event
https://bugs.freedesktop.org/show_bug.cgi?id=105258 --- Comment #11 from Aaron Plattner--- Thanks Peter! I built from commit 12410dfba4b903108c8926d68c64ed1c7468902d and so far, haven't been able to reproduce the problem. -- 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 102649] Mouse taps (?) detected while typing
https://bugs.freedesktop.org/show_bug.cgi?id=102649 --- Comment #50 from Christopher Carr--- I'm now at 1.10.2. Will give it a spin for a couple days and let you know if I continue to encounter the same issues. Rimas' " ... cursor jumped between 't' and 'ermina' ..." description describes what I've been encountering exactly. -- 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 105407] Xorg assertion failure: Xorg: ../src/evdev-mt-touchpad-tap.c:1002: tp_tap_handle_state: Assertion `tp->tap.nfingers_down > 0' failed.
https://bugs.freedesktop.org/show_bug.cgi?id=105407 --- Comment #6 from sven--- I get a similar assertion on 1.10.2, while 1.10.1 works fine for me. System is a ThinkPad T420 without any external input devices. > gnome-shell: ../libinput-1.10.2/src/evdev-mt-touchpad-tap.c:1028: > tp_tap_handle_state: Assertion `tp->tap.nfingers_down >= 1' failed. And also this message by gnome-shell: > libinput error: client bug: timer event13 middlebutton: offset negative > (-222ms) -- 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 101139] Acceleration still too fast with slow and slow-medium finger movements
https://bugs.freedesktop.org/show_bug.cgi?id=101139 --- Comment #32 from Peter Hutterer--- doh, sorry, hit the wrong button. Continued: More experimenting with the lowclip patch is needed, and it needs to be compared to the original touchpad pointer accel (for which I got a lot of complaints for, so let's not go back to that). I think macos may also use pressure values (well, touch sizes) for acceleration, but I'm not 100% of that. What it definitely has is deceleration at low speeds, that bit is missing from the lowclip patch. So the things to do to get closer to macos (from git master): * keep deceleration at super-low speed * shorten the plateau * experiment with the incline a bit more * verify max accel is still useful once the above is there * slightly reduce the baseline lowclip does 2 and 5 of these already, but the baseline is too low for a default setting. If you want it that low, you can reduce your speed in the config. The rest, well, we'll have to experiment to see if we come to some agreement :) -- 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 101139] Acceleration still too fast with slow and slow-medium finger movements
https://bugs.freedesktop.org/show_bug.cgi?id=101139 --- Comment #31 from Peter Hutterer--- Hooray. The good news: based on these videos, I don't think we have a libinput *bug*, this does appear to be just a different preference. AFAICT, the movement matches what I got with the lowclip patch, at least considering the finger motion speed etc. The bad news: to accommodate for this, we'd need some new pointer acceleration profile because if *that* is your preferred behaviour, it's going to be difficult to find a middle ground between the current and your patch. Because I consider the fast pointer motion (like in your second video) to be uncontrollable, I don't even get near any target when moving fast. Adding a new profile is relatively trivial, but it opens us up to a few things: once you have two profiles, the floodgates are open for N profiles. Anyone not happy with the current profile will be pushing for another profile slightly different and that's a situation I really want to avoid. fwiw, my macos at default speed is a lot faster than the lowclip patch. And given that we have the accel range, I think the first thing to look at is moving that baseline. From what I can tell, the macos accel doesn't have that same unaccelerated plateau that we have, it seems to almost contineously linear. -- 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