xf86-input-synaptics issueshttps://gitlab.freedesktop.org/xorg/driver/xf86-input-synaptics/-/issues2018-08-10T20:59:21Zhttps://gitlab.freedesktop.org/xorg/driver/xf86-input-synaptics/-/issues/1AreaBottomEdge is not always ignored and sometimes causes other touches to be...2018-08-10T20:59:21ZBugzilla Migration UserAreaBottomEdge is not always ignored and sometimes causes other touches to be ignored## Submitted by Jeremy Huddleston Sequoia
Assigned to **Peter Hutterer `@whot`**
**[Link to original bug (#66532)](https://bugs.freedesktop.org/show_bug.cgi?id=66532)**
## Description
I have a clickpad, and I'm trying to get synap...## Submitted by Jeremy Huddleston Sequoia
Assigned to **Peter Hutterer `@whot`**
**[Link to original bug (#66532)](https://bugs.freedesktop.org/show_bug.cgi?id=66532)**
## Description
I have a clickpad, and I'm trying to get synaptics to behave well with it.
I really want an "IgnoreThumb" option which would allow me to have one finger (my thumb) pressing down on the button while the other finger drags (eg an icon).
To approximate that, I decided to try defining AreaBottomEdge (to 85%). If I move my finger into that region, the mouse cursor stops moving. Great. The only problem is that if I have a finger in that region, *ALL* movement is ignored (not just the one within that region).
For example:
1) If I am moving my finger in the region above the bottom, the cursor will move, but as soon as I touch the bottom region with another finger, the cursor will stop moving, and scroll events will be generated instead (because it sees two fingers).
2) In the opposite case, if I start with one finger in the bottom region and then place another finger above it and start moving it, there is no cursor movement nor scroll events.
In both of those example cases, I would expect the touch in the AreaBottomEdge to be ignored and the movement above the edge to translate the cursor.
### Depends on
* [Bug 66534](https://bugs.freedesktop.org/show_bug.cgi?id=66534)https://gitlab.freedesktop.org/xorg/driver/xf86-input-synaptics/-/issues/3Cursor jumps when clicking while moving2018-08-10T20:59:32ZBugzilla Migration UserCursor jumps when clicking while moving## Submitted by Mike C. Fletcher
Assigned to **Peter Hutterer `@whot`**
**[Link to original bug (#94773)](https://bugs.freedesktop.org/show_bug.cgi?id=94773)**
## Description
This is running on a Kubuntu 15.10 (using the Neon pack...## Submitted by Mike C. Fletcher
Assigned to **Peter Hutterer `@whot`**
**[Link to original bug (#94773)](https://bugs.freedesktop.org/show_bug.cgi?id=94773)**
## Description
This is running on a Kubuntu 15.10 (using the Neon packages for KDE) with kernel 4.2.0-34-generic and synaptics driver version 1.8.2-1ubuntu1 and xorg version 1:7.7+7ubuntu4 .
This appears to at least be related to #87788, though with different hardware running on a very up-to-date machine (that report is from 2014). This is seen on a Dell XPS 15 9550 (early 2016 model with a fully multi-touch-capable touchpad) with the following reported in dmesg during boot:
[ 2.277771] psmouse serio1: synaptics: queried max coordinates: x [..5664], y [..4646]
[ 2.322865] psmouse serio1: synaptics: queried min coordinates: x [1278..], y [1206..]
[ 2.412838] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 0xf00123/0x840300/0x12e800/0x0, board id: 3125
, fw id: 1961136
[ 2.469331] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6
the issue occurs in the following case:
* move cursor with one finger in the trackpad area (to target a control)
* while moving, rest another finger in the "click button" area at the bottom of the touchpad (preparing to click)
* lift the "moving" finger while clicking the button-area finger
It can also be produced with left-to-right and bottom to top offsets by rapidly switching between fingers used to move (i.e. separate fingers and "rock" between them), but obviously the "click with the mouse button" case is the most common (and frustrating) case. That is, it is possible to have the touchpad register a "jump" without clicking in the "button" area, and the jump can occur in any direction, not just down.
This seems like it could be largely mitigated by looking for a jump of greater than a human would possibly be able to move on the trackpad in a given period of time and resetting the "last position" to current position, or better, issuing a mouse-up-mouse-down sequence for previous and current positions.
While it might still occur in the rare cases where the user was moving at the extreme bottom of the touchpad area, the jump would be far smaller (the jump is generally going all the way to the bottom of the screen in a single step and registering the clicks on the task-bar instead of the control targeted in client windows).
The evemu-record log of a jump looks like this, with the jump happening at 7.674717.
E: 7.635071 0000 0000 0000 # ------------ SYN_REPORT (0) ----------
E: 7.647477 0003 0036 2637 # EV_ABS / ABS_MT_POSITION_Y 2637
E: 7.647477 0003 003a 0053 # EV_ABS / ABS_MT_PRESSURE 53
E: 7.647477 0003 0001 2637 # EV_ABS / ABS_Y 2637
E: 7.647477 0003 0018 0053 # EV_ABS / ABS_PRESSURE 53
E: 7.647477 0000 0000 0000 # ------------ SYN_REPORT (0) ----------
E: 7.659907 0003 0035 3289 # EV_ABS / ABS_MT_POSITION_X 3289
E: 7.659907 0003 0036 2639 # EV_ABS / ABS_MT_POSITION_Y 2639
E: 7.659907 0003 003a 0051 # EV_ABS / ABS_MT_PRESSURE 51
E: 7.659907 0003 0000 3289 # EV_ABS / ABS_X 3289
E: 7.659907 0003 0001 2639 # EV_ABS / ABS_Y 2639
E: 7.659907 0003 0018 0051 # EV_ABS / ABS_PRESSURE 51
E: 7.659907 0000 0000 0000 # ------------ SYN_REPORT (0) ----------
E: 7.674717 0003 0036 2643 # EV_ABS / ABS_MT_POSITION_Y 2643
E: 7.674717 0003 003a 0043 # EV_ABS / ABS_MT_PRESSURE 43
E: 7.674717 0003 0001 2643 # EV_ABS / ABS_Y 2643
E: 7.674717 0003 0018 0043 # EV_ABS / ABS_PRESSURE 43
E: 7.674717 0000 0000 0000 # ------------ SYN_REPORT (0) ----------
E: 7.694278 0003 0035 2367 # EV_ABS / ABS_MT_POSITION_X 2367
E: 7.694278 0003 0036 4568 # EV_ABS / ABS_MT_POSITION_Y 4568
E: 7.694278 0003 003a 0025 # EV_ABS / ABS_MT_PRESSURE 25
E: 7.694278 0003 0000 2367 # EV_ABS / ABS_X 2367
E: 7.694278 0003 0001 4568 # EV_ABS / ABS_Y 4568
E: 7.694278 0003 0018 0025 # EV_ABS / ABS_PRESSURE 25
E: 7.694278 0000 0000 0000 # ------------ SYN_REPORT (0) ----------
E: 7.707251 0003 003a 0050 # EV_ABS / ABS_MT_PRESSURE 50
E: 7.707251 0003 0018 0050 # EV_ABS / ABS_PRESSURE 50
E: 7.707251 0000 0000 0000 # ------------ SYN_REPORT (0) ----------
E: 7.719144 0003 0035 2375 # EV_ABS / ABS_MT_POSITION_X 2375
E: 7.719144 0003 0036 4516 # EV_ABS / ABS_MT_POSITION_Y 4516
E: 7.719144 0003 003a 0057 # EV_ABS / ABS_MT_PRESSURE 57
Version: 7.7 (2012.06)https://gitlab.freedesktop.org/xorg/driver/xf86-input-synaptics/-/issues/6Crash on UpdateTouchState2018-08-10T20:59:50ZBugzilla Migration UserCrash on UpdateTouchState## Submitted by Marc
Assigned to **Peter Hutterer `@whot`**
**[Link to original bug (#101721)](https://bugs.freedesktop.org/show_bug.cgi?id=101721)**
## Description
Created attachment 132506
xorg log
Hello,
I noticed a bug on my ...## Submitted by Marc
Assigned to **Peter Hutterer `@whot`**
**[Link to original bug (#101721)](https://bugs.freedesktop.org/show_bug.cgi?id=101721)**
## Description
Created attachment 132506
xorg log
Hello,
I noticed a bug on my lenovo yoga 2 13 laptop. Seemingly random the x server kind of dies : it slows down really hard until I cannot do anything and have to force a restart. Here's the important part of the stacktrace :
[117119.110] (EE) BUG: triggered 'if (priv->num_active_touches == 0)'
[117119.110] (EE) BUG: ../../src/synaptics.c:2958 in UpdateTouchState()
[117119.110] (EE)
[117119.110] (EE) Backtrace:
[117119.111] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x56003cf28c8a]
[117119.111] (EE) 1: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f446b311000+0x4914) [0x7f446b315914]
[117119.111] (EE) 2: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f446b311000+0x6802) [0x7f446b317802]
[117119.111] (EE) 3: /usr/lib/xorg/Xorg (0x56003cd70000+0x1badfc) [0x56003cf2adfc]
[117119.111] (EE) 4: /usr/lib/xorg/Xorg (0x56003cd70000+0x1bd501) [0x56003cf2d501]
[117119.111] (EE) 5: /usr/lib/xorg/Xorg (0x56003cd70000+0x1bac56) [0x56003cf2ac56]
[117119.111] (EE) 6: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f4474cf0000+0x76da) [0x7f4474cf76da]
[117119.111] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (clone+0x5f) [0x7f4474a3117f]
[117119.111] (EE)
**Attachment 132506**, "xorg log":
[Xorg.1.log](/uploads/57f097c56ae84fe2a26e537866e06ef1/Xorg.1.log)https://gitlab.freedesktop.org/xorg/driver/xf86-input-synaptics/-/issues/9Commit 0a4cf80a0066 ("Drop touch events from the driver") breaks three/four f...2018-08-10T21:00:01ZBugzilla Migration UserCommit 0a4cf80a0066 ("Drop touch events from the driver") breaks three/four fingers gesture## Submitted by Kai-Heng Feng
Assigned to **Peter Hutterer `@whot`**
**[Link to original bug (#105743)](https://bugs.freedesktop.org/show_bug.cgi?id=105743)**
## Description
Unity 7 uses three fingers double tap to do application ...## Submitted by Kai-Heng Feng
Assigned to **Peter Hutterer `@whot`**
**[Link to original bug (#105743)](https://bugs.freedesktop.org/show_bug.cgi?id=105743)**
## Description
Unity 7 uses three fingers double tap to do application switch (alt + tab), four fingers tap to open Dash menu.
Both gesture stops working after commit 0a4cf80a0066.
Version: git