[Wayland-bugs] [Bug 105043] 3-fingers touch occasionally fails to get detected
https://bugs.freedesktop.org/show_bug.cgi?id=105043 --- Comment #6 from Peter Hutterer --- whoops. that was supposed to be: [1] we *decide* whether a detected touch is a logical touch based on pressure/size to filter out palms but also light/hovering touches. but that still requires the touchpad to detect them first. -- 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 #5 from Hi-Angel --- (In reply to Peter Hutterer from comment #4) > libinput converts the touches into relative motion, or taps, or scrolling, > etc. But libinput cannot *detect* the touches [1], that has to be done by > the firmware. The kernel sets BTN_TOOL_FINGER, BTN_TOOL_DOUBLETAP and > BTN_TOOL_TRIPLETAP together with the slot data (which is what we use where > available), so that's the easiest and quickest way to check if a finger is > detected at all. You probably wanted to add a link, but forgot :) > Easiest way to verify if that is (part of) the issue is running evemu-record > |grep BTN_TOOL and checking that output while tapping. If you don't see > TRIPLETAP every time you three-finger tap, then that's the source of that. > Slower tapping can help, might be you're really too fast for the device to > detect contact. > > Without that data, we can't do that much. So in this particular recording, > the only one we could fix in libinput is the one that's also detected as a > palm, but not the other two. Okay, thanks for the idea — when that gonna happen again, I'll try to check what BTN_TOOL* events produced upon triple-tapping, perhaps is there some pattern showing that something weird is going on. I shall note that triple-tap for some reason stops working occasionally, and then usually it don't work for a number of consequent triple-taps. Slowing down, holding fingers on the touchpad, etc, doesn't help 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 105043] 3-fingers touch occasionally fails to get detected
https://bugs.freedesktop.org/show_bug.cgi?id=105043 --- Comment #4 from Peter Hutterer --- libinput converts the touches into relative motion, or taps, or scrolling, etc. But libinput cannot *detect* the touches [1], that has to be done by the firmware. The kernel sets BTN_TOOL_FINGER, BTN_TOOL_DOUBLETAP and BTN_TOOL_TRIPLETAP together with the slot data (which is what we use where available), so that's the easiest and quickest way to check if a finger is detected at all. Easiest way to verify if that is (part of) the issue is running evemu-record |grep BTN_TOOL and checking that output while tapping. If you don't see TRIPLETAP every time you three-finger tap, then that's the source of that. Slower tapping can help, might be you're really too fast for the device to detect contact. Without that data, we can't do that much. So in this particular recording, the only one we could fix in libinput is the one that's also detected as a palm, but not the other two. -- 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 #3 from Hi-Angel --- (In reply to Peter Hutterer from comment #2) > are all these 3-finger taps in that recording? There are only two > BTN_TOOL_TRIPLETAP events in here, the first of which is detected as palm > (edge), the second one (last tap in the recording) is, correctly, a middle > click. > > If there are more than two 3-finger taps in this recording, then one issue > is with the hardware not even detecting the three fingers. Yeah, I remember there were at least 3 3-finger taps besides the last one (i.e. 4 3-finger taps overall); and at least one of them was detected as a 2-finger tap. So, isn't detection done by libinput itself? Can it be done by libinput instead of firmware? -- 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 Peter Hutterer changed: What|Removed |Added CC||peter.hutte...@who-t.net Status|NEW |NEEDINFO --- Comment #2 from Peter Hutterer --- are all these 3-finger taps in that recording? There are only two BTN_TOOL_TRIPLETAP events in here, the first of which is detected as palm (edge), the second one (last tap in the recording) is, correctly, a middle click. If there are more than two 3-finger taps in this recording, then one issue is with the hardware not even detecting the three fingers. -- 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 105050] DualShock 4 Touchpad not working with libinput.
https://bugs.freedesktop.org/show_bug.cgi?id=105050 Peter Hutterer changed: What|Removed |Added CC||peter.hutte...@who-t.net Status|NEW |NEEDINFO --- Comment #1 from Peter Hutterer --- Please attach an evemu-describe from that device, that will at least tell us *why* it doesn't work. But generally, the answer right now is likely: libinput does not support joysticks/gamepads and just outright ignores those. The touchpad on the p4 controller is a bit of a special case but it's probably tagged as joystick and thus ignored. -- 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 105024] Elan1200 touchpad not well managed
https://bugs.freedesktop.org/show_bug.cgi?id=105024 --- Comment #2 from PapsOu --- Here a small log of i2c_hid.debug=1 kernel option : parts with « input: ff » seems to fit with the cursor jumps detected. févr. 12 21:19:35 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: ff févr. 12 21:19:35 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 46 05 f8 04 73 94 01 00 12 44 00 00 févr. 12 21:19:35 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 3b 05 eb 04 c7 95 01 00 1b 44 00 00 févr. 12 21:19:35 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 1f 05 df 04 c5 97 01 00 1f 54 00 00 févr. 12 21:19:35 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: ff févr. 12 21:19:35 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 06 05 d9 04 c3 99 01 00 27 54 00 00 févr. 12 21:19:35 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 03 05 f3 04 0d 9b 01 00 2a 54 00 00 févr. 12 21:19:35 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 fe 04 21 05 93 9c 01 00 29 54 00 00 févr. 12 21:19:35 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: ff févr. 12 21:19:35 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 e6 04 6b 05 f9 9f 01 00 29 64 00 00 févr. 12 21:19:35 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 ed 04 95 05 ed a1 01 00 29 54 00 00 févr. 12 21:19:35 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 ef 04 9e 05 47 a2 01 00 29 54 00 00 févr. 12 21:19:35 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 f9 04 bd 05 a5 a3 01 00 27 54 00 00 févr. 12 21:19:35 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 fb 04 c3 05 ff a3 01 00 25 54 00 00 févr. 12 21:19:35 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 06 05 d6 05 cb a5 01 00 24 54 00 00 févr. 12 21:19:35 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 08 05 e1 05 29 a7 01 00 16 44 00 00 févr. 12 21:19:35 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 07 05 e9 05 d3 a7 01 00 10 54 00 00 févr. 12 21:19:37 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 ef 04 9e 04 25 e2 01 00 16 54 00 00 févr. 12 21:19:37 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: ff févr. 12 21:19:37 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 9c 04 97 04 67 e6 01 00 24 55 00 00 févr. 12 21:19:37 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 89 04 96 04 11 e7 01 00 24 54 00 00 févr. 12 21:19:37 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 80 04 94 04 6b e7 01 00 24 54 00 00 févr. 12 21:19:37 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 66 04 90 04 bf e8 01 00 27 54 00 00 févr. 12 21:19:37 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 59 04 8c 04 69 e9 01 00 27 54 00 00 févr. 12 21:19:37 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 2e 04 7e 04 53 eb 01 00 25 55 00 00 févr. 12 21:19:37 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 ff 03 6e 04 a7 ec 01 00 25 54 00 00 févr. 12 21:19:37 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 e8 03 65 04 51 ed 01 00 27 54 00 00 févr. 12 21:19:37 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 bc 03 54 04 ff ee 01 00 27 54 00 00 févr. 12 21:19:37 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 b4 03 50 04 6d ef 01 00 27 44 00 00 févr. 12 21:19:37 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 b0 03 4c 04 b3 ef 01 00 27 44 00 00 févr. 12 21:19:37 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 a6 03 46 04 7b f0 01 00 27 44 00 00 févr. 12 21:19:37 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: ff févr. 12 21:19:37 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 7b 03 38 04 eb f3 01 00 1d 44 00 00 févr. 12 21:19:37 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 79 03 37 04 95 f4 01 00 12 43 00 00 févr. 12 21:19:37 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: ff févr. 12 21:19:37 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 01 79 03 37 04 8f f5 01 00 0e 43 00 00 févr. 12 21:19:39 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: ff févr. 12 21:19:39 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: ff févr. 12 21:19:39 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 e5 03 5b 03 a5 48 01 00 1d 55 00 00 févr. 12 21:19:40 localhost.localdomain kernel: i2c_hid i2c-ELAN1200:00: input: 10 00 04 03 16 04 3b 03 81 49 01 00 1f 44 00 00 févr. 12 21:19:40 localhost.lo
[Wayland-bugs] [Bug 786694] wayland: fix fontconfig monitoring
https://bugzilla.gnome.org/show_bug.cgi?id=786694 Martin Blanchard changed: What|Removed |Added Attachment #365988|0 |1 is obsolete|| Bastien Nocera changed: What|Removed |Added CC||bugzi...@hadess.net --- Comment #7 from Martin Blanchard --- Created attachment 368188 --> https://bugzilla.gnome.org/attachment.cgi?id=368188&action=edit Introduce org.gnome.SettingsDaemon.FontConfig (timestamp as int64) Second version: time is represented as int64 and valued using g_get_real_time(). Comments and feedbacks welcome. --- Comment #8 from Bastien Nocera --- It's too late to land this for GNOME 3.28. The gnome-shell patch will need reviewing before this can land, assuming the code is correct. At a glance, you'll want to go through the patch and remove the unnecessary whitespace changes. -- 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 793062] [Wayland] Crash under gdk_wayland_window_attach_image()
https://bugzilla.gnome.org/show_bug.cgi?id=793062 --- Comment #15 from Olivier Fourdan --- I am not 100% sure about the leak, I've left FF running a few times overnight and that did not happen. The patch fixes the issue, I reckon. -- 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 793062] [Wayland] Crash under gdk_wayland_window_attach_image()
https://bugzilla.gnome.org/show_bug.cgi?id=793062 --- Comment #14 from Martin Stransky --- I'll check that patch, Thanks. The leaking is interesting, I'll check that. -- 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
