[Wayland-bugs] [Bug 105203] Update to 1.10.0 makes cursor "vibrate" when using touchpad
https://bugs.freedesktop.org/show_bug.cgi?id=105203 Bug ID: 105203 Summary: Update to 1.10.0 makes cursor "vibrate" when using touchpad Product: Wayland Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: libinput Assignee: wayland-bugs@lists.freedesktop.org Reporter: y...@masson-informatique.fr Hi, I am using Debian testing on a Dell E7440, which just switched libinput from 1.9.4-2 to 1.10.0-1. When I touch the touchpad, without moving the finger, the cursor vibrates. It does not depend on the pressure. Cursor does not move much, but it makes it difficult to click on precise areas. Do not hesitate to ask if you need more information. Best regards, Yvan $ xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ xwayland-pointer:13 id=6[slave pointer (2)] ⎜ ↳ xwayland-relative-pointer:13 id=7[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ xwayland-keyboard:13 id=8[slave keyboard (3)] $ xinput list-props 2 Device 'Virtual core pointer': Device Enabled (119): 1 Coordinate Transformation Matrix (121): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 $ xinput list-props 4 Device 'Virtual core XTEST pointer': Device Enabled (119): 1 Coordinate Transformation Matrix (121): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 XTEST Device (238): 1 $ xinput list-props 6 Device 'xwayland-pointer:13': Device Enabled (119): 1 Coordinate Transformation Matrix (121): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (244): 0 Device Accel Constant Deceleration (245): 1.00 Device Accel Adaptive Deceleration (246): 1.00 Device Accel Velocity Scaling (247):10.00 $ udevadm info /sys/class/input/event2 P: /devices/platform/i8042/serio1/input/input2/event2 N: input/event2 S: input/by-path/platform-i8042-serio-1-event-mouse E: DEVLINKS=/dev/input/by-path/platform-i8042-serio-1-event-mouse E: DEVNAME=/dev/input/event2 E: DEVPATH=/devices/platform/i8042/serio1/input/input2/event2 E: ID_BUS=i8042 E: ID_INPUT=1 E: ID_INPUT_HEIGHT_MM=43 E: ID_INPUT_TOUCHPAD=1 E: ID_INPUT_TOUCHPAD_INTEGRATION=internal E: ID_INPUT_WIDTH_MM=95 E: ID_PATH=platform-i8042-serio-1 E: ID_PATH_TAG=platform-i8042-serio-1 E: ID_SERIAL=noserial E: LIBINPUT_DEVICE_GROUP=11/2/8:isa0060/serio1 E: LIBINPUT_MODEL_ALPS_TOUCHPAD=1 E: LIBINPUT_MODEL_FIRMWARE_VERSION=310 E: MAJOR=13 E: MINOR=66 E: SUBSYSTEM=input E: USEC_INITIALIZED=50227224 $ cat /sys/class/dmi/id/modalias dmi:bvnDellInc.:bvrA22:bd10/18/2017:svnDellInc.:pnLatitudeE7440:pvr00:rvnDellInc.:rn091TRH:rvrA00:cvnDellInc.:ct9:cvr: -- 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 --- Comment #6 from Simon --- Here is a record with the requested simple move sequence (excluding multitouch or click events): # EVEMU 1.3 # Kernel: 4.15.3-gentoo # DMI: dmi:bvnLENOVO:bvr83ET76WW(1.46):bd07/05/2013:svnLENOVO:pn4180CE9:pvrThinkPadT420:rvnLENOVO:rn4180CE9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: # Input device name: "Sony Interactive Entertainment Wireless Controller Touchpad" # Input device ID: bus 0x03 vendor 0x54c product 0x9cc version 0x8111 # Supported events: # Event type 0 (EV_SYN) # Event code 0 (SYN_REPORT) # Event code 1 (SYN_CONFIG) # Event code 2 (SYN_MT_REPORT) # Event code 3 (SYN_DROPPED) # Event code 4 ((null)) # Event code 5 ((null)) # Event code 6 ((null)) # Event code 7 ((null)) # Event code 8 ((null)) # Event code 9 ((null)) # Event code 10 ((null)) # Event code 11 ((null)) # Event code 12 ((null)) # Event code 13 ((null)) # Event code 14 ((null)) # Event code 15 (SYN_MAX) # Event type 1 (EV_KEY) # Event code 272 (BTN_LEFT) # Event code 325 (BTN_TOOL_FINGER) # Event code 330 (BTN_TOUCH) # Event code 333 (BTN_TOOL_DOUBLETAP) # Event type 3 (EV_ABS) # Event code 47 (ABS_MT_SLOT) # Value1 # Min 0 # Max 1 # Fuzz 0 # Flat 0 # Resolution 0 # Event code 53 (ABS_MT_POSITION_X) # Value0 # Min 0 # Max 1920 # Fuzz 0 # Flat 0 # Resolution 0 # Event code 54 (ABS_MT_POSITION_Y) # Value0 # Min 0 # Max942 # Fuzz 0 # Flat 0 # Resolution 0 # Event code 57 (ABS_MT_TRACKING_ID) # Value0 # Min 0 # Max 65535 # Fuzz 0 # Flat 0 # Resolution 0 # Properties: # Property type 0 (INPUT_PROP_POINTER) # Property type 2 (INPUT_PROP_BUTTONPAD) N: Sony Interactive Entertainment Wireless Controller Touchpad I: 0003 054c 09cc 8111 P: 05 00 00 00 00 00 00 00 B: 00 0b 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 01 00 00 00 00 00 B: 01 20 24 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 02 00 00 00 00 00 00 00 00 B: 03 00 00 00 00 00 80 60 02 B: 04 00 00 00 00 00 00 00 00 B: 05 00 00 00 00 00 00 00 00 B: 11 00 00 00 00 00 00 00 00 B: 12 00 00 00 00 00 00 00 00 B: 14 00 00 00 00 00 00 00 00 B: 15 00 00 00 00 00 00 00 00 B: 15 00 00 00 00 00 00 00 00 A: 2f 0 1 0 0 0 A: 35 0 1920 0 0 0 A: 36 0 942 0 0 0 A: 39 0 65535 0 0 0 # Waiting for events # E: 0.01 0003 002f # EV_ABS / ABS_MT_SLOT 0 E: 0.01 0003 0039 0004 # EV_ABS / ABS_MT_TRACKING_ID 4 E: 0.01 0003 0035 0636 # EV_ABS / ABS_MT_POSITION_X636 E: 0.01 0003 0036 0259 # EV_ABS / ABS_MT_POSITION_Y259 E: 0.01 0001 014a 0001 # EV_KEY / BTN_TOUCH1 E: 0.01 0001 0145 0001 # EV_KEY / BTN_TOOL_FINGER 1 E: 0.01 # SYN_REPORT (0) -- +0ms E: 0.011912 0003 0035 0637 # EV_ABS / ABS_MT_POSITION_X637 E: 0.011912 # SYN_REPORT (0) -- +11ms E: 0.016015 0003 0035 0638 # EV_ABS / ABS_MT_POSITION_X638 E: 0.016015 0003 0036 0260 # EV_ABS / ABS_MT_POSITION_Y260 E: 0.016015 # SYN_REPORT (0) -- +5ms E: 0.019961 0003 0035 0640 # EV_ABS / ABS_MT_POSITION_X640 E: 0.019961 # SYN_REPORT (0) -- +3ms E: 0.023989 0003 0035 0642 # EV_ABS / ABS_MT_POSITION_X642 E: 0.023989 0003 0036 0261 # EV_ABS / ABS_MT_POSITION_Y261 E: 0.023989 # SYN_REPORT (0) -- +4ms E: 0.031916 0003 0035 0644 # EV_ABS / ABS_MT_POSITION_X644 E: 0.031916 # SYN_REPORT (0) -- +8ms E: 0.035969 0003 0035 0647 # EV_ABS / ABS_MT_POSITION_X647 E: 0.035969 # SYN_REPORT (0) -- +4ms E: 0.039903 0003 0035 0650 # EV_ABS / ABS_MT_POSITION_X650 E: 0.039903 0003 0036 0262 # EV_ABS / ABS_MT_POSITION_Y262 E: 0.039903 # SYN_REPORT (0) -- +4ms E: 0.043958 0003 0035 0653 # EV_ABS / ABS_MT_POSITION_X653 E: 0.043958 # SYN_REPORT (0) -- +4ms E: 0.051985 0003 0035 0659 # EV_ABS / ABS_MT_POSITION_X659 E: 0.051985 # SYN_REPORT (0) -- +8ms E: 0.
[Wayland-bugs] [Bug 105050] DualShock 4 Touchpad not working with libinput.
https://bugs.freedesktop.org/show_bug.cgi?id=105050 --- Comment #7 from Simon --- I thought I included everything related to the touchpad from the xorg.log but of course I can also upload a full log, do you want TWO full logs with evdev AND libinput driver? -- 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 104990] XPS13 L322X touchpad laggy
https://bugs.freedesktop.org/show_bug.cgi?id=104990 --- Comment #7 from VF --- I found these additional information in Dell XP13-L322X specifications : Touchpad Resolution: 250 cpi Size: Width: 96,8 mm (3,81") Heitgh: 58,8 mm (2,31") Please notice that I was not able to identify the device on Cypress web site, and that resolution information supplied by Dell for the L322X is very different than the one they give for the next very closely marketed model (XPS13-9333), which is: Touchpad Resolution: Horizontal: 1275 dpi Vertical: 1656 dpi Size (same as L322X): Width: 96,8 mm (3,81") Heitgh: 58,8 mm (2,31") -- 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 --- Comment #8 from Simon --- Here is a full Xorg.0.log trying libinput as ds4 touchpad driver: https://paste.pound-python.org/show/4Yu2zjQCcW7dmJnHxVbs/ -- 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 --- Comment #9 from Simon --- I see the other touchpad is actually recognized.. "event5 - (II) SynPS/2 Synaptics TouchPad: (II) is tagged by udev as: Touchpad" So probably libinput doesn't recognize the ds4 touchpad because it has no ID_INPUT_TOUCHPAD set!? -- 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 786694] wayland: fix fontconfig monitoring
https://bugzilla.gnome.org/show_bug.cgi?id=786694 Bastien Nocera changed: What|Removed |Added Attachment #368734|none|needs-work status|| --- Comment #12 from Bastien Nocera --- Review of attachment 368734: 1) Get rid of the array 2) Every time a timestamp change has happened, queue sending the new value for half-a-second (or a second?), reschedule if a new timestamp arrives in that time 3) Don't use g_get_real_time() ::: plugins/xsettings/gsd-xsettings-manager.c @@ +80,3 @@ +static const gchar introspection_xml[] = +"" +" " Is this really the name of the interface we want to use? What about GTK+ apps under other Wayland desktops? @@ +284,3 @@ GSettings *plugin_settings; FcMonitor *fontconfig_monitor; +GArray*fontconfig_timestamps; I've stared at the code for a long while, and can't figure out why you need to send a "changed" signal for each and every fontconfig timestamp change. Why do that? You could just keep the last one, and send it out when it changes, or aggregate/coalesce the changes into one event if the changes are too close together. You need to remember that this would wake up every single GTK+ program, so less notifications is better. @@ +1189,3 @@ GList *list, *l; const char *session; +gint64 timestamp = g_get_real_time (); You shouldn't user g_get_real_time(), this will break if the time on the machine is changed. Any reason why g_get_monotonic_time() can't be used? @@ +1453,3 @@ +manager = GNOME_XSETTINGS_MANAGER (user_data); + +if (manager->priv->dbus_connection == NULL) This isn't necessary, you get a connection in the arguments of the function above, and you don't use this variable anyway. -- 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 786693] wayland: fix fontconfig monitoring
https://bugzilla.gnome.org/show_bug.cgi?id=786693
Bastien Nocera changed:
What|Removed |Added
Attachment #368197|accepted-commit_now |needs-work
status||
--- Comment #5 from Bastien Nocera ---
Review of attachment 368197:
I don't think this is a good enough interface for GTK+ to use, but best discuss
it in a location where it will be implemented (in gnome-settings-daemon)
::: gdk/wayland/gdkscreen-wayland.c
@@ +919,3 @@
+ if (proxy == NULL)
+{
+ if (error != NULL)
This will warn for every GTK+ app running under a non-GNOME Wayland server.
@@ +946,3 @@
+screen_wayland->fc_settings.timestamp = (guint)timestamp;
+ else if (timestamp > G_MAXUINT)
+g_warning ("Could not handle fontconfig init: timestamp too long");
too long?
@@ +975,3 @@
+G_DBUS_PROXY_FLAGS_NONE,
+NULL,
+GSD_DBUS_FONTCONFIG_NAME,
This is highly GNOME specific.
--
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 786694] wayland: fix fontconfig monitoring
https://bugzilla.gnome.org/show_bug.cgi?id=786694 --- Comment #13 from Bastien Nocera --- The XSettings in the xsettings plugin are either: - in GSettings, and GTK+ will read those directly under Wayland - hardcoded in gnome-settings-daemon, for older versions of GTK+, and hardcoded in newer versions of GTK+ 3.x - "computed" in the xsettings plugin Those last ones are what we're interested in here. They are: - fontconfig timestamps (Fontconfig/Timestamp) - whether to enable animations (used for remote displays, Gtk/EnableAnimations) - GTK+ modules list (Gtk/Modules) - whether gnome-shell (and its builtin menu) is running (Gtk/ShellShowsAppMenu) - a number of font and DPI settings (see xft_settings_set_xsettings()) That last two are handled directly in GTK+ in Wayland talking to the compositor and checking its capabilities, or in gdk/wayland/gdkscreen-wayland.c. Which leaves us with those first 3 settings (for now). So, on top of the fontconfig specific changes above, it would be nice if: - the D-Bus name showed that the settings are GTK+ specific, say "org.gtk.Settings" - also export Gtk/EnableAnimations and the modules list through D-Bus -- 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 786694] wayland: fix fontconfig monitoring
https://bugzilla.gnome.org/show_bug.cgi?id=786694 --- Comment #14 from Bastien Nocera --- Created attachment 368775 --> https://bugzilla.gnome.org/attachment.cgi?id=368775&action=edit xsettings: Expose monitored settings through D-Bus A number of things that gnome-settings-daemon monitors for all the GTK+ applications aren't currently available for GTK+ Wayland clients, only through XSettings. As we already monitor fontconfig configurations, enabled GTK+ modules and whether applications should use animations, export those through a D-Bus interface. See https://bugzilla.gnome.org/show_bug.cgi?id=786693 Based on patch by Martin Blanchard -- 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 786694] wayland: fix fontconfig monitoring
https://bugzilla.gnome.org/show_bug.cgi?id=786694 --- Comment #15 from Bastien Nocera --- The patch above is completely untested, and the GTK+ patch needs rewriting. You might need to also apply the patch from bug 793721 for this one to apply. -- 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 786694] wayland: fix fontconfig monitoring
https://bugzilla.gnome.org/show_bug.cgi?id=786694 Bastien Nocera changed: What|Removed |Added Attachment #368734|0 |1 is obsolete|| -- 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 105203] Update to 1.10.0 makes cursor "vibrate" when using touchpad
https://bugs.freedesktop.org/show_bug.cgi?id=105203 Peter Hutterer changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE CC||peter.hutte...@who-t.net --- Comment #1 from Peter Hutterer --- *** This bug has been marked as a duplicate of bug 104828 *** -- 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 104985] Intuos paper generating button click on palm off
https://bugs.freedesktop.org/show_bug.cgi?id=104985 Peter Hutterer changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #2 from Peter Hutterer --- commit 2a378beab032d742770e24a6822378faa90cf1f6 Author: Peter Hutterer Date: Mon Feb 19 14:00:42 2018 +1000 touchpad: delay arbitration by 90ms after touch toggle -- 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 104828] Wobbly AlpsPS/2 ALPS DualPoint TouchPad
https://bugs.freedesktop.org/show_bug.cgi?id=104828 Peter Hutterer changed: What|Removed |Added CC||y...@masson-informatique.fr --- Comment #27 from Peter Hutterer --- *** Bug 105203 has been marked as a duplicate of this bug. *** -- 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 --- Comment #10 from Peter Hutterer --- fwiw, please attach anything longer than say 10 lines, otherwise it gets too difficult to find the real comments. and never use pastebins, they disappear randomly. we have bugzilla attachments for that. ok, checked the code again and you are right, it is likely missing ID_INPUT_TOUCHPAD, so libinput doesn't know what to do with the device, see http://who-t.blogspot.com/2015/06/libinput-and-lack-of-device-types.html for more details. question though is why it's missing, afaict from the udev builtin you should have both set (MOUSE and TOUCHPAD, which is a bug, but anyway). are you using a recent enough version of systemd? (not that that code has changed in ages...) You'll likely find that once the ID_INPUT_TOUCHPAD tag is set, it'll start working, so this needs to move to udev to figure out why it isn't set in the first place. -- 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 --- Comment #11 from Peter Hutterer --- for the systemd bug, see: https://github.com/systemd/systemd/pull/8259 -- 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 103970] Apple Wireless Trackpad sensitivity too low
https://bugs.freedesktop.org/show_bug.cgi?id=103970 Daniel van Vugt changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WONTFIX |--- --- Comment #5 from Daniel van Vugt --- Bug confirmed (using libinput 1.10) now. I will collect the required 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 103970] Apple Magic Trackpad sensitivity too low (does not detect normal touches)
https://bugs.freedesktop.org/show_bug.cgi?id=103970 Daniel van Vugt changed: What|Removed |Added Summary|Apple Wireless Trackpad |Apple Magic Trackpad |sensitivity too low |sensitivity too low (does ||not detect normal touches) -- 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 103970] Apple Magic Trackpad sensitivity too low (does not detect normal touches)
https://bugs.freedesktop.org/show_bug.cgi?id=103970 --- Comment #6 from Daniel van Vugt --- $ sudo libinput measure touch-size Using Apple Wireless Trackpad: /dev/input/event15 Ready for recording data. Touch sizes used: 130:150 Palm size used: 800 Place a single finger on the device to measure touch size. Ctrl+C to exit Sequence: major: [ 0.. 92] minor: [ 0..148] Sequence: major: [ 0..102] minor: [ 0..156] Sequence: major: [ 0..102] minor: [ 0..168] Sequence: major: [ 0..124] minor: [ 0..200] Sequence: major: [ 0..120] minor: [ 0..192] Sequence: major: [ 0..124] minor: [ 0..204] $ sudo libinput measure touchpad-pressure Using Apple Wireless Trackpad: /dev/input/event15 Error: device does not have ABS_MT_PRESSURE -- 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 103970] Apple Magic Trackpad sensitivity too low (does not detect touches unless pressing hard)
https://bugs.freedesktop.org/show_bug.cgi?id=103970 Daniel van Vugt changed: What|Removed |Added Summary|Apple Magic Trackpad|Apple Magic Trackpad |sensitivity too low (does |sensitivity too low (does |not detect normal touches) |not detect touches unless ||pressing hard) -- 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 103970] Apple Magic Trackpad sensitivity too low (does not detect touches unless pressing hard)
https://bugs.freedesktop.org/show_bug.cgi?id=103970 Daniel van Vugt changed: What|Removed |Added See Also||https://launchpad.net/bugs/ ||1751190 -- 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 105108] Lenovo Yoga 11S touchpad is jittery
https://bugs.freedesktop.org/show_bug.cgi?id=105108 --- Comment #12 from Peter Hutterer --- Alright, https://github.com/whot/libinput/tree/wip/hysteresis-wobbles is the compiled branch for all the current hysteresis fixes. Please give it a test. This includes: * reducing to the fuzz * enabling hysteresis where fuzz != 0 * wobble detection from Hi-Angel [slightly modified by me, but the functionality is the same] * hysteresis fixes to work across both axes simultaneously The last one I'm not 100% sure about, I just finished the code and there may be a massive thinko. Tests and sanity-checks 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
[Wayland-bugs] [Bug 103970] Apple Magic Trackpad sensitivity too low (does not detect touches unless pressing hard)
https://bugs.freedesktop.org/show_bug.cgi?id=103970 Peter Hutterer changed: What|Removed |Added Status|REOPENED|NEEDINFO --- Comment #7 from Peter Hutterer --- Thanks. Unfortunately this isn't just a tool you can run once, you need to experiment with --touch-thresholds and --palm-threshold to figure out the right setting, it's an interactive tool. Make sure that when the thresholds are set, the 'down' and 'palm' tags show up correctly as you're interacting with the device. -- 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
