[Acer Aspire E5-571G] Touchpad not working after suspend/resume

Bug #1393079 reported by BoD
98
This bug affects 20 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Ubuntu 14.10 on an Acer Laptop, model: Aspire E5-571G-941Y
$ uname -a
Linux Acer-Aspire-E5-571G 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:07:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Every time I suspend, the trackpad no longer works when resuming.

I see several other people have the same issue with the same laptop here:
http://ubuntuforums.org/showthread.php?t=2250002
(some people say it's a 14.10 specific problem)

I realize this report is very poor but please don't hesitate to request data / clarifications from me, I'll be happy to help.
---
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bod 3942 F.... pulseaudio
 /dev/snd/controlC1: bod 3942 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=2e6e7d72-637c-4b16-8cda-0471dfb711d4
InstallationDate: Installed on 2014-11-14 (15 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Acer Aspire E5-571G
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed root=UUID=94aa9203-873c-4dff-8207-4e6b33a6a3e7 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-25-generic N/A
 linux-backports-modules-3.16.0-25-generic N/A
 linux-firmware 1.138
Tags: utopic
Uname: Linux 3.16.0-25-generic x86_64
UpgradeStatus: Upgraded to utopic on 2014-11-14 (15 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/06/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EA50_HB
dmi.board.vendor: Acer
dmi.board.version: V1.04
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571G:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E5-571G
dmi.product.version: V1.04
dmi.sys.vendor: Acer

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1393079/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
BoD (bod-c) wrote :

Following https://wiki.ubuntu.com/Bugs/FindRightPackage I think this problems probably lies in pm-utils or the Kernel, but to be honest, I have no idea.

affects: ubuntu → pm-utils (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in pm-utils (Ubuntu):
status: New → Confirmed
Revision history for this message
Ernesto Alejo (ernestoalejo) wrote :

This also affects my laptop

Revision history for this message
Victor Passapera (vpassapera) wrote :

Affects my laptop as well.

System Information
 Manufacturer: Dell Inc.
 Product Name: Inspiron 7547

Revision history for this message
odie (odie-t) wrote :

My laptop is also affected (Acer e3-111). When I resume from sleep (S3), my Xorg.0.log says:

[ 1204.869] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 1204.869] (II) intel(0): switch to mode 1366x768@60.1 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 1206.441] (--) synaptics: SYN1B7D:01 06CB:2991 UNKNOWN: touchpad found

Furthermore, I get the following in dmesg:

[ 1191.910761] usb 1-2: reset high-speed USB device number 2 using xhci_hcd
[ 1191.911060] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
[ 1191.911064] usb 1-2: hub failed to enable device, error -22
[ 1192.023049] usb 1-2: reset high-speed USB device number 2 using xhci_hcd
[ 1192.039597] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800773ef720
[ 1192.151154] usb 1-4: reset high-speed USB device number 3 using xhci_hcd
[ 1192.151165] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
[ 1192.151168] usb 1-4: hub failed to enable device, error -229
[ 1192.263026] usb 1-4: reset high-speed USB device number 3 using xhci_hcd
[ 1192.263130] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
[ 1192.263133] usb 1-4: hub failed to enable device, error -22
[ 1192.375037] usb 1-4: reset high-speed USB device number 3 using xhci_hcd
[ 1192.405965] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800773ef9c0
[ 1192.464863] usb 1-2.1: reset full-speed USB device number 5 using xhci_hcd
[ 1192.464991] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 4.
[ 1192.464995] usb 1-2.1: hub failed to enable device, error -22
[ 1192.535293] usb 1-2.1: reset full-speed USB device number 5 using xhci_hcd
[ 1192.535319] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 4.
[ 1192.535322] usb 1-2.1: hub failed to enable device, error -22
[ 1192.607494] usb 1-2.1: reset full-speed USB device number 5 using xhci_hcd
[ 1192.623719] usb 1-2.1: device firmware changed
[ 1192.935923] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[ 1194.015516] PM: resume of devices complete after 2491.115 msecs
[ 1194.016052] PM: Finishing wakeup.

Ugly workaround for this is to reload the hid_multitouch after resuming:

# sudo rmmod hid_multitouch
# sudo modprobe hid_multitouch

Please let me know if there is more information needed.

Revision history for this message
odie (odie-t) wrote :

This is what I did to fix this for me:

# sudo touch /etc/pm/sleep.d/10_touchpad
# sudo chmod 755 /etc/pm/sleep.d/10_touchpad

Then edit the file 10_touchpad and paste the following into it:

#!/bin/sh

case "${1}" in
        resume|thaw)
                rmmod hid_multitouch
                modprobe hid_multitouch
                ;;
esac

Revision history for this message
BoD (bod-c) wrote :

Thanks a lot odie, this workaround works for me as well!

Revision history for this message
penalvch (penalvch) wrote :

BoD, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1393079

affects: pm-utils (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
BoD (bod-c) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected utopic
description: updated
Revision history for this message
BoD (bod-c) wrote : BootDmesg.txt

apport information

Revision history for this message
BoD (bod-c) wrote : CRDA.txt

apport information

Revision history for this message
BoD (bod-c) wrote : CurrentDmesg.txt

apport information

Revision history for this message
BoD (bod-c) wrote : IwConfig.txt

apport information

Revision history for this message
BoD (bod-c) wrote : Lspci.txt

apport information

Revision history for this message
BoD (bod-c) wrote : Lsusb.txt

apport information

Revision history for this message
BoD (bod-c) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
BoD (bod-c) wrote : ProcEnviron.txt

apport information

Revision history for this message
BoD (bod-c) wrote : ProcInterrupts.txt

apport information

Revision history for this message
BoD (bod-c) wrote : ProcModules.txt

apport information

Revision history for this message
BoD (bod-c) wrote : PulseList.txt

apport information

Revision history for this message
BoD (bod-c) wrote : RfKill.txt

apport information

Revision history for this message
BoD (bod-c) wrote : UdevDb.txt

apport information

Revision history for this message
BoD (bod-c) wrote : UdevLog.txt

apport information

Revision history for this message
BoD (bod-c) wrote : WifiSyslog.txt

apport information

Revision history for this message
penalvch (penalvch) wrote : Re: Touchpad not working after suspend/resume

BoD, as per http://us.acer.com/ac/en/US/content/drivers an update to your BIOS is available (1.09). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, 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

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

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, then please mark this report Status Confirmed.

Thank you for your understanding.

tags: added: bios-outdated-1.09
Revision history for this message
BoD (bod-c) wrote :

Unfortunately, I do not have access to a Windows partition to boot on :(
Because of this, I don't know a way to update the Bios.

I hope someone else interested in this issue can try it and keep us informed here.

Revision history for this message
odie (odie-t) wrote :

I have the same problem as BoD since Acer only allows BIOS update through a Windows tool. Linux tools or a update boot cd is not available. Furthermore, questions in their forums about what has been actually fixed by an update stay unanswered.

Revision history for this message
penalvch (penalvch) wrote :

odie, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu 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
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
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.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Revision history for this message
odie (odie-t) wrote :

I just managed to update my Acer BIOS with the help of Freedos 1.1 bootet via USB. My BIOS is now version 1.29 instead of 1.04. Touchpad problem still exists.

Revision history for this message
penalvch (penalvch) wrote :
Revision history for this message
odie (odie-t) wrote :

Christopher,
please help me to understand why I should open a new bug. All I did was to provide a workaround for the problem and confirmed, that I have the same problem as DoD with pretty similar hardware.

Revision history for this message
Michael Litherland (gpf-me) wrote :

This bug also appears to happen on my Dell Inspiron 13 7347. Is there any information I can provide to help find an actual resolution? Thanks, odie, for the work-around; I'm going to give that a shot here in a minute.

Revision history for this message
penalvch (penalvch) wrote :

Michael Litherland, it would be most helpful if you filed a new report via a terminal:
ubuntu-bug linux

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

@ Christopher M. Penalver:

It is pretty clear this bug isn't of a low importance.

Changed in linux (Ubuntu):
importance: Low → Medium
Revision history for this message
Dirk Seidel (dseidel) wrote :

Executing xinput on my laptop (Acer Aspire V Nitro) gives:
  SYN1B7F:01 06CB:2970 UNKNOWN id=14 [slave pointer (2)]
for my touchpad.

From
http://www.adamdrew.net/?tag=kernel
I found a potential kernel patch which might solve the problem:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=109571cf3ec78a39477eedd6b11927f52cbcb1e8

I only tried reloading the i2c-hid module and this worked for me. Only the KDE settings for the touchpad are screwed up after that. Going into KDE settings and click apply, everything is fine again.

Revision history for this message
peddanet (peddanet) wrote :

This bug is annoying, can I do something to assist?

Revision history for this message
T.Breustedt (tbreustedt) wrote :

Hello, is there any hope for a solution?

Revision history for this message
Ernesto Alejo (ernestoalejo) wrote :

Remember there is a script that fixes the error and you can use in the meanwhile:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1393079/comments/7

(Thanks odie-t by the way)

Revision history for this message
Dirk Seidel (dseidel) wrote :

Unfortunately. at least for KDE with customized settings for the touchpad, it is not a satisfactory fix (see #36). As long as I don't find a way to reload KDE settings via konsole I have to click through the menue to properly restore the touchpad...

Revision history for this message
odie (odie-t) wrote :

dseidel: Have you tried adding the following to the script (or executing it manually)?

rmmod psmouse
modprobe psmouse

Maybe this helps KDE to rediscover the touchpad. I can't test it since I don't use KDE, sorry.

Revision history for this message
Dirk Seidel (dseidel) wrote :

odie, thanks for the try. Unfortunately it doesn't help.

Revision history for this message
T.Breustedt (tbreustedt) wrote :

Thanks Ernesto,
unfortunately the script from odie does not fix the problem.
The command modprobe hid_multitouch gets no result.
The output from xinput:
SYN1B7F:01 06CB:2970 UNKNOWN.

Thanks for help. Who can help?

Revision history for this message
Dirk Seidel (dseidel) wrote :

@ tbreustedt: did you also remove the driver first (rmmod hid_multitouch)?
Also, you could try the same with i2c-hid:
sudo rmmod i2c-hid
sudo modprobe i2c-hid

Instead of odie's script you can also try the following for a "permanent" solution:
sudo touch /etc/pm/config.d/00sleep_module
sudo chmod 755 /etc/pm/config.d/00sleep_module

edit the file and insert
SUSPEND_MODULES="$SUSPEND_MODULES i2c-hid"

Revision history for this message
Dirk Seidel (dseidel) wrote :

I just installed the 3.17.8 kernel. You can get the deb's from here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17.8-vivid/

For a 64-bit system you need
linux-headers-3.17.8-031708-generic_3.17.8-031708.201501081837_amd64.deb
linux-headers-3.17.8-031708_3.17.8-031708.201501081837_all.deb
linux-image-3.17.8-031708-generic_3.17.8-031708.201501081837_amd64.deb

and install the files with 'sudo dpkg -i linux-*'. If you want to remove it again just do 'sudo apt-get remove linux-headers-3.17.8-* linux-image-3.17.8-* && sudo update-grub'

This version of the kernel includes the patch mentioned in #36. The touchpad works flawlessly now, including the KDE settings!

Is there any chance that this patch will be included in 14.10?

And does anyone know how security updated are handled for kernels obtained from here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/
Does the latest version of the 3.17 kernel always include the relevant updates?

Revision history for this message
Dirk Seidel (dseidel) wrote :

The mainline kernel does not get security updates and is only intended for debugging...

Revision history for this message
oberon2007 (bernhard-c) wrote :

odie, thank you so much for the script! For me it worksdoesn't work (Acer TravelMate B115 + Ubuntu Gnome 14.10) after having tried all sorts of other things. That's really wonderful!
It only works with suspend though, not after hibernate. When after hibernate the touchpad is frozen and I use the Acer hotkey (Fn+F4) to switch to suspend again and then resume once more, the touchpad is back at work - kind of funny ;)
That's not really a big deal since its easy to avoid hibernate for me. Anyway, can you think of a way to alter the script to include resume after hibernate, maybe?

Revision history for this message
oberon2007 (bernhard-c) wrote :

btw in a similar discussion on ubuntuforums http://ubuntuforums.org/showthread.php?t=1321032 some people discovered that the syntax sometimes differs between $1 or "$1" or "${1}" - so: try out what works for you (maybe check the syntax of other files in that same dir) and also make sure to make the file executable!

Revision history for this message
oberon2007 (bernhard-c) wrote :

hm. the last few times i have tried it now, restart worked fine, no matter if from suspend, suspend-hybrid or hibernate - maybe the one time described above was just bad luck or a combination of things ...

Revision history for this message
Dirk Seidel (dseidel) wrote :

So here is the complete fix:

build a new kernel with the patch (see #36). Don't worry, it's very easy! Got it from here:
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
Tested for the current kernel in 14.10

Get the source:
apt-get source linux-image-$(uname -r)
cd linux-3.16.0

replace the attatched file in drivers/hid/i2c-hid/

Build the kernel:
fakeroot debian/rules clean
fakeroot debian/rules binary-headers binary-generic

this takes some time.

cd ..
sudo dpkg -i linux-headers-* linux-image-*

Reboot.

Done!

Revision history for this message
Dirk Seidel (dseidel) wrote :

Forgot one thing, you need:
sudo apt-get build-dep linux-image-$(uname -r)
before building the kernel.

Revision history for this message
Dirk Seidel (dseidel) wrote :

Instead of replacing the file you should apply the attached patch:
patch drivers/hid/i2c-hid/i2c-hid.c < i2c-hid.c.patch

tags: added: patch
Revision history for this message
oberon2007 (bernhard-c) wrote :

Thank you for this Dirk! But can I please ask you what exactly to do now in what order on a freshly installed Ubuntu Gnome 14.10
I'm just re-installing and don't want to do anything wrong or in the wrong order now... 8-) I did have the frozen clickpad-issue before re-install and Odie's solution did work for my setup.
greetings
Bernhard

Revision history for this message
oberon2007 (bernhard-c) wrote :

your posts and corrections above now sound a bit confusing to me - I'm a Linux-beginner.... sorry ;)

Revision history for this message
oberon2007 (bernhard-c) wrote :

Does this look like the correct step-by-step? :

1. build environment:
sudo apt-get build-dep linux-image-$(uname -r)

2. Get the source:
apt-get source linux-image-$(uname -r)
cd linux-3.16.0

3. download patch:
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1393079/+attachment/4308734/+files/i2c-hid.c.patch <<
- Where to store this patch file? I guess its only important to use the correct path during patching, right?

4. patch:
patch drivers/hid/i2c-hid/i2c-hid.c < i2c-hid.c.patch

5. Build the kernel:
fakeroot debian/rules clean
fakeroot debian/rules binary-headers binary-generic

6. install
cd ..
sudo dpkg -i linux-headers-* linux-image-*
reboot

Revision history for this message
Dirk Seidel (dseidel) wrote :

Hi Bernhard,
yes, this is how it should be done. You can store the patch-file in the linux-3.16.0 directory. Then your point 4 is exactly what you have to execute.

But why do you want to compile the kernel? You said that Odie's workaround worked for you. It should also work with your new install and it is easier than the "real" fix. You would have to recompile every time there is a kernel update. I only do this because I still had problems with the KDE settings of the touchpad.

Revision history for this message
oberon2007 (bernhard-c) wrote :

hm, well I had some other bugs in the system after some unexperienced fumbling around here and there ... ;) Also on occasion the frozen touchpad-problem did happen again. so I decided to reinstall and I thought this would be the cleaner solution altogether. and ok, if this wouldn't have been necessary, anyway I guess I learned a few things about linux today which is good in any case.

Kernel is building right now - how long does that take? 30 Minutes? Or more like 60? 8-}

Only additional thing that was still needed during download of the source was
sudo apt-get install dpkg-dev

and
sudo apt-get build-dep linux-image-$(uname -r)
would not work before downloading the source, so I did that before building the kernel

the patch-file I copied to the dir of the original and left both files there after patching - hope that's ok...

will let you know how the system behaves with the patched kernel...
cheers
Bernhard

Revision history for this message
oberon2007 (bernhard-c) wrote :

ok, cool! it took about 2 hours altogether.
system is running fine and mouspad works fine.after suspend.
thank you again for your help!

so does that mean that all future official kernel updates for 14.10 will still include the old unpached i2c-hid?
how's this in 14.04?

Revision history for this message
Dirk Seidel (dseidel) wrote :

Great that it works.
Concerning 14.04, I think the bug was not present there, but I'm not sure (see bug description above).
Kernel versions >=3.17 do include the patch, so with Ubuntu 15.04 latest, the bug will be gone. But hopefully, the patch will be included already in updates for 14.10.

@Joseph Salisbury: please, apply the patch (before the next kernel update?):
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=109571cf3ec78a39477eedd6b11927f52cbcb1e8

Revision history for this message
Orco (lvmartinezl) wrote :

Excuse me, I've been followed this conversation because I have the same problem and there is not any solution has orked for me, I've tried several "solutions" but they doesn't work, I used this:
/etc/pm/sleep.d/70input-reset

#!/bin/sh
#
# Reload the AT keyboard interface.

case "$1" in
hibernate|suspend)
echo -n "i8042" > /sys/bus/platform/drivers/i8042/unbind
;;
thaw|resume)
echo -n "i8042" > /sys/bus/platform/drivers/i8042/bind
;;
*)
;;
esac

