Wrong handling of forcepad edges

Bug #1472739 reported by Jan
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I have experienced incorrect behaviour of the driver when forcepad very edges are touched (HP Elitebook 1040 G1). With Tap-and-drag gesture disabled and even tapping disabled (although this does not change anything) when one finger touches the touchpad and another taps the very edge of the touchpad (any side), the system behaves as if there was a click and hold action as long as the finger is on the touchpad. This seems to be linked to the driver reporting a left click when the second finger touches the veery edge of the touchpad, see output from evtest below.

How to replicate: disable tapping. On the desktop, put one finger on the touchpad, then lightly tap the very 1mm of the edge. Move the first finger down and right and notice an area being selected. This should only happen when the finger is pressed (like for a click) against the touchpad and held so during the move.

Attached are outputs from synclient and xinput.

I believe it is a bug in a kernel driver.

From system logs:
[ 3.349148] psmouse serio3: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2a1, caps: 0xd40923/0x840300/0x12e800, board id: 2685, fw id: 1608298

****

cat /proc/bus/input/devices

I: Bus=0011 Vendor=0002 Product=0007 Version=01a1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio3/input0
S: Sysfs=/devices/platform/i8042/serio3/input/input10
U: Uniq=
H: Handlers=mouse0 event5
B: PROP=5
B: EV=b
B: KEY=e520 610000 0 0 0 0
B: ABS=660800011000003

****

Output from evtest of the very moment second finger touched the bottom edge of the touchpad:

Event: time 1436383712.432784, type 3 (EV_ABS), code 58 (ABS_MT_PRESSURE), value 68
Event: time 1436383712.432784, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 68
Event: time 1436383712.432784, -------------- SYN_REPORT ------------
Event: time 1436383712.514285, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1436383712.514285, -------------- SYN_REPORT ------------
Event: time 1436383712.554585, type 3 (EV_ABS), code 58 (ABS_MT_PRESSURE), value 69
Event: time 1436383712.554585, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 6

Thanks,
Jan

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.16.0-41-generic 3.16.0-41.57~14.04.1
ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11
Uname: Linux 3.16.0-41-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jul 8 19:14:14 2015
InstallationDate: Installed on 2015-05-14 (54 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: jp 2090 F.... pulseaudio
 /dev/snd/controlC0: jp 2090 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=c4a08a5c-08ad-42d4-8a39-76149ed3a95e
InstallationDate: Installed on 2015-05-14 (220 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
Lsusb:
 Bus 001 Device 002: ID 8087:8000 Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 002 Device 006: ID 05c8:0369 Cheng Uei Precision Industry Co., Ltd (Foxlink)
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP EliteBook Folio 1040 G1
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-57-generic root=UUID=f2cdc7c4-e5be-4934-9e34-3bb55e1d87fc ro acpi_osi=Linux "acpi_osi=!Windows 2012"
ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-57-generic N/A
 linux-backports-modules-3.16.0-57-generic N/A
 linux-firmware 1.127.19
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: trusty
Uname: Linux 3.16.0-57-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 07/20/2015
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L83 Ver. 01.32
dmi.board.name: 213E
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 24.2D
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrL83Ver.01.32:bd07/20/2015:svnHewlett-Packard:pnHPEliteBookFolio1040G1:pvrA3008D510B03:rvnHewlett-Packard:rn213E:rvrKBCVersion24.2D:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook Folio 1040 G1
dmi.product.version: A3008D510B03
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Jan (jpalczew-net) wrote :
Jan (jpalczew-net)
description: updated
Revision history for this message
penalvch (penalvch) wrote :

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

affects: linux-lts-utopic (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Jan (jpalczew-net) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Jan (jpalczew-net) wrote : BootDmesg.txt

apport information

Revision history for this message
Jan (jpalczew-net) wrote : CRDA.txt

apport information

Revision history for this message
Jan (jpalczew-net) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Jan (jpalczew-net) wrote : IwConfig.txt

apport information

Revision history for this message
Jan (jpalczew-net) wrote : Lspci.txt

apport information

Revision history for this message
Jan (jpalczew-net) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Jan (jpalczew-net) wrote : ProcEnviron.txt

apport information

Revision history for this message
Jan (jpalczew-net) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Jan (jpalczew-net) wrote : ProcModules.txt

apport information

Revision history for this message
Jan (jpalczew-net) wrote : PulseList.txt

apport information

Revision history for this message
Jan (jpalczew-net) wrote : UdevDb.txt

apport information

Revision history for this message
Jan (jpalczew-net) wrote : UdevLog.txt

apport information

Revision history for this message
Jan (jpalczew-net) wrote : WifiSyslog.txt

apport information

Revision history for this message
Jan (jpalczew-net) wrote :

I experimented with the module synaptic editing its code hoping to fix it myself. It seemed to me that the incorrect behaviour was already present in codes passed on to synaptics_parse_hw_state(...). BTW, the touchpad works fine under Windows which eliminates the explanation that touchpad firmware or the hardware is faulty.

penalvch (penalvch)
tags: added: bios-outdated-1.33
Revision history for this message
Jan (jpalczew-net) wrote :

I have updated BIOS to the newest version, see the output:
L83 Ver. 01.33
11/06/2015
This has not changed anything in the problem described above. I should also comment that the touchpad firmware is up-to-date too.

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

Jan, at your earliest convenience, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

tags: added: latest-bios-1.33
removed: bios-outdated-1.33
Changed in linux (Ubuntu):
importance: Low → Medium
status: Confirmed → Incomplete
Revision history for this message
Jan (jpalczew-net) wrote :

The bug is still present in unchanged form in the most recent upstream kernel
Linux mat-lin4117 4.4.0-040400rc6-generic #201512202030 SMP Mon Dec 21 01:32:09 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Thanks

Jan (jpalczew-net)
tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.4-rc6
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jan (jpalczew-net) wrote :

Output from synclient attached.

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

Jan, please execute the following at a terminal and advise if the issue is reproducible:
synclient MiddleButtonAreaLeft=0 MiddleButtonAreaRight=0 MiddleButtonAreaTop=0

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jan (jpalczew-net) wrote :

The output from the above command is:

X Error of failed request: BadValue (integer parameter out of range for operation)
  Major opcode of failed request: 131 (XInputExtension)
  Minor opcode of failed request: 37 (X_ChangeDeviceProperty)
  Value in failed request: 0x12a
  Serial number of failed request: 24
  Current serial number in output stream: 25

To clarify what produces errors, see below:

jp@mat-lin4117:~$ synclient MiddleButtonAreaRight=0
X Error of failed request: BadValue (integer parameter out of range for operation)
  Major opcode of failed request: 131 (XInputExtension)
  Minor opcode of failed request: 37 (X_ChangeDeviceProperty)
  Value in failed request: 0x12a
  Serial number of failed request: 22
  Current serial number in output stream: 25
jp@mat-lin4117:~$ synclient MiddleButtonAreaTop=0
X Error of failed request: BadValue (integer parameter out of range for operation)
  Major opcode of failed request: 131 (XInputExtension)
  Minor opcode of failed request: 37 (X_ChangeDeviceProperty)
  Value in failed request: 0x12a
  Serial number of failed request: 22
  Current serial number in output stream: 25

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
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.