Bug 39055 - Can't disable touchpad by tapping on hot-area on touchpad
Summary: Can't disable touchpad by tapping on hot-area on touchpad
Alias: None
Product: xorg
Classification: Unclassified
Component: Input/synaptics (show other bugs)
Version: 7.7 (2012.06)
Hardware: All Linux (All)
: medium minor
Assignee: Peter Hutterer
QA Contact:
Whiteboard: 2011BRB_Reviewed
Keywords: patch
: 42867 (view as bug list)
Depends on: 38303
  Show dependency treegraph
Reported: 2011-07-07 19:53 UTC by Bryce Harrington
Modified: 2018-04-06 08:01 UTC (History)
7 users (show)

See Also:
i915 platform:
i915 features:

BootDmesg.txt (61.83 KB, text/plain)
2011-07-07 19:55 UTC, Bryce Harrington
no flags Details
CurrentDmesg.txt (62.58 KB, text/plain)
2011-07-07 19:55 UTC, Bryce Harrington
no flags Details
peripherals.txt (605 bytes, text/plain)
2011-07-07 19:56 UTC, Bryce Harrington
no flags Details
xinput.txt (990 bytes, text/plain)
2011-07-07 19:56 UTC, Bryce Harrington
no flags Details
XorgLog.txt (31.62 KB, text/plain)
2011-07-07 19:56 UTC, Bryce Harrington
no flags Details

Description Bryce Harrington 2011-07-07 19:53:28 UTC
Forwarding this bug from Ubuntu reporter Stefan Ebner:

The touchpad surface includes a hot area to enable/disable it, but it does not work in linux.  Perhaps support needs added for it?

[Original Description]
My laptop doesn't have an extra button for disabling/enabling the touchpad.
On the top left corner of the touchpad there is an small area (marked with a white dot) where you have to tap 2 times to disable/enable it. If disabled it shows a orange light.

This doesn't work under ubuntu, also not under oneiric with all updates installed.

[    9.615958] Synaptics Touchpad, model: 1, fw: 7.4, id: 0x1e0b1, caps: 0xd04773/0xe40000/0x5a0400
[    9.705035] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input10

DistroRelease: Ubuntu 11.10
Package: xserver-xorg-input-synaptics 1.3.99+git20110116.0e27ce3a-0ubuntu15
ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39
Uname: Linux 2.6.39-3-generic i686
NonfreeKernelModules: wl
Architecture: i386
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Jun 11 14:52:23 2011
DistUpgraded: Log time: 2011-06-04 16:54:22.107183
DistroCodename: oneiric
DistroVariant: ubuntu
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:163c]
 ATI Technologies Inc Madison [AMD Radeon HD 5000M Series] [1002:68c1] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:163c]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
 LANG=en_GB.UTF-8ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.39-3-generic root=UUID=AA18AE5218AE1CF7 loop=/hostname/disks/root.disk ro single
Renderer: Unknown
SourcePackage: xserver-xorg-input-synaptics
UpgradeStatus: Upgraded to oneiric on 2011-06-04 (6 days ago)
dmi.bios.date: 10/21/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.23
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 163C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 65.35
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.23:bd10/21/2010:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr0580120015243D10010020100:rvnHewlett-Packard:rn163C:rvr65.35:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.version: 0580120015243D10010020100
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.4+bzr20110606-0ubuntu3
version.libdrm2: libdrm2 2.4.25-2ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.0-3ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1
Comment 1 Bryce Harrington 2011-07-07 19:55:28 UTC
Created attachment 48874 [details]
Comment 2 Bryce Harrington 2011-07-07 19:55:49 UTC
Created attachment 48875 [details]
Comment 3 Bryce Harrington 2011-07-07 19:56:04 UTC
Created attachment 48876 [details]
Comment 4 Bryce Harrington 2011-07-07 19:56:21 UTC
Created attachment 48877 [details]
Comment 5 Bryce Harrington 2011-07-07 19:56:38 UTC
Created attachment 48878 [details]
Comment 6 Peter Hutterer 2011-07-08 02:44:15 UTC
AFAIK, this is part of the clickpad series of touchpads for which we don't have upstream support yet. Patches circulated on the list a while ago, but they need finishing
Comment 7 Thomas Vogt 2011-11-14 01:14:52 UTC
Well, it _does_ work with OpenSuse 11.4. So why can't you implement the same patch, that is used in OpenSuse 11.4?
Comment 8 Peter Hutterer 2011-11-27 18:20:34 UTC
Time. Please feel free to grab those patches and upstream them to the list. The last set of patches I've seen was not ready.

Comment 9 Peter Hutterer 2012-03-13 21:49:12 UTC
*** Bug 42867 has been marked as a duplicate of this bug. ***
Comment 10 Matthew Monaco 2012-04-30 16:37:54 UTC
I'm pretty sure the suse support for this depends on an LED being available in the touchpad. I have been maintaining this support on Arch Linux. Does anyone have a touchpad with a disable area _without_ an led?

