can not re-enable touchpad

Bug #1518737 reported by bd339
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I am running Ubuntu 15.10 (32-bit edition but I know it is also a problem on 64-bit edition) on an Acer Aspire 5738 laptop which has a physical button next to the touchpad that can toggle the device.
When I hit the button a desktop notification appears, informing me that the device has been disabled (an icon of a touchpad with an x in the bottom-right-hand-corner) and I am no longer able to use the touchpad for anything, as expected.
When I press the button again to re-enable the touchpad, a desktop notification appears, informing me that the device has been enabled (an icon of a touchpad with no x in the bottom-right-hand-corner) but the touchpad remains disabled, i.e I can use it for absolutely nothing. (clicking, scrolling, pointing, ...)
Re-logging or restarting the laptop enables the touchpad, but I can also use modprobe to remove and insert psmouse module, which will also cause it to enable.
When I use the button physically next to the touchpad to enable/disable the touchpad, it does not affect the toggle switch in the "Mouse and Touchpad" settings, but if I use that setting (the toggle switch) I can correctly enable and disable the touchpad.
xinput lists the device under "Virtual core pointer" as an "AlpsPS/2 ALPS GlidePoint".
BIOS is updated as of today.
If I can be of help in patching the bug, I would love to, but I just have no idea where to look. I altered the psmouse kernel module to print information to the logs about various activity (resetting, deactivating) but none of it was very informative (again, I don't know where to look).
---
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: benjamin 1617 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 15.10
HibernationDevice: RESUME=UUID=7b71d0e9-05b0-4b07-9cd1-e4a998e8be54
InstallationDate: Installed on 2015-11-23 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Acer Aspire 5738
Package: linux (not installed)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=c2650be5-50b4-4182-a8e7-c428326ae23e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-18-generic N/A
 linux-backports-modules-4.2.0-18-generic N/A
 linux-firmware 1.149.2
Tags: wily
UdevLog: Error: [Errno 2] Ingen sådan fil eller filkatalog: '/var/log/udev'
Uname: Linux 4.2.0-18-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/24/2010
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.34
dmi.board.name: JV50_MV
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.34:bd09/24/2010:svnAcer:pnAspire5738:pvr0100:rvnAcer:rnJV50_MV:rvrRev:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 5738
dmi.product.version: 0100
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/1518737/+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
bd339 (bd339-deactivatedaccount) wrote :

I am fairly certain this is a hardware / device driver bug and as such it does not originate in any repository package but in the kernel.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1518737

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
bd339 (bd339-deactivatedaccount) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected wily
description: updated
Revision history for this message
bd339 (bd339-deactivatedaccount) wrote : CRDA.txt

apport information

Revision history for this message
bd339 (bd339-deactivatedaccount) wrote : CurrentDmesg.txt

apport information

Revision history for this message
bd339 (bd339-deactivatedaccount) wrote : IwConfig.txt

apport information

Revision history for this message
bd339 (bd339-deactivatedaccount) wrote : JournalErrors.txt

apport information

Revision history for this message
bd339 (bd339-deactivatedaccount) wrote : Lspci.txt

apport information

Revision history for this message
bd339 (bd339-deactivatedaccount) wrote : Lsusb.txt

apport information

Revision history for this message
bd339 (bd339-deactivatedaccount) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
bd339 (bd339-deactivatedaccount) wrote : ProcEnviron.txt

apport information

Revision history for this message
bd339 (bd339-deactivatedaccount) wrote : ProcInterrupts.txt

apport information

Revision history for this message
bd339 (bd339-deactivatedaccount) wrote : ProcModules.txt

apport information

Revision history for this message
bd339 (bd339-deactivatedaccount) wrote : PulseList.txt

apport information

Revision history for this message
bd339 (bd339-deactivatedaccount) wrote : RfKill.txt

apport information

Revision history for this message
bd339 (bd339-deactivatedaccount) wrote : UdevDb.txt

apport information

Revision history for this message
bd339 (bd339-deactivatedaccount) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
description: updated
description: updated
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 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'.

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/v4.4-rc2+cod1-wily/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
penalvch (penalvch)
tags: added: latest-bios-1.34
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
Revision history for this message
bd339 (bd339-deactivatedaccount) wrote :

I experienced this bug in every version of Ubuntu I have tried on this laptop (15.10 (currently) & 15.04).

Revision history for this message
bd339 (bd339-deactivatedaccount) wrote :

By using:
"xinput list-props 13"
where 13 is the id of the touchpad as retrieved by "xinput list",
I have discovered that the faulty mechanism does not affect the "Device Enabled" xinput propety, but the working mechanism in "Mouse and Touchpad settings" (the toggle button) does indeed toggle the "Device Enabled" xinput propety.

penalvch (penalvch)
tags: added: kernel-bug-exists-upstream-4.4-rc2 vivid
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.