[Wayland-bugs] [Bug 105043] 3-fingers touch occasionally fails to get detected
https://bugs.freedesktop.org/show_bug.cgi?id=105043 Peter Hutterer changed: What|Removed |Added Status|NEEDINFO|ASSIGNED --- Comment #23 from Peter Hutterer --- > event10 - tap: touch 0 state TAP_STATE_TOUCH_2 → TAP_EVENT_MOTION → > TAP_STATE_TOUCH_2_HOLD That's still the problem here, a motion event after the second finger down causes it to not detect the tap. I think this may be related to how we handle semi-mt touchpads too, because we treat them effectively as single-finger touchpads. In the 20.550366 event you get a large finger movement as slot 1 ends but because we process slots in order, I wonder if that triggers a bug where we think there's movement before we realise it's part of the finger up. -- 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 105094] Two finger scroll stuck/not happening
https://bugs.freedesktop.org/show_bug.cgi?id=105094 --- Comment #5 from Peter Hutterer --- in libinput, touchpads and mice are completely separate so please let's not mix the two issues. If it is a libinput bug, it cannot be the same because there's virtually no overlapping code. The debug log here shows that the button state is correct, you get a press followed by a release event, the seat count is correct too. So if that triggered a stuck button, the issue is in the compositor or on the client side. But either way, this needs a separate bug report please. -- 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 105485] Add hwdb entry for X280 trackpoint (too fast)
https://bugs.freedesktop.org/show_bug.cgi?id=105485 Peter Hutterer changed: What|Removed |Added CC||peter.hutte...@who-t.net Status|NEW |NEEDINFO --- Comment #1 from Peter Hutterer --- Did you measure that with the systemd PR there or without? It'll change the range available so the numbers are garbage otherwise -- 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 105409] Touchpad deadzone on Razer Blade Stealth
https://bugs.freedesktop.org/show_bug.cgi?id=105409 --- Comment #21 from Dave --- Just to confirm, after my finger passes through the deadzone, only MSC_TIMESTAMP records appear, even when I continue moving it. -- 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 105472] Hysteresis inappropriately turned back on for my hardware after being off for months
https://bugs.freedesktop.org/show_bug.cgi?id=105472 --- Comment #8 from Nate Graham --- Um, how do I turn it off then? It turned on quite before I did the small circles routine; I only did that to illustrate the issue. I really don't like how easy it is to accidentally turn this on. -- 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 105472] Hysteresis inappropriately turned back on for my hardware after being off for months
https://bugs.freedesktop.org/show_bug.cgi?id=105472 Peter Hutterer changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG --- Comment #7 from Peter Hutterer --- Your device should have the hysteresis disabled by default. So by doing that you're tricking the code into thinking you have pointer jitter and the wobble detection code *enables* the hysteresis. You're defeating yourself here :) Let me know if the hysteresis enables during a real-world use-case, because that's something worth investigating. -- 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 105472] Hysteresis inappropriately turned back on for my hardware after being off for months
https://bugs.freedesktop.org/show_bug.cgi?id=105472 --- Comment #6 from Nate Graham --- > Is this a real use-case? No, it's just the best way to quickly tell if hysteresis is on or off. -- 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 105472] Hysteresis inappropriately turned back on for my hardware after being off for months
https://bugs.freedesktop.org/show_bug.cgi?id=105472 --- Comment #5 from Peter Hutterer --- > if I continuously make small circles with the cursor Is this a real use-case? You can trick the code (it's a result of how simple it is) but I haven't been able to trigger this during normal interaction. -- 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 105434] libinput-1.10.2: Synaptics touchpad misinterprets movement from top as palm
https://bugs.freedesktop.org/show_bug.cgi?id=105434 Peter Hutterer changed: What|Removed |Added Depends on||101574 Referenced Bugs: https://bugs.freedesktop.org/show_bug.cgi?id=101574 [Bug 101574] Palm detection with TrackPoint buttons -- 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 101574] Palm detection with TrackPoint buttons
https://bugs.freedesktop.org/show_bug.cgi?id=101574 Peter Hutterer changed: What|Removed |Added Blocks||105434 Referenced Bugs: https://bugs.freedesktop.org/show_bug.cgi?id=105434 [Bug 105434] libinput-1.10.2: Synaptics touchpad misinterprets movement from top as palm -- 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 105409] Touchpad deadzone on Razer Blade Stealth
https://bugs.freedesktop.org/show_bug.cgi?id=105409 --- Comment #20 from Peter Hutterer --- oh, right, confidence bit. Forgot to look at that. Anyway, even with a perfect userspace it wouldn't really fix the issue because we'd just be ignoring a palm touch anyway... So IMO this is something the kernel needs to sort out -- 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 tp_tap_handle_state() [evdev-mt-touchpad-tap.c:1030|1028]
https://bugs.freedesktop.org/show_bug.cgi?id=105258 --- Comment #26 from Peter Hutterer --- regarding addr2line: https://who-t.blogspot.com.au/2014/02/making-sense-of-backtraces-with.html see comment #20, this bug is fixed on master, and I cannot reproduce it with the recording (but I can with the commit before d8db6b59). -- 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 105447] Two-finger scrolling broken in 1.10.2
https://bugs.freedesktop.org/show_bug.cgi?id=105447 Peter Hutterer changed: What|Removed |Added Resolution|--- |FIXED Status|NEEDINFO|RESOLVED --- Comment #14 from Peter Hutterer --- ok, thanks for testing. closing as fixed with d8db6b5927f6 based comment 8, that fix will land in 1.10.3 as well. -- 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 tp_tap_handle_state() [evdev-mt-touchpad-tap.c:1030|1028]
https://bugs.freedesktop.org/show_bug.cgi?id=105258 --- Comment #25 from mrbloo...@hotmail.com --- Created attachment 138074 --> https://bugs.freedesktop.org/attachment.cgi?id=138074&action=edit evemu-record of touchpad evemu-record of my SynPS/2 Synaptics TouchPad on a Thinkpad T410. -- 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 tp_tap_handle_state() [evdev-mt-touchpad-tap.c:1030|1028]
https://bugs.freedesktop.org/show_bug.cgi?id=105258 mrbloo...@hotmail.com changed: What|Removed |Added CC||mrbloo...@hotmail.com --- Comment #24 from mrbloo...@hotmail.com --- Created attachment 138073 --> https://bugs.freedesktop.org/attachment.cgi?id=138073&action=edit coredump info I am still getting crashes with 1.10.2. I tried to provide more information by following the instructions in comment #2, but I'm afraid I don't quite understand how to. I am also experiencing the crashes on Arch Linux. I rebuilt the libinput package specifying --builtype debug. Then I triggered another crash and got a coredump (attached info). I will attach an evemu recording shortly. There is nothing in my Xorg log, apart from this line: [ 1149.033] (II) Axis 0x1 value 5120 is outside expected range [1237, 4990] I also ran "eu-addr2line -e /usr/lib64/libinput.so", but I don't know what I'm supposed to do with it since there was no output. Can someone help me to provide more information? -- 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 105094] Two finger scroll stuck/not happening
https://bugs.freedesktop.org/show_bug.cgi?id=105094 --- Comment #4 from eyen...@gmail.com --- This is the part where the 'finger' wasn't released. I'm using my mouse, not the touchpad, and it's also not the scrolling that is the problem but a click. What happened here is that I was clicking on a image link (while moving the mouse) in chromium but instead of registering a click only the push down was registered - continuing at the end of this log part I was "dragging" the image around, without holding any mouse button. To reproduce this behaviour it is important to klick and move at the same time (1 out of ~20 tries behaves this way). The scroll issue did also occur in the terminal so chromium is possibly not the issue. ... event15 POINTER_MOTION +377.87s 1.00/ -1.00 event15 POINTER_MOTION +377.88s 2.00/ -1.00 event15 POINTER_MOTION +377.89s 0.00/ -1.00 event15 POINTER_MOTION +377.89s 0.00/ -1.00 event15 POINTER_MOTION +377.90s 1.00/ -1.00 event15 POINTER_MOTION +377.93s 0.00/ -1.00 event15 POINTER_MOTION +377.95s 1.00/ 0.00 event15 - debounce state: DEBOUNCE_STATE_IS_UP → DEBOUNCE_EVENT_PRESS → DEBOUNCE_STATE_DOWN_WAITING event15 POINTER_BUTTON +378.03s BTN_LEFT (272) pressed, seat count: 1 event15 - debounce state: DEBOUNCE_STATE_DOWN_WAITING → DEBOUNCE_EVENT_TIMEOUT → DEBOUNCE_STATE_IS_DOWN event15 POINTER_MOTION +378.08s 0.00/ -1.00 event15 POINTER_MOTION +378.09s 1.00/ -2.00 event15 - debounce state: DEBOUNCE_STATE_IS_DOWN → DEBOUNCE_EVENT_RELEASE → DEBOUNCE_STATE_RELEASE_WAITING event15 POINTER_MOTION +378.10s 2.00/ -2.00 event15 POINTER_BUTTON +378.10s BTN_LEFT (272) released, seat count: 0 event15 POINTER_MOTION +378.10s 1.00/ -1.00 event15 - debounce state: DEBOUNCE_STATE_RELEASE_WAITING → DEBOUNCE_EVENT_TIMEOUT_SHORT → DEBOUNCE_STATE_RELEASED event15 POINTER_MOTION +378.11s 1.00/ -1.00 event15 - debounce state: DEBOUNCE_STATE_RELEASED → DEBOUNCE_EVENT_TIMEOUT → DEBOUNCE_STATE_IS_UP event15 POINTER_MOTION +378.12s 0.00/ -1.00 event15 POINTER_MOTION +378.13s 0.00/ -1.00 event15 POINTER_MOTION +378.14s 0.99/ 0.00 event15 POINTER_MOTION +378.14s 1.99/ -1.99 event15 POINTER_MOTION +378.15s 2.00/ -2.00 ... -- 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 777693] Input event (e. g. typing on keyboard) is sent repeatedly during high load
https://bugzilla.gnome.org/show_bug.cgi?id=777693 Piotr Drąg changed: What|Removed |Added CC||wild.tch...@gmail.com --- Comment #16 from Piotr Drąg --- *** Bug 794300 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 105043] 3-fingers touch occasionally fails to get detected
https://bugs.freedesktop.org/show_bug.cgi?id=105043 --- Comment #22 from Hi-Angel --- s/double-touch/double-finger touch. -- 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 105043] 3-fingers touch occasionally fails to get detected
https://bugs.freedesktop.org/show_bug.cgi?id=105043 --- Comment #21 from Hi-Angel --- (In reply to Peter Hutterer from comment #20) > Any updates now that all the hysteresis patches have been merged on master? Yeah, double-touch still seems to not work occasionally. I'm using git at commit d8db6b5927f61460b2991479a85056256c819485 "touchpad: end hovering touches in maybe_end_touch". Output of "libinput debug-events --verbose --enable-tap" for a single "non-working" double-touch: event10 - pressure: begin touch 0 event10 - button state: touch 0 from BUTTON_STATE_NONE, event BUTTON_EVENT_IN_AREA to BUTTON_STATE_AREA event10 - button state: touch 1 from BUTTON_STATE_NONE, event BUTTON_EVENT_IN_AREA to BUTTON_STATE_AREA event10 - tap: touch 0 state TAP_STATE_IDLE → TAP_EVENT_TOUCH → TAP_STATE_TOUCH event10 - tap: touch 1 state TAP_STATE_TOUCH → TAP_EVENT_TOUCH → TAP_STATE_TOUCH_2 event10 - button state: touch 1 from BUTTON_STATE_AREA, event BUTTON_EVENT_UP to BUTTON_STATE_NONE event10 - tap: touch 0 state TAP_STATE_TOUCH_2 → TAP_EVENT_MOTION → TAP_STATE_TOUCH_2_HOLD event10 - tap: touch 1 state TAP_STATE_TOUCH_2_HOLD → TAP_EVENT_RELEASE → TAP_STATE_HOLD event10 - tap: touch 0 state TAP_STATE_HOLD → TAP_EVENT_MOTION → TAP_STATE_HOLD event10 - pressure: end touch 0 event10 - button state: touch 0 from BUTTON_STATE_AREA, event BUTTON_EVENT_UP to BUTTON_STATE_NONE event10 - tap: touch 0 state TAP_STATE_HOLD → TAP_EVENT_RELEASE → TAP_STATE_IDLE Output of evemu-record for the same double-touch: E: 20.461822 0003 002f # EV_ABS / ABS_MT_SLOT 0 E: 20.461822 0003 0039 0527 # EV_ABS / ABS_MT_TRACKING_ID 527 E: 20.461822 0003 0035 4097 # EV_ABS / ABS_MT_POSITION_X4097 E: 20.461822 0003 0036 3175 # EV_ABS / ABS_MT_POSITION_Y3175 E: 20.461822 0003 4097 # EV_ABS / ABS_X4097 E: 20.461822 0003 0001 3175 # EV_ABS / ABS_Y3175 E: 20.461822 0003 0018 0026 # EV_ABS / ABS_PRESSURE 26 E: 20.461822 0003 001c 0006 # EV_ABS / ABS_TOOL_WIDTH 6 E: 20.461822 0001 0145 0001 # EV_KEY / BTN_TOOL_FINGER 1 E: 20.461822 # SYN_REPORT (0) -- +6837ms E: 20.492061 0003 0035 3366 # EV_ABS / ABS_MT_POSITION_X3366 E: 20.492061 0003 0036 2975 # EV_ABS / ABS_MT_POSITION_Y2975 E: 20.492061 0003 002f 0001 # EV_ABS / ABS_MT_SLOT 1 E: 20.492061 0003 0039 0528 # EV_ABS / ABS_MT_TRACKING_ID 528 E: 20.492061 0003 0035 4097 # EV_ABS / ABS_MT_POSITION_X4097 E: 20.492061 0003 0036 2508 # EV_ABS / ABS_MT_POSITION_Y2508 E: 20.492061 0001 014a 0001 # EV_KEY / BTN_TOUCH1 E: 20.492061 0003 0001 2975 # EV_ABS / ABS_Y2975 E: 20.492061 0003 0018 0041 # EV_ABS / ABS_PRESSURE 41 E: 20.492061 0003 001c 0005 # EV_ABS / ABS_TOOL_WIDTH 5 E: 20.492061 0001 0145 # EV_KEY / BTN_TOOL_FINGER 0 E: 20.492061 0001 014d 0001 # EV_KEY / BTN_TOOL_DOUBLETAP 1 E: 20.492061 # SYN_REPORT (0) -- +31ms E: 20.515281 0003 002f # EV_ABS / ABS_MT_SLOT 0 E: 20.515281 0003 0036 2971 # EV_ABS / ABS_MT_POSITION_Y2971 E: 20.515281 0003 002f 0001 # EV_ABS / ABS_MT_SLOT 1 E: 20.515281 0003 0035 4096 # EV_ABS / ABS_MT_POSITION_X4096 E: 20.515281 0003 0036 2509 # EV_ABS / ABS_MT_POSITION_Y2509 E: 20.515281 0003 4093 # EV_ABS / ABS_X4093 E: 20.515281 0003 0001 2967 # EV_ABS / ABS_Y2967 E: 20.515281 0003 0018 0043 # EV_ABS / ABS_PRESSURE 43 E: 20.515281 # SYN_REPORT (0) -- +23ms E: 20.538615 0003 002f # EV_ABS / ABS_MT_SLOT 0 E: 20.538615 0003 0036 2972 # EV_ABS / ABS_MT_POSITION_Y2972 E: 20.538615 0003 002f 0001 # EV_ABS / ABS_MT_SLOT 1 E: 20.538615 0003 0036 2566 # EV_ABS / ABS_MT_POSITION_Y2566 E: 20.538615 0003 4094 # EV_ABS / ABS_X4094 E: 20.538615 0003 0001 2978 # EV_ABS / ABS_Y2978 E: 20.538615 # SYN_REPORT (0) -- +23ms E: 20.550366 0003 002f # EV_ABS / ABS_MT_SLOT 0 E: 20.550366 0003 0035 3328 # EV_ABS / ABS_MT_POSITION_X3328 E: 20.550366 0003 0036 3129 # EV_ABS / ABS_MT_POSITION_Y3129 E: 20.550366 0003 002f 0001 # EV_ABS / ABS_MT_SLOT 1 E: 20.550366 0003 0039 -001 # EV_ABS / ABS_MT_TRACKING_ID -1 E
[Wayland-bugs] [Bug 105472] Hysteresis inappropriately turned back on for my hardware after being off for months
https://bugs.freedesktop.org/show_bug.cgi?id=105472 --- Comment #4 from Nate Graham --- I understand. It's just frustrating to still be wrestling with this issue a year and a half later, after the herculean effort you've put in to make it work. Hysteresis is just so frustrating with my hardware that it makes me want to chuck the computer out a window. Anyway, I'm done grousing and am ready to help! :) -- 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 105485] Add hwdb entry for X280 trackpoint (too fast)
https://bugs.freedesktop.org/show_bug.cgi?id=105485 Bug ID: 105485 Summary: Add hwdb entry for X280 trackpoint (too fast) Product: Wayland Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: libinput Assignee: wayland-bugs@lists.freedesktop.org Reporter: benja...@sipsolutions.net The trackpoint on the X280 is too fast. I first thought that adding an entry to the systemd hwdb is correct, but changing the acceleration to 64 there improves things only until libinput also reads the property. https://github.com/systemd/systemd/pull/8442 has the relevant matching rules for the machine. The libinput-measure-trackpoint-range utility seems to suggest a value of 70 for the machine. Though, to be honest, it is hard to tell how much one is supposed to press. Doesn't feel perfect, but I am not a big trackpoint user, so might be misinterpreting things. Rule: libinput:name:*ALPS TrackPoint*:svnLENOVO:*:pvrThinkPadX280:* LIBINPUT_ATTR_TRACKPOINT_RANGE=70 -- 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 105447] Two-finger scrolling broken in 1.10.2
https://bugs.freedesktop.org/show_bug.cgi?id=105447 --- Comment #13 from Mantas Mikulėnas --- (In reply to Peter Hutterer from comment #12) > So it works on master now? Yes, master has no scrolling problems. -- 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 105409] Touchpad deadzone on Razer Blade Stealth
https://bugs.freedesktop.org/show_bug.cgi?id=105409 --- Comment #19 from Benjamin Tissoires --- The problem here is that the touchpad sends events with a confidence of 0. This usually means the touchpad considers the touch to be a palm. Currently hid-multitouch ignores such events so that's why the kernel filter them out. Theoretically, we could forward such events with the tool MT_TOOL_PALM, but IIRC we already discussed about that and this might break user space which doesn't expect the ABS_MT_TOOL to change. -- 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
