Button assigned to LBCornerButton gets triggered in the middle of the right side of the pad
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-input-synaptics (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: xfree86-
The touchpad will randomly register a button event in the middle of the right side of the pad. In each case, the button event corresponds to the value assigned to LBCornerButton. I have confirmed this with xev.
In my case, I assign 8 to this button, which Firefox interprets as the Back navigation button. It also affects Nautilus for me as I have xbindkeys set to send \[Alt_L]\[Left].
I am using version 0.99.3-2ubuntu4 (jaunty) on Ubuntu 9.04 Jaunty Beta.
In the meantime, I intend to downgrade synaptics to 0.15.2 as a workaround.
UPDATED - 9:42pm 04.16.09: Downgrading to xserver-
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: xserver-
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-11-generic (buildd@rothera) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #41-Ubuntu SMP Wed Apr 8 04:38:53 UTC 2009
SourcePackage: xfree86-
Uname: Linux 2.6.28-11-generic i686
[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
Subsystem: Acer Incorporated [ALI] Device [1025:0110]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
Subsystem: Acer Incorporated [ALI] Device [1025:0110]
tags: |
added: jaunty lbcornerbutton synaptics touchpad removed: apport-bug i386 |
description: | updated |
Changed in xfree86-driver-synaptics (Ubuntu): | |
status: | New → Confirmed |
description: | updated |
affects: | xfree86-driver-synaptics (Ubuntu) → xserver-xorg-input-synaptics (Ubuntu) |
Now that HAL is deprecated in Ubuntu 10.4, it seems that downgrading the driver to 0.15.2 just breaks it completely. So no more workaround, and the bug persists in the latest version of the driver. Any chance of movement on this, it's been a year now.