Ubuntu
xorg package

Mouse cursor moves choppy/doesn't update its position as it should

Bug #1610666 reported by Mohit Tokas on 2016-08-07

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	xorg (Ubuntu)	Won't Fix	High	Unassigned

Bug Description

Q. What I expected to happen?
A. The mouse would run smoothly as it does run in windows.

Q. What happened instead?
A. The mouse lags moves choppy/doesn't update its position as it should

Additional Information:
Output of "xinput --list --short"

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ E-Signal USB Gaming Mouse id=10 [slave pointer (2)]
⎜ ↳ E-Signal USB Gaming Mouse id=11 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Power Button id=8 [slave keyboard (3)]
    ↳ Microsoft® LifeCam HD-3000 id=9 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]

Output of "xinput --list-props 11"

Device 'E-Signal USB Gaming Mouse':
Device Enabled (133): 1
Coordinate Transformation Matrix (135): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device Accel Profile (259): 0
Device Accel Constant Deceleration (260): 1.000000
Device Accel Adaptive Deceleration (261): 1.000000
Device Accel Velocity Scaling (262): 10.000000
Device Product ID (251): 1241, 41132
Device Node (252): "/dev/input/event4"
Evdev Axis Inversion (263): 0, 0
Evdev Axes Swap (265): 0
Axis Labels (266): "Rel X" (143), "Rel Y" (144), "Rel Horiz Wheel" (257), "Rel Vert Wheel" (258)
Button Labels (267): "Button Left" (136), "Button Middle" (137), "Button Right" (138), "Button Wheel Up" (139), "Button Wheel Down" (140), "Button Horiz Wheel Left" (141), "Button Horiz Wheel Right" (142), "Button Side" (255), "Button Extra" (256), "Button Unknown" (254), "Button Unknown" (254), "Button Unknown" (254), "Button Unknown" (254)
Evdev Scrolling Distance (268): 1, 1, 1
Evdev Middle Button Emulation (269): 0
Evdev Middle Button Timeout (270): 50
Evdev Third Button Emulation (271): 0
Evdev Third Button Emulation Timeout (272): 1000
Evdev Third Button Emulation Button (273): 3
Evdev Third Button Emulation Threshold (274): 20
Evdev Wheel Emulation (275): 0
Evdev Wheel Emulation Axes (276): 0, 0, 4, 5
Evdev Wheel Emulation Inertia (277): 10
Evdev Wheel Emulation Timeout (278): 200
Evdev Wheel Emulation Button (279): 4
Evdev Drag Lock Buttons (280): 0

Output of "lsusb"

Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 002: ID 0bc2:3321 Seagate RSS LLC
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 04d9:a0ac Holtek Semiconductor, Inc.
Bus 001 Device 003: ID 045e:0779 Microsoft Corp. LifeCam HD-3000
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Note : Holtek Semiconductor, Inc. is my mouse

Also found this in dmesg :

[ 292.597380] usb 1-1.4: new full-speed USB device number 5 using ehci-pci
[ 293.941408] usb 1-1.4: New USB device found, idVendor=04d9, idProduct=a0ac
[ 293.941413] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 293.941416] usb 1-1.4: Product: USB Gaming Mouse
[ 293.941418] usb 1-1.4: Manufacturer: E-Signal
[ 294.241702] input: E-Signal USB Gaming Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:04D9:A0AC.0004/input/input16
[ 294.242160] hid-generic 0003:04D9:A0AC.0004: input,hidraw0: USB HID v1.10 Mouse [E-Signal USB Gaming Mouse] on usb-0000:00:1a.0-1.4/input0
[ 294.841559] input: E-Signal USB Gaming Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.1/0003:04D9:A0AC.0005/input/input17
[ 294.897825] hid-generic 0003:04D9:A0AC.0005: input,hiddev0,hidraw1: USB HID v1.10 Keyboard [E-Signal USB Gaming Mouse] on usb-0000:00:1a.0-1.4/input1
[ 295.241685] hid-generic 0003:04D9:A0AC.0006: hiddev0,hidraw2: USB HID v1.10 Device [E-Signal USB Gaming Mouse] on usb-0000:00:1a.0-1.4/input2

Things that i have already tried:

Set "Device Accel Constant Deceleration (260):1.000000" prop to greater values, makes the mouse go faster doesn't make it update its position quicker.

Set usbhid mousepoll to 1 and 4 in /sys/module, doesn't make much of a difference.

WORKAROUND: Use kernel parameter:
irqpoll

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
Uname: Linux 4.4.0-10-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.20-0ubuntu3
Architecture: amd64
BootLog:
[[0;32m OK [0m] Started Network Manager.
Starting Network Manager Wait Online...
[[0;32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor to "ondemand".
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sun Aug 7 15:49:08 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0122] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2040]
InstallationDate: Installed on 2016-03-12 (147 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=f07625b5-4b5d-4d0a-a297-9a53679a2c03 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/17/2013
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BHZ7710H.86A.0100.2013.0517.0942
dmi.board.name: DZ77BH-55K
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG39008-400
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0100.2013.0517.0942:bd05/17/2013:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build1
xserver.bootTime: Sun Aug 7 21:03:28 2016
xserver.configfile: default
xserver.errors: systemd-logind: failed to get session: PID 839 does not belong to any known session
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.17.3-2ubuntu4

See original description

Tags:

Revision history for this message

Mohit Tokas (mohittokas) wrote on 2016-08-07:

screencast of cursor movement Edit (1.2 MiB, video/webm)
CurrentDmesg.txt Edit (66.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (5.7 KiB, text/plain; charset="utf-8")
DpkgLog.txt Edit (1.2 MiB, text/plain; charset="utf-8")
GconfCompiz.txt Edit (297 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (13.5 KiB, text/plain; charset="utf-8")
LightdmDisplayLog.txt Edit (37.7 KiB, text/plain; charset="utf-8")
LightdmGreeterLog.txt Edit (169.8 KiB, text/plain; charset="utf-8")
LightdmLog.txt Edit (185.6 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (11.7 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (701 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (7.2 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (109 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (4.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.7 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (177.3 KiB, text/plain; charset="utf-8")
UnitySupportTest.txt Edit (615 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (27.8 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (22.5 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (8.9 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (9.7 KiB, text/plain; charset="utf-8")
xserver.devices.txt Edit (475 bytes, text/plain; charset="utf-8")

Revision history for this message

penalvch (penalvch) wrote on 2016-09-01:

Mohit Tokas, thank you for reporting this and helping make Ubuntu better.

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:
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://wiki.ubuntu.com/Kernel/MainlineBuilds .

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.

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.