Touch no longer working after suspend

Bug #1620053 reported by Steve Lympany on 2016-09-04
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical System Image
mir (Ubuntu)
unity8 (Ubuntu)

Bug Description

I have a Dell XPS 9350 qhd+ touch. All works fine. If I suspend it and then restart, touch no longer works.

Version 16.04.1 LTS

(Sorry -new to Ubuntu, but definitely abandonding Windows. Thank you!)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unity8 (not installed)
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Sep 4 14:49:24 2016
InstallationDate: Installed on 2016-09-02 (1 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system.
       Users in the 'systemd-journal' group can see all messages. Pass -q to
       turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: unity8
UpgradeStatus: No upgrade log present (probably fresh install)

Steve Lympany (steve-lympany) wrote :
tags: added: unity8-desktop
tags: added: input
Launchpad Janitor (janitor) wrote :

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

Changed in unity8 (Ubuntu):
status: New → Confirmed
Changed in unity8 (Ubuntu):
importance: Undecided → High
Changed in canonical-devices-system-image:
status: New → Confirmed
Changed in mir:
status: New → Confirmed
Mario Limonciello (superm1) wrote :

This was also happening in Unity7 and fixed with this kernel commit:

I would expect that same fix to fix unity8, but you can confirm.

Michał Sawicz (saviq) wrote :

Syncing task from Mir.

Changed in mir (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments