[Wayland-bugs] [Bug 105753] Logitech wireless touchpad hesitates or stops on Ubuntu
https://bugs.freedesktop.org/show_bug.cgi?id=105753 --- Comment #20 from stacktracer--- I'm stuck. "udevadm test" shows "LIBINPUT_ATTR_PALM_PRESSURE_THRESHOLD=500", but "libinput debug-events" shows "palm: pressure threshold is 130". -- 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 105753] Logitech wireless touchpad hesitates or stops on Ubuntu
https://bugs.freedesktop.org/show_bug.cgi?id=105753 --- Comment #18 from stacktracer--- Notably, the cursor still gets stuck when, and only when, "libinput measure" reports a max pressure above 130. It's very consistent. Maybe my 500 isn't taking effect after all. -- 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 98839] Somehow conditionalize hysteresis (hardware black/whitelist, device property introspection, user-exposed setting, etc)
https://bugs.freedesktop.org/show_bug.cgi?id=98839 --- Comment #100 from Daniel van Vugt--- Excellent, thanks. I had actually forgotten to report that hysteresis was breaking the X1 Carbon G5 again... -- 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 98839] Somehow conditionalize hysteresis (hardware black/whitelist, device property introspection, user-exposed setting, etc)
https://bugs.freedesktop.org/show_bug.cgi?id=98839 --- Comment #99 from Peter Hutterer--- https://lists.freedesktop.org/archives/wayland-devel/2018-April/038025.html -- 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 106204] Trackpad not precise on X1 carbon 6th gen
https://bugs.freedesktop.org/show_bug.cgi?id=106204 --- Comment #9 from Peter Hutterer--- no, the kernel doesn't do anything other than forward the events. If you switch to imps, the kernel doesn't switch the touchpad to touchpad mode so the firmware emulates a PS/2 compatible mouse. You can verify this by running evemu-record, you should see BTN_LEFT, etc. as well as REL_X/Y. It's more of a firmware bug in that the device is only ever tested with windows and if it works there, they ship it. If we don't have the same behaviour as the windows driver we trigger bugs that windows doesn't have to care about. as you could see from the libinput vs synaptics behaviour - different pointer acceleration suddenly shows up a bug that's effectively unfixable without emulating that behaviour (which can break other devices, yay). -- 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 105753] Logitech wireless touchpad hesitates or stops on Ubuntu
https://bugs.freedesktop.org/show_bug.cgi?id=105753 --- Comment #23 from Peter Hutterer--- commit 59eb10e593213403c301a5ce3fbd0a22b6e52efd Author: Peter Hutterer <> Date: Mon Apr 30 10:40:45 2018 +1000 util: allow for palm pressure > 255 so grabbing git master should work for running debug-events now -- 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 105753] Logitech wireless touchpad hesitates or stops on Ubuntu
https://bugs.freedesktop.org/show_bug.cgi?id=105753 --- Comment #21 from Peter Hutterer--- This may be caused by a peculiar behaviour of udevadm test: it shows the properties to be applied but only applies them when being run as root. So make sure to run as root if you want it to apply the properties too. Check with udevadm info if the property shows up there? If so but libinput doesn't detect it, then that's a bug in libinput somewhere. -- 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 105753] Logitech wireless touchpad hesitates or stops on Ubuntu
https://bugs.freedesktop.org/show_bug.cgi?id=105753 --- Comment #22 from Peter Hutterer--- Created attachment 139224 --> https://bugs.freedesktop.org/attachment.cgi?id=139224=edit 0001-util-allow-for-palm-pressure-255.patch Sorry, posted to quickly. This one is the reason it doesn't work, an artificial upper limit. -- 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 106286] NEW: Proposal for mouse scroll wheel disabling while middle click is held.
https://bugs.freedesktop.org/show_bug.cgi?id=106286 Peter Huttererchanged: What|Removed |Added CC||peter.hutte...@who-t.net Status|NEW |NEEDINFO --- Comment #1 from Peter Hutterer --- Can you post an example evemu-record of a sequence that's gone wrong? Like how many inadvertant clicks do you use usually get? Do you get the clicks before/after the wheel triggers the actual button? This is a tricky one for libinput because we don't have any user feedback and making this configurable is a bit pointless. Having it as a hw-specific quirk is easy enough but it will prevent wheel scrolling with the middle button down. Which means we'll likely need some extra heuristics like a threshold when we start scrolling. That again is hard to discover and likely to upset people. -- 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 105753] Logitech wireless touchpad hesitates or stops on Ubuntu
https://bugs.freedesktop.org/show_bug.cgi?id=105753 --- Comment #16 from stacktracer--- For me the palm threshold needs to be set to at least 300. It probably makes sense to set it even higher (maybe 500?), since this is a desktop touchpad -- separate device, not built into a laptop surface -- so accidental palm contact practically never happens. In a few minutes of regular usage, I've seen max pressures in the 70-260 range. Still trying put together a .hwdb file. The debug procedure page is not very specific about how to figure out the right values for the match line, so it may take me a while to figure those out. libinput version: 1.10.5-1 uname: Linux 4.16.3-1-ARCH #1 SMP PREEMPT Thu Apr 19 09:17:56 UTC 2018 x86_64 GNU/Linux.) -- 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 106313] weston freezes when mouse pointer moved to the left edge of the desktop.
https://bugs.freedesktop.org/show_bug.cgi?id=106313 anthonychanged: What|Removed |Added Hardware|Other |x86-64 (AMD64) -- 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 106310] crash backtrace
https://bugs.freedesktop.org/show_bug.cgi?id=106310 Bug ID: 106310 Summary: crash backtrace Product: Wayland Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: weston Assignee: wayland-bugs@lists.freedesktop.org Reporter: dpa-b...@aegee.org Weston 4.0 crashed with this backtrace: I use wayland-1.15.0 and wayland-protocols-1.13: #0 0x7fc64ce3f60a in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 set = {__val = {81926, 0, 140489700286272, 140489556020087, 140489700291456, 140489700504292, 64, 0, 2, 140489700284736, 1, 140489557871911, 140489700130880, 140489700130880, 21454416, 59648}} pid = tid = #1 0x7fc64ce406e1 in __GI_abort () at abort.c:79 save_stage = 1 act = {__sigaction_handler = {sa_handler = 0x30, sa_sigaction = 0x30}, sa_mask = {__val = {19337240, 80, 20, 18446744073709551152, 140489693846227, 206158430211, 1315717493, 140489695969600, 140489693846496, 140489695972304, 140489693846227, 27036704, 1315717491, 140489695969624, 140732477818496, 140732477818784}}, sa_flags = -715569536, sa_restorer = 0x1000} sigs = {__val = {32, 0 }} #2 0x7fc64ce809a7 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fc64cf83458 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 ap = {{gp_offset = 24, fp_offset = 0, overflow_arg_area = 0x7ffed55947b0, reg_save_area = 0x7ffed5594740}} fd = list = nlist = cp = written = #3 0x7fc64ce86d7a in malloc_printerr (str=str@entry=0x7fc64cf815d6 "corrupted double-linked list") at malloc.c:5350 #4 0x7fc64ce8a256 in _int_malloc (av=av@entry=0x7fc64d1b8c40 , bytes=bytes@entry=744) at malloc.c:3926 p = 0x7fc64ce3f60a <__GI_raise+202> iters = nb = 752 idx = bin = victim = size = victim_index = remainder = remainder_size = block = bit = map = fwd = bck = tcache_unsorted_count = tcache_nb = 752 tc_idx = 45 return_cached = __PRETTY_FUNCTION__ = "_int_malloc" #5 0x7fc64ce8c1e1 in __libc_calloc (n=n@entry=1, elem_size=elem_size@entry=744) at malloc.c:3436 av = oldtop = 0x1aa5200 p = bytes = 744 sz = 744 csz = oldtopsize = 1064448 mem = clearsize = nclears = d = hook = __PRETTY_FUNCTION__ = "__libc_calloc" #6 0x7fc64e6d4c98 in zalloc (size=744) at ./shared/zalloc.h:38 #7 0x7fc64e6d4c98 in weston_surface_create (compositor=compositor@entry=0x1281160) at libweston/compositor.c:459 #8 0x7fc64e6d8704 in compositor_create_surface (client=0x1943f40, resource=0x1483580, id=12) at libweston/compositor.c:3262 ec = 0x1281160 surface = #9 0x7fc64e2b060e in ffi_call_unix64 () at /usr/local/lib/../lib/libffi.so.6 #10 0x7fc64e2af8d9 in ffi_call () at /usr/local/lib/../lib/libffi.so.6 #11 0x7fc64e4bed0c in wl_closure_invoke (closure=0x19c2b50, flags=, target=, opcode=0, data=) at src/connection.c:996 cif = {abi = FFI_UNIX64, nargs = 3, arg_types = 0x7ffed5594a50, rtype = 0x7fc64e2b0a00 , bytes = 0, flags = 0} ffi_types = {0x7fc64e2b08e0 , 0x7fc64e2b08e0 , 0x7fc64e2b0960 , 0x7fc64e2b08e0 , 0x7fc64e2b0960 , 0x7fc64e2b0960 , 0x90, 0x50, 0x19944c0, 0x80, 0x19944b0, 0x7fc64e4c0990, 0x90, 0x7fc64ce8bced <__GI___libc_realloc+205>, 0x1c0, 0x7fc64d1b8c40 , 0x19c2e88, 0x80, 0x1943f70, 0x8, 0x7fc64e4c0990, 0x7fc64e4bdad3} ffi_args = {0x7ffed5594a20, 0x7ffed5594a28, 0x19c2b68, 0xc, 0x19c2b70, 0x7fc64e4bf9ef , 0xc, 0x7fc64e4c0e18, 0x7ffed5594ba8, 0x7fc64e4be731 , 0x19c2c2c, 0x19c2e70, 0x19c2c20, 0x19c2c2c, 0x19c2b50, 0x7fc64e4bea20 , 0x7ffed5594ba0, 0x7fc64e4b9e53 , 0x19c2b50, 0x7fc64e6c4b60 , 0x4a, 0x148356e} implementation = #12 0x7fc64e4bb69f in wl_client_connection_data (fd=, mask=, data=0x1943f40) at src/wayland-server.c:420 client = 0x1943f40 connection = resource = 0x1483580 object = 0x1483580 closure = 0x19c2b50 message = 0x7fc64e6c4b60 p = {4, 786432} resource_flags = opcode = 0 size = since = len = #13 0x7fc64e4bcf72 in wl_event_loop_dispatch (loop=0x1278ee0, timeout=timeout@entry=-1) at src/event-loop.c:641 ep = {{events = 1, data = {ptr = 0x19b0720, fd = 26937120, u32 = 26937120, u64 = 26937120}}, {events = 1, data = {ptr = 0x1427b40, fd = 21134144, u32 = 21134144, u64 =
[Wayland-bugs] [Bug 105753] Logitech wireless touchpad hesitates or stops on Ubuntu
https://bugs.freedesktop.org/show_bug.cgi?id=105753 --- Comment #17 from stacktracer--- Hmm, no joy yet. I increased the palm threshold, by putting the following in /etc/udev/hwdb.d/99-logitech-wireless-touchpad-palm.hwdb: libinput:touchpad:input:b0003v046Dp4011* LIBINPUT_ATTR_PALM_PRESSURE_THRESHOLD=500 I did a full system reboot afterwards. Both "udevadm test" and "libinput measure touchpad-pressure" now report the palm threshold to be 500. However, the mouse cursor still gets stuck, just like before. "libinput measure touchpad-threshold" used to print "palm" at the end of the line when the cursor would get stuck. Now that the palm threshold is higher it no longer prints "palm" ... but the cursor still gets stuck just like before. Bummer. -- 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 105753] Logitech wireless touchpad hesitates or stops on Ubuntu
https://bugs.freedesktop.org/show_bug.cgi?id=105753 --- Comment #19 from stacktracer--- Indeed: $ libinput debug-events --device /dev/input/event14 --verbose event14 - Logitech Wireless Touchpad: is tagged by udev as: Touchpad event14 - using pressure-based touch detection (5:6) event14 - palm: pressure threshold is 130 event14 - Logitech Wireless Touchpad: device is a touchpad ... Not sure where to go next. I'll try the udevadm update steps again, but I'm not optimistic. Suggestions appreciated. -- 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