[Acer Aspire S7-392] Touchscreen stops working after resume from S3

[clayton craft]

Touchscreen stops working after resume from S3 (suspend). This is printed to Xorg.0.log when the system is powered up:

[ 29.915] (II) XINPUT: Adding extended input device "ELAN Touchscreen" (type: TOUCHSCREEN
, id 11)
[ 29.915] (II) evdev: ELAN Touchscreen: initialized for absolute axes.
[ 29.915] (**) ELAN Touchscreen: (accel) keeping acceleration scheme 1
[ 29.915] (**) ELAN Touchscreen: (accel) acceleration profile 0
[ 29.915] (**) ELAN Touchscreen: (accel) acceleration factor: 2.000
[ 29.915] (**) ELAN Touchscreen: (accel) acceleration threshold: 4
[ 29.916] (II) config/udev: Adding input device ELAN Touchscreen (/dev/input/mouse0)

There's no information in kernel log or Xorg.0.log after resume..

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-9-generic 3.11.0-9.16
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
Uname: Linux 3.11.0-9-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: clayton 2497 F.... pulseaudio
 /dev/snd/controlC0: clayton 2497 F.... pulseaudio
Date: Sun Sep 29 15:11:54 2013
HibernationDevice: RESUME=UUID=43274a69-d023-452a-9f3a-70c188b4405b
InstallationDate: Installed on 2013-09-28 (1 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
MachineType: Acer Aspire S7-392
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-9-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-9-generic N/A
 linux-backports-modules-3.11.0-9-generic N/A
 linux-firmware 1.114
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/07/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.03
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Storm2
dmi.board.vendor: Acer
dmi.board.version: V2.03
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.03
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.03:bd06/07/2013:svnAcer:pnAspireS7-392:pvrV2.03:rvnAcer:rnStorm2:rvrV2.03:cvnAcer:ct10:cvrV2.03:
dmi.product.name: Aspire S7-392
dmi.product.version: V2.03
dmi.sys.vendor: Acer

[clayton craft (craftyguy)]

Xorg.0.log file attached

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc3-saucy/

[clayton craft (craftyguy)]

confirmed on upstream kernel:

clayton@ultrabook:~$ uname -a
Linux ultrabook 3.12.0-031200rc3-generic #201309291835 SMP Sun Sep 29 22:37:02 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[foggydude (rogier-stekje)]

affects me to @asus x202e

[penalvch (penalvch)]

craftyguy, as per http://us.acer.com/ac/en/US/content/drivers an update is available for your BIOS (2.05). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.

[penalvch (penalvch)]

foggydude, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[Launchpad Janitor (janitor)]

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