but then my computer doesn't suspend, when I close the lid it only gets the screen off and furthermore it has caused another problems. I' like to apply the patch but I don't know how to, I understanded up to the number 3 in #55, when I try to make the clon, it says: "destination path 'ubuntu-trusty' already exists and is not an empty directory." I applied those steps with kernel 3.13.0, I don't know where to create the patch and where to "paste" then.

Revision history for this message
Dirk Seidel (dseidel) wrote :

@Orco: did you try the workarounds in #7 and #44? If they do not work for you, the patch is most probably not applying to your case anyway...

Revision history for this message
Orco (lvmartinezl) wrote :

I tried #7 in all its ways, when tried #44 it says: rmmod: ERROR: Module i2c_hid is not currently loaded

Revision history for this message
Dirk Seidel (dseidel) wrote :

Then your touchpad uses a differrent driver. The patch is specifically for the i2c-hid driver and so it is of no use for you, sorry.

Revision history for this message
oberon2007 (bernhard-c) wrote :

bad news from my side: the success with the patch is not consistent and it just happened again and no touchpad after suspend... grrr.
isn't there a way to restart the driver with a command line at least? A little command-line script I could could define as a keyboard-short cut?

Revision history for this message
oberon2007 (bernhard-c) wrote :

via terminal window works in my case:
rmmod hid_multitouch
modprobe hid_multitouch

