Bug 90688 - libinput trackpad issues
Summary: libinput trackpad issues
Status: RESOLVED DUPLICATE of bug 90731
Alias: None
Product: Wayland
Classification: Unclassified
Component: libinput (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Wayland bug list
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-27 22:40 UTC by Jon
Modified: 2015-06-01 23:33 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
udevadm output (137.22 KB, text/plain)
2015-05-29 01:01 UTC, Jon
Details
Using track nipple plus trying to scroll (64.05 KB, text/plain)
2015-05-30 02:31 UTC, Jon
Details
Only scrolling on the track pad (46.24 KB, text/plain)
2015-05-30 02:31 UTC, Jon
Details

Description Jon 2015-05-27 22:40:43 UTC
Moved from fedora 21 to fedora 22 and my trackpad now acts like there's jam in it. Two finger scrolling works, but occasionally doesn't notice my fingers for a few seconds. Some times the scroll gets buffered and happens after libinput kicks in and other times it doesn't. I'm not sure I can explain this in technical terms, but this is a huge regression from whatever did the job before libinput (xinput?). Hardware being used is a thinkpad x230.
Comment 1 Peter Hutterer 2015-05-28 06:00:41 UTC
previous driver was synaptics so if it gets unbearable you can install xorg-x11-drv-synaptics + xorg-x11-drv-evdev and remove xorg-x11-drv-libinput.

did you have a custom configuration section for your touchpad before? we have model-specific code for the x230 because the touchpad is essentially broken.

pls attach the output of udevadm info --export-db and the evemu-record output of one of these stuck sequences. Thanks.
Comment 2 Jon 2015-05-29 01:01:51 UTC
Created attachment 116128 [details]
udevadm output
Comment 3 Jon 2015-05-29 01:02:20 UTC
 Not sure what constitutes a custom configuration (I changed the speed via the gnome setting panel), but even on a fresh fedora 21 install everything just felt better (and honestly it was better than windows ever was). One thing I've noticed now is that I can't two finger scroll while also using the nipple mouse (which I was able to do before). The requested udevadm output is attached. Can you explain how to get the evemu output? I get a 'could not open device' error.

Thanks,
Jon
Comment 4 Peter Hutterer 2015-05-29 01:08:29 UTC
custom configuration would be either a xorg.conf or some xorg.conf.d snippets in /etc that aren't distribution provided. the gnome bits don't matter for this, since we know what they change ;)

evemu needs to be run as root, the device nodes aren't readable by the normal user (usually anyway).


