Bug 1475229 - Touchpad re-enables itself after opening laptop
Touchpad re-enables itself after opening laptop
Status: NEW
Product: Fedora
Classification: Fedora
Component: libinput (Show other bugs)
26
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Peter Hutterer
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-26 05:00 EDT by Stefan Hajnoczi
Modified: 2017-07-26 05:02 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Stefan Hajnoczi 2017-07-26 05:00:22 EDT
Description of problem:

The touchpad on my ThinkPad X1 Carbon 3rd Gen re-enables itself after opening the laptop lid.

The touchpad is disabled in the BIOS and GNOME.  After opening the lid the touchpad responds but GNOME's mouse settings dialog still thinks it is disabled.

I noticed that libinput-debug-events shows POINTER_MOTION events while the touchpad is successfully disabled in GNOME and the on-screen mouse cursor isn't moving.  Perhaps libinput or a higher layer of the stack "forgets" to ignore the touchpad after the lid has been opened?

This is a F26 regression, previous Fedora releases worked fine.  I am using Wayland.

Version-Release number of selected component (if applicable):
libinput-1.7.3-1.fc26.x86_64
xorg-x11-drv-libinput-0.25.1-2.fc26.x86_64
libwayland-client-1.13.0-1.fc26.x86_64
xorg-x11-server-Xwayland-1.19.3-4.fc26.x86_64
gnome-session-wayland-session-3.24.1-2.fc26.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Disable touchpad in BIOS and GNOME mouse settings.
2. Verify that the touchpad does not respond.
3. Close laptop lid and reopen.
4. Test if the touchpad responds.

Actual results:
Touchpad responds.

Expected results:
Touchpad does not respond.

Additional info:
# libinput-list-devices
Device:           SynPS/2 Synaptics TouchPad
Kernel:           /dev/input/event5
Group:            12
Seat:             seat0, default
Size:             98x54mm
Capabilities:     pointer 
Tap-to-click:     disabled
Tap-and-drag:     enabled
Tap drag lock:    disabled
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: disabled
Calibration:      n/a
Scroll methods:   *two-finger edge 
Click methods:    *button-areas clickfinger 
Disable-w-typing: enabled
Accel profiles:   none
Rotation:         n/a
Comment 1 Stefan Hajnoczi 2017-07-26 05:02:38 EDT
Note this is a possible duplicate of bz 1448962 but I wasn't able to decide whether they are the same issue or not.

Note You need to log in before you can comment on or make changes to this bug.