Laptop stick and touchpad problems after linux 4.4 update

Bug #1657553 reported by arsenix
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned
systemd (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have behaved erratically on my Dell Precision 7510:
* The trackpoint moves WAY too fast and there don't seem to be any parameters I can change in xinput to fix this. It is essentially unusable.
* The touchpad starts with parameters set incorrectly.
* Touchpad tap to click is now turned on again and is very sensitive. This I can change through xinput but the change is still odd.
* The two finger scrolling is set incorrectly to be highly sensitive. This I can also change through xinput.
* Two finger scrolling still activates often during normal use of the trackpad. To the extent that I had to turn off two finger scrolling to stop inadvertent scrolling.

All of the above behavior is new going from 4.4.0-47 to -53. Previously this all worked perfectly on this machine.

Seems to be symptoms noted by these other users on askubuntu here as well: http://askubuntu.com/questions/862527/laptop-stick-mouse-problems-after-linux-4-4-update-on-14-04

The touchpad symptoms I seem to be able to work around my changing xinput parameters, but the trackpoint I have not been able to fix at all (which is sad since that is my primary mouse device normally). Would appreciate any suggestions as to how to revert the old behavior.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-53-generic 4.4.0-53.74
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: jpeverill 2813 F.... pulseaudio
 /dev/snd/controlC0: jpeverill 2813 F.... pulseaudio
Date: Wed Jan 18 10:21:55 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-07-17 (916 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 8087:0a2b Intel Corp.
 Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc.
 Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 7510
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed root=UUID=4a4cfeb0-ad39-4293-bcaf-000d6538b550 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-59-generic N/A
 linux-backports-modules-4.4.0-59-generic N/A
 linux-firmware 1.157.6
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-05-01 (262 days ago)
dmi.bios.date: 01/24/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.10
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.3.10:bd01/24/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision 7510
dmi.sys.vendor: Dell Inc.

Revision history for this message
arsenix (arsenix) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

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

Does this bug go away if you boot back into the prior kernel version?

Changed in linux (Ubuntu):
importance: Undecided → Medium
Changed in linux (Ubuntu Xenial):
importance: Undecided → Medium
status: New → Incomplete
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
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 v4.10 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.10-rc4

Revision history for this message
N/A (ubuntu-berknapp) wrote :

I've now running: "Linux ucl09404 4.10.0-11-generic #13-Ubuntu SMP Wed Mar 1 21:27:28 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux"

and I still have the problem on my Dell Precision 7510.

$ xinput list
xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPad id=13 [slave pointer (2)]
⎜ ↳ AlpsPS/2 ALPS DualPoint Stick id=14 [slave pointer (2)]

Using the stick is impossible, it's far too sensitive.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Hi, please download the attach file, then

$ sudo cp 71-pointingstick-precision.hwdb /etc/udev/hwdb.d/
$ sudo systemd-hwdb update
$ sudo udevadm trigger

And check if this issue is solved or not.

Revision history for this message
N/A (ubuntu-berknapp) wrote :

Hi kaihengfeng,

yes that has effect, it works.

But 0.1 is too slow, I've tried 0.25 and find it's usable.

Thanks a lot. :-)

Revision history for this message
N/A (ubuntu-berknapp) wrote :

I also put an xinput command into ~/.xsession

xinput set-prop 'AlpsPS/2 ALPS DualPoint Stick' 'libinput Accel Speed' 0.1

to have some difference in pushing the stick hard or soft

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Changed in systemd (Ubuntu):
status: New → Confirmed
Changed in systemd (Ubuntu Xenial):
status: New → Confirmed
Changed in systemd (Ubuntu):
importance: Undecided → Medium
Changed in systemd (Ubuntu Xenial):
importance: Undecided → Medium
Revision history for this message
N/A (ubuntu-berknapp) wrote :

Hi again,

after fiddeling around somehow, I found following combination most useful:

evdev:name:*DualPoint Stick:dmi:bvn*:bvr*:bd*:svnDellInc.:pnPrecision7510*:pvr*
 POINTINGSTICK_CONST_ACCEL=0.025

*AND* in ~/.xsession:

xinput set-prop 'AlpsPS/2 ALPS DualPoint Stick' 'libinput Accel Speed' 1

So set, it's a little bit slow when moving across the whole screen, but accurate enough to position on very small items as single characters and small buttons for example in BB forums. ;-)

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Hello,
Can you confirm the parameter for "POINTINGSTICK_CONST_ACCEL" should be 0.025 or 0.25?

Thanks

Revision history for this message
Philip K (kaphi) wrote :

Hi,

I am pretty sure that I've got the same issue (Dell Latitude E5470, Linux Mint 18.1 x64).
It did not work with kernel 4.8 so I updated to kernel 4.10.0-20-generic and the problem persists.

xinput lists:
⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPad id=12 [slave pointer (2)]
⎜ ↳ AlpsPS/2 ALPS DualPoint Stick id=13 [slave pointer (2)]

Let me know if any other information is needed.

Thanks and best regards,
Philip

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Philip, the 'not working' one or the 'way too fast' one?

Revision history for this message
Philip K (kaphi) wrote :

Sorry, I should have specified this more clearly.

The trackpad works flawlessly, but the trackpoint is way too sensitive rendering it unusable.

Changes in the (Linux Mint) mouse settings dialog show no effect.

BTW: The trackpoint worked great when booting from the Mint live cd, which could point to a kernel issue.

I have tried to fix that via xorg.conf but did not succeed (see https://forums.linuxmint.com/viewtopic.php?f=49&t=241246)

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Hi, please download the attach file, then

$ sudo cp 71-pointingstick-5470.hwdb /etc/udev/hwdb.d/
$ sudo systemd-hwdb update
$ sudo udevadm trigger

And check if this issue is solved or not.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Revision history for this message
Philip K (kaphi) wrote :

Thanks for the quick reply. Unfortunately this does not change anything (also did a reboot to be sure).

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Changed in systemd (Ubuntu):
status: Confirmed → Incomplete
Changed in systemd (Ubuntu Xenial):
status: Confirmed → Incomplete
no longer affects: linux (Ubuntu Xenial)
no longer affects: systemd (Ubuntu Xenial)
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]

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