'disable-touchpad'-hardware-key is not enabling touchpad again

Bug #1037085 reported by Aapo Rantalainen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Laptop has hardware button for disabling touchpad.
(image showing button: http://images03.olx.ae/ui/3/60/14/61595614_3-ACER-ASPIRE-5738Z-CHEAP-Like-New-Dubai.jpg )

Pressing it will disable touchpad.
 There are visual feedback on screen. No message on dmesg. Led of button will light on.

Pressing it again will NOT enable touchpad.
 There are visual feedback on screen. No message on dmesg. Led of button will light off.

dmidecode -s system-manufacturer
Acer
dmidecode -s system-product-name
Aspire 5738
dmidecode -s system-version
0100

uname -a
Linux 3.2.0-27-generic #43-Ubuntu SMP Fri Jul 6 14:25:57 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: aapo 1610 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf4700000 irq 45'
   Mixer name : 'Intel Cantiga HDMI'
   Components : 'HDA:10ec0888,10250205,00100202 HDA:11c11040,11c10001,00100200 HDA:80862802,80860101,00100000'
   Controls : 45
   Simple ctrls : 22
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=2ef0165e-6ab2-4c98-b151-0e1a800c51e8
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: Acer Aspire 5738
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-27-generic root=UUID=3c480b2e-204d-433d-9100-c9f904d1ac3c ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-27-generic N/A
 linux-backports-modules-3.2.0-27-generic N/A
 linux-firmware 1.79
Tags: precise running-unity
Uname: Linux 3.2.0-27-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 02/11/2010
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.30i
dmi.board.name: JV50
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.30i:bd02/11/2010:svnAcer:pnAspire5738:pvr0100:rvnAcer:rnJV50:rvrRev:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 5738
dmi.product.version: 0100
dmi.sys.vendor: Acer

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 1037085

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
tags: added: precise
Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : AcpiTables.txt

apport information

tags: added: apport-collected running-unity
description: updated
Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : AlsaDevices.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : AplayDevices.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : ArecordDevices.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : BootDmesg.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : CRDA.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : Card0.Codecs.codec.1.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : Card0.Codecs.codec.3.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : IwConfig.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : Lspci.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : Lsusb.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : PciMultimedia.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : ProcModules.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : PulseList.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : RfKill.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : UdevDb.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : UdevLog.txt

apport information

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote : WifiSyslog.txt

apport information

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

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.5kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

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.6-rc1-quantal/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote :

Happens with:
Linux 3.6.0-030600rc1-generic #201208022056 SMP Fri Aug 3 00:57:36 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote :

I continued with this.

Bug happens with kernel 3.2.0-49 (newest for precise)

Bug happens with kernel 3.10.1 (newest for saucy)

Restarting Xorg is not enough to bring touchpad to life, full reboot is needed.

Debug build (for debug messages) of xserver-xorg-input-synaptics doesn't show any messages when hardware-button is pressed.

synclient touchpadoff=1 and synclient touchpadoff=0 and synclient touchpadoff=2 and synclient | grep -i touchpadoff are working as expected.
When touchpad is disabled with hardware-button "synclient | grep -i touchpadoff" still shows 0.

I attached screenshot of overlay icon for disabled touchpad. I think it comes from package gnome-settings-daemon and more precisely it is shown by this file: plugins/media-keys/gsd-media-keys-manager.c

Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote :

I found another way to disable/enable touchpad from commandline:
gsettings set org.gnome.settings-daemon.peripherals.touchpad touchpad-enabled false
gsettings set org.gnome.settings-daemon.peripherals.touchpad touchpad-enabled true
This is working. But after touchpad breaks with hardware-button this will not bring it back.

*
After playing with gnome-settings-daemon (gsd):

gsd-media-keys-manager is handling three different touchpadkey-events:
        { TOUCHPAD_KEY, NULL, "XF86TouchpadToggle" },
        { TOUCHPAD_ON_KEY, NULL, "XF86TouchpadOn" },
        { TOUCHPAD_OFF_KEY, NULL, "XF86TouchpadOff" },
Where first (TOUCHPAD_KEY) is only which is really doing something about settings, two latters are only about showing info on screen. And this laptop is only sending these ON/OFF events.

I then commented out everything relating touchpad -> Bug still triggers: Hardware-button disables touchpad, but doesn't enable it back (this time there are no visual icon on screen).
*

What another process/application is handling media keys? (acpi_listen is not showing it)

affects: linux (Ubuntu) → gnome-settings-daemon (Ubuntu)
Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote :

And one more way to disable+enable touchpad:
xinput list | grep TouchPad
 -> id=11

xinput set-prop 11 Device Enabled 0
xinput set-prop 11 Device Enabled 1

And for checking current status: xinput list-props 11 | grep Enabled

But this is not the way what hardware-button is using, and is not helping when touchpad breaks.

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.