that's something at least ;)
will create a keyboard shortcut like that calling in the pw with "echo <password>" and sudo -S ...
like that its barable for me for the moment.

Revision history for this message
Dirk Seidel (dseidel) wrote :

Bernhard, sorry, my bad. I left out one important step. Before compiling you should also edit the file linux-3.16.0/debian.master/changelog and change the version number in the first line to, e.g., 3.16.0-30.40+hidfix
Without this, the updater tries to update the newly compiled kernel, even though it has the same version number. Also, there was a kernel update from 3.16.0-29 to 3.16.0-30 sometime within the last 24 hours which still does not include the patch.
If you still want to do build the new kernel, delete the old source, update the system and redo all the steps to compile the kernel including the above addition. And remember that you will have to do this every time there is a kernel update.

Revision history for this message
Dirk Seidel (dseidel) wrote :

The patch from #52 is implemented in today's new kernel 3.16.0-31.41!

Revision history for this message
Michael Litherland (gpf-me) wrote :

This bug still affects my laptop and my desktop. I filed a separate report on my laptop. Any hope for a fix? I'm running the 3.16.0-31.41 kernel but it still happens.

Revision history for this message
Li-aung Yip ("Lewis") (littleweseth) wrote :

Bug also affects Acer Aspire ES1-311-C9XM. The workaround in comment #7 fixes the issue.

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

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
svenmeier (sven-meiers) wrote :

A workaround for Ubuntu 15.04 is to add a new service to systemd which reloads the module after suspend:

sven@:/etc/systemd/system$ more touchscreen.service
[Unit]
Description=Restore touchscreen after suspend
After=suspend.target

[Service]
Type=simple
ExecStartPre=/sbin/modprobe -r hid_multitouch
ExecStart=/sbin/modprobe hid_multitouch

[Install]
WantedBy=suspend.target

sven@:/etc/systemd/system$ sudo systemctl enable /etc/systemd/system/touchscreen.service

Revision history for this message
penalvch (penalvch) wrote :

svenmeier, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

summary: - Touchpad not working after suspend/resume
+ [Acer Aspire E5-571G] Touchpad not working after suspend/resume
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.