Touchpad input doesn't work after longer suspend.

Bug #1718654 reported by Michał Sawicz
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Invalid
High
Unassigned
linux (Ubuntu)
Fix Released
High
Unassigned

Bug Description

When I resume my laptop from a longer (not sure what the threshold is yet) suspend, I don't get input from the touchpad, a short suspend cycle fixes it.

Touchscreen works all the time.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 21 14:20:56 2017
DisplayManager: gdm3
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Michał Sawicz (saviq) wrote :
Changed in gnome-shell (Ubuntu):
importance: Undecided → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please install 'evtest':

   sudo apt install evtest

and then test your touchpad before and after suspending by running:

   sudo evtest

Does evtest still show events after suspend? (I'm wondering if the kernel isn't sending them or libinput or above is ignoring them)

Changed in gnome-shell (Ubuntu):
status: Confirmed → Incomplete
tags: added: resume
Revision history for this message
Jonathan Elchison (jelchison) wrote :

In my case, evtest succeeds before suspend. Then provides no data after suspend. Last line that prints is "Testing ..."

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Jonathan, that confirms you have a kernel issue.

The direction of this bug however depends on what saviq says...

Revision history for this message
Jonathan Elchison (jelchison) wrote :

Concur, thanks for the guidance. This touchpad behavior seems to have been introduced between 4.10.0-37-generic and 4.13.0-16-generic.

Other folks experiencing this issue should attempt booting into your last-known-good kernel.

Revision history for this message
Jeppe Bundsgaard (jeppe) wrote :

It helped booting into 4.10.0-37. The touchpad now works after suspend.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks Jeppe. Since you have figured that out I've reopened and reassigned your bug 1729391 to the kernel.

Changed in linux (Ubuntu):
status: New → Incomplete
importance: Undecided → High
Revision history for this message
Jeppe Bundsgaard (jeppe) wrote :

Kernel 4.14.0 and 4.13.12 fixes the problem. Thanks!

tags: added: kernel-fixed-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Michał Sawicz (saviq) wrote :

Confirmed, I haven't seen this issue in a while.

Changed in gnome-shell (Ubuntu):
status: Incomplete → Invalid
Changed in linux (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.