Keyboard and mouse stop working randomly

Bug #1744511 reported by Phill
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gdm3 (Ubuntu)
Fix Released
Undecided
Unassigned
gnome-shell (Ubuntu)
Fix Released
Undecided
abhisheks

Bug Description

Lenovo Yogo 300 has a keyboard, touch pad and touch screen. Keyboard and mouse stop working, I am unable to see any pattern to the problem. This affects both Wayland and Xorg sessions, log-in and lock screen and desktop environment. Originally mistaken for a full system freeze, but touch-screen works fine. Putting computer into standby and resuming resolves the issue, but sometimes happens within seconds of resuming, sometimes it works for ages without a problem.

Filed against gdm3 due to these events found in the log, but this may be unrelated:
Jan 20 23:20:51 phill-Lenovo-YOGA-300-11IBY /usr/lib/gdm3/gdm-x-session[1234]: (II) event8 - (II) PEAQ WMI hotkeys: (II) device removed
Jan 20 23:20:51 phill-Lenovo-YOGA-300-11IBY /usr/lib/gdm3/gdm-x-session[1234]: (II) event4 - (II) AT Translated Set 2 keyboard: (II) device removed

Problem started immediately after installing 17.10.1, 17.04 had been used flawlessly since it's release on this hardware. Note that "gnome-session" is installed which I normally use, but as the problem occurs on the lock and login screens I guess it's nothing to do with that.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gdm3 3.26.1-3ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Jan 20 23:31:03 2018
InstallationDate: Installed on 2018-01-18 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Phill (phill.l) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I've seen this kind of bug occur on other laptops, and in those cases it was a hardware fault (the ribbon cables for the keyboard and touchpad randomly lose contact).

For the moment let's assume your case is still a software problem. So can you please try:
  1. Booting 16.04 and use it for a while. Does the problem occur there? https://www.ubuntu.com/download/desktop
  2. Booting 18.04 and use it for a while. Does the problem occur there? http://cdimages.ubuntu.com/daily-live/current/
  3. Does installing older or newer kernel versions fix the issue? kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

Changed in gdm3 (Ubuntu):
status: New → Incomplete
Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
Phill (phill.l) wrote :

17.04 did not have any problems, I never had 16.04 on this computer.

An update to the kernel yesterday seems to have resolved this issue (linux-image-4.13.0-31). So it's not worth investigating further at this point in time.

However, the kernel update seems to have introduced a full system freeze that occurs less often than the original problem, but this is another matter. I think I'll just run 17.04 until 18.04 comes out.

I'm not sure if this should be marked invalid or fixed, so I'll leave that to someone else.

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

"Incomplete" is fine. If there are no more comments for 60 days then it will automatically change to Expired.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-shell (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.]

Changed in gdm3 (Ubuntu):
status: Incomplete → Expired
abhisheks (abhisheks)
Changed in gnome-shell (Ubuntu):
assignee: nobody → abhisheks (abhisheks)
status: Expired → Fix Released
Changed in gdm3 (Ubuntu):
status: Expired → 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.