Cursor jump sometimes by touchpad button
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-input-synaptics (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
The cursor jump or sticking sometimes, when I click touchpad button while one finger on touchpad.
syslog:
Sep 3 16:54:59 atlantis kernel: [24012.686354] psmouse serio1: Touchpad at isa0060/
Sep 3 16:54:59 atlantis kernel: [24012.693535] psmouse serio1: Touchpad at isa0060/
Sep 3 16:54:59 atlantis kernel: [24012.700467] psmouse serio1: Touchpad at isa0060/
Sep 3 16:54:59 atlantis kernel: [24012.710051] psmouse serio1: Touchpad at isa0060/
Sep 3 16:54:59 atlantis kernel: [24012.720168] psmouse serio1: Touchpad at isa0060/
Sep 3 16:54:59 atlantis kernel: [24012.730265] psmouse serio1: Touchpad at isa0060/
Sep 3 16:54:59 atlantis kernel: [24012.740728] psmouse serio1: Touchpad at isa0060/
Sep 3 16:54:59 atlantis kernel: [24012.740730] psmouse serio1: issuing reconnect request
Otherwise the usb mouse work perfectly.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xserver-
ProcVersionSign
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Sep 3 16:56:30 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
InstallationDate: Installed on 2016-08-29 (4 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: LENOVO 20FD0021MC
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xserver-
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/20/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: N1GET64W (1.43 )
dmi.board.
dmi.board.name: 20FD0021MC
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 20FD0021MC
dmi.product.
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-
version.
version.
version.
version.
version.
version.
version.
version.
xserver.bootTime: Sat Sep 3 10:14:57 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 4665
vendor CMN
xserver.version: 2:1.18.3-1ubuntu2.3
information type: | Public → Public Security |
information type: | Public Security → Public |
Changed in xserver-xorg-input-synaptics (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in xserver-xorg-input-synaptics (Ubuntu): | |
status: | Confirmed → Incomplete |
Gabor Peltzer, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http:// kernel. ubuntu. com/~kernel- ppa/mainline/ ?C=N;O= D ? Please keep in mind the following: /wiki.ubuntu. com/Kernel/ MainlineBuilds .
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https:/
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: fixed-upstream fixed-upstream- X.Y-rcZ
kernel-
kernel-
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: bug-exists- upstream bug-exists- upstream- X.Y-rcZ
kernel-
kernel-
Please note, an error to install the kernel does not fit the criteria of kernel- bug-exists- upstream.
Also, you don't need to apport-collect further unless specifically requested to do so.
It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed.
Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.
Thank you for your help.