(In reply to Jon from comment #3)
> One thing I've noticed now is that I can't two finger scroll while also using
> the nipple mouse (which I was able to do before).

you mean move the nipple mouse to move the pointer and use two-finger scrolling on the touchpad at the same time? this should work, I think, at least on all but the Lenovo *40 models. double check and file a separate bug for this please, it's easier to track it that way.
Comment 5 Jon 2015-05-29 01:11:33 UTC
Which device should I check? It gives me 0-14 as options. As for the nipple, yes I try to move the mouse pointer with one hand and two finger scroll with the other and it only accepts input from the nipple.
Comment 6 Peter Hutterer 2015-05-29 01:19:57 UTC
ok, please file a separate bug for that issue, should be easy to fix.

for the evemu output, pick the "SynPS/2 Synaptics TouchPad" device, that's your touchpad. probably /dev/input/event4, but that can change after reboots.
Comment 7 Jon 2015-05-29 01:25:32 UTC
Select the device event number [0-14]: 4   
# EVEMU 1.2
# Input device name: "SynPS/2 Synaptics TouchPad"
# Input device ID: bus 0x11 vendor 0x02 product 0x07 version 0x1b1
# 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 type 1 (EV_KEY)
#     Event code 272 (BTN_LEFT)
#     Event code 325 (BTN_TOOL_FINGER)
#     Event code 328 (BTN_TOOL_QUINTTAP)
#     Event code 330 (BTN_TOUCH)
#     Event code 333 (BTN_TOOL_DOUBLETAP)
#     Event code 334 (BTN_TOOL_TRIPLETAP)
#     Event code 335 (BTN_TOOL_QUADTAP)
#   Event type 3 (EV_ABS)
#     Event code 0 (ABS_X)
#       Value   3352
#       Min     1174
#       Max     5768
#       Fuzz       0
#       Flat       0
#       Resolution 65
#     Event code 1 (ABS_Y)
#       Value   2993
#       Min      790
#       Max     5062
#       Fuzz       0
#       Flat       0
#       Resolution 136
#     Event code 24 (ABS_PRESSURE)
#       Value      0
#       Min        0
#       Max      255
#       Fuzz       0
#       Flat       0
#       Resolution 0
#     Event code 28 (ABS_TOOL_WIDTH)
#       Value      0
#       Min        0
#       Max       15
#       Fuzz       0
#       Flat       0
#       Resolution 0
#     Event code 47 (ABS_MT_SLOT)
#       Value      0
#       Min        0
#       Max        1
#       Fuzz       0
#       Flat       0
#       Resolution 0
#     Event code 53 (ABS_MT_POSITION_X)
#       Value      0
#       Min     1174
#       Max     5768
#       Fuzz       0
#       Flat       0
#       Resolution 65
#     Event code 54 (ABS_MT_POSITION_Y)
#       Value      0
#       Min      790
#       Max     5062
#       Fuzz       0
#       Flat       0
#       Resolution 136
#     Event code 57 (ABS_MT_TRACKING_ID)
#       Value      0
#       Min        0
#       Max    65535
#       Fuzz       0
#       Flat       0
#       Resolution 0
#     Event code 58 (ABS_MT_PRESSURE)
#       Value      0
#       Min        0
#       Max      255
#       Fuzz       0
#       Flat       0
#       Resolution 0
# Properties:
#   Property  type 0 (INPUT_PROP_POINTER)
#   Property  type 2 (INPUT_PROP_BUTTONPAD)
N: SynPS/2 Synaptics TouchPad
I: 0011 0002 0007 01b1
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 e5 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 03 00 00 11 00 80 60 06
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: 00 1174 5768 0 0 65
A: 01 790 5062 0 0 136
A: 18 0 255 0 0 0
A: 1c 0 15 0 0 0
A: 2f 0 1 0 0 0
A: 35 1174 5768 0 0 65
A: 36 790 5062 0 0 136
A: 39 0 65535 0 0 0
A: 3a 0 255 0 0 0
################################
#      Waiting for events      #
################################
Comment 8 Jon 2015-05-29 01:26:33 UTC
I move the nipple around a bunch and the trackpad did show signs of life in the event capture. Just no scrolling. Other bug report is made as well.
Comment 9 Peter Hutterer 2015-05-29 03:23:29 UTC
sorry, wasn't clear: that is just the description of the touchpad, I'd need a buggy event sequence so I can replay it here. so pls leave it running, try to reproduce the bug (with as few events as possible), then attach the file here (as attachment please).
Comment 10 Jon 2015-05-30 02:31:27 UTC
Created attachment 116164 [details]
Using track nipple plus trying to scroll
Comment 11 Jon 2015-05-30 02:31:52 UTC
Created attachment 116165 [details]
Only scrolling on the track pad
Comment 12 Jon 2015-05-30 02:32:20 UTC
Ok, added two captures. One while moving the nipple and the other without.
Comment 13 Peter Hutterer 2015-06-01 06:14:47 UTC
thanks. can you explain again what I need to be looking for? I have the faint feeling that I'm not looking at the right thing. Thanks
Comment 14 Jon 2015-06-01 21:20:03 UTC
I think this may have been covered by your other bug comment about palm detection
http://wayland.freedesktop.org/libinput/doc/latest/palm_detection.html
https://bugs.freedesktop.org/show_bug.cgi?id=90731

Having read the libinput page I think the disabling of the touchpad is probably what's going on. I will miss my nipple plus scroll, but I guess I can get used to it. Thanks for all the help.
Comment 15 Peter Hutterer 2015-06-01 23:33:07 UTC
ok, sorry for all the confusion. I'll close this one as duplicate then because the other one is a lot more terse and easier to follow than this one.

*** This bug has been marked as a duplicate of bug 90731 ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.