Would a patch be less likely to be accepted if it doesn't separate the LED support from the disable support?
Comment 11 Peter Hutterer 2012-04-30 19:44:01 UTC
(In reply to comment #10)
> Would a patch be less likely to be accepted if it doesn't separate the LED
> support from the disable support?

yes. I don't want crazy in-driver functionality for touchpads that don't need it. There should be discovery of that feature and it should only be exposed when the LED is available.

note that we'll likely need to query the LED state as well to avoid getting the touchpad into an inconsistent state (disabled, when it's actually enabled etc.)

looking through linux/input.h, we should send KEY_TOUCHPAD_ON/OFF when that button is pressed. The clients can then decide what to do, rather than having this behaviour enforced in the driver.
Comment 12 Stefan Nagy 2012-09-03 21:37:59 UTC
I add links to two related bugs in the debian BTS:
- debian bug 609903 (HP G62 laptop): LED indicator in the upper left corner of the touchpad itself.
- debian bug 683762 (HP Folio 13-2000 laptop): LED indicator between the touchpad and the keyboad.

Apart from that I thought it might be a good idea to add links to the unfinished patch sent upstream by Takashi Iwai a while ago (review by Peter Hutterer):
- http://article.gmane.org/gmane.comp.freedesktop.xorg.devel/13437 (patch)
- http://article.gmane.org/gmane.comp.freedesktop.xorg.devel/13607 (review)

I'm affected by this bug on the HP Folio 13-2000 laptop. I'd be glad to provide more information and/or test revised patches.
Comment 13 David Dreggors 2012-11-21 06:04:53 UTC
I created bug #42867 which is now marked as a duplicate of this bug. I am glad to see some more movement on this. My laptop (HP Pavilion G6) as a tiny LED above the mouse pad as well. It is between the mouse pad and the keyboard.

Neither work in all versions of Fedora I have tested it on (Fedora 16 & 17).

The mouse pad works as expected, you just can't turn it on or off via the hot spot button at the top left corner of the mouse pad.

The version of the synaptics driver I currently have installed is:


Also, below is the hardware information I posted in the original bug I created in case it helps.

Hardware info:
My laptop is an HP Pavilion G6 (G6-1B50US).
AMD Phenom(tm) II P650 Dual-Core Processor
4GB Ram

Handle 0x0001, DMI type 1, 27 bytes
System Information
 Manufacturer: Hewlett-Packard
 Product Name: HP Pavilion g6 Notebook PC
 Version: 0593110000204610000620100
 Serial Number: 5CG1221MYF
 UUID: 579C58E8-B265-06E7-3163-8DDE56E7D88D
 Wake-up Type: Power Switch
 SKU Number: QF761UA#ABA
 Family: 103C_5335KV G=N L=CON B=HP S=PAV

Handle 0x000C, DMI type 21, 7 bytes
Built-in Pointing Device
 Type: Touch Pad
 Interface: PS/2
 Buttons: 4
Comment 14 Nickolay 2012-11-22 03:55:02 UTC
I'm affected by this bug on HP Pavilion G6-2137SR, hope it will be fixed soon.
Comment 15 Peter Hutterer 2014-03-07 05:56:32 UTC
we currently have no plans of fixing this, sorry.
Comment 16 Alexey Svistunov 2018-04-04 13:56:04 UTC
(In reply to Peter Hutterer from comment #15)
> we currently have no plans of fixing this, sorry.

I have this issue with HP ProBook 4525s with LED on left up cover. Maybe now it's possible to fix it? I am ready to provide any information about the hardware, logs and more. I can take part in testing. And I can test it on openSUSE Leap.
Comment 17 Peter Hutterer 2018-04-04 21:54:08 UTC
Theoretically, this feature could be put into libinput provided the LED is exposed by the kernel. But google suggests that the 4525 is around 8 years old, I won't add any extra features to libinput for hardware that's at the end of their life and may die before the feature ever gets into a distribution, sorry.
Comment 18 Alexey Svistunov 2018-04-05 07:42:32 UTC
Almost all HP ProBooks and EliteBooks use similar models of touchpads, with LED in the upper left corner and a double-tap disconnect. For example, the new HP EliteBook (https://www.youtube.com/watch?v=VwOeYeZfhWQ) or the latest HP ProBook 650 (https://www.youtube.com/watch?v=Sb1xdsX3J4Q). So do not worry that the work will be done in vain.
Comment 19 Peter Hutterer 2018-04-05 23:02:21 UTC
Oh, good do know, thanks. Though for synaptics this won't happen, it's in maintenance mode. Please file a bug against libinput (in product Wayland) and we can take it from there. Note that this feature will require kernel-level support too for the LED to be controlled. Unless we have that, we can't (well, won't) do much in libinput.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.