← Back to team overview

kernel-packages team mailing list archive

[Bug 1430622] Re: Touchscreen stops working after upgrading to Utopic HWE stack


Jared Dominguez, thank you for reporting this and helping make Ubuntu

Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1430622

** Package changed: linux-lts-utopic (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Touchscreen stops working after upgrading to Utopic HWE stack

Status in Dell Sputnik:
Status in linux package in Ubuntu:

Bug description:
  The system is a Dell Precision M3800 Developer Edition, i.e. it has
  Ubuntu 14.04 factory installed. If I upgrade the kernel and Xorg to
  the Utopic HWE versions, the touchscreen doesn't work. *However*, if I
  suspend and resume, the touchscreen starts working again.

  I noticed the touchscreen not working with just upgrading the kernel
  though didn't think of suspending/resuming to see if it came back.
  However, I do know that the touchscreen stops working when upgrading
  the kernel (3.13->3.16).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-31-generic 3.16.0-31.41~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 22:51:15 2015
   # This is a distribution channel descriptor
   # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
  InstallationDate: Installed on 2015-02-12 (26 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to: