USB mouse acceleration reset when plugged in

[Lambros Lambrou]

Description:

When the X Server starts up and the login screen is shown, the initial sensitivity of my USB mouse (acceleration and/or threshold) is very high (the mouse pointer moves a long way with small movements of the mouse). After I log in, the mouse sensitivity usually, but not always, gets automatically adjusted to my preferred setting. One problem I'm having is: this adjustment sometimes doesn't seem to happen. I often have to run the Mouse configuration applet, move one of the sliders and move it back, to correct the problem. The second problem (which seems closely related, and perhaps causes the first problem) is: if I unplug the USB mouse and plug it back in, the sensitivity goes back to being very high again, as it was on the Login screen. This second problem reproduces reliably.

Steps to reproduce (second problem):

On the login screen, mentally note the mouse's sensitivity (roughly).
Log on, then run the Mouse applet and set the sensitivity to be very different from what it was on the logon screen (that is, slide the "Acceleration" slider all the way to the left or right, whichever is most noticeably different from the Logon screen behaviour).
Unplug, then reconnect the USB mouse. Move the mouse around to get a feel for the sensitivity.

Observed behaviour:

The mouse sensitivity reverts back to what it was on the Logon screen.

Expected behaviour:

The mouse sensitivity should be set according to the Acceleration slider position, and should feel the same as just before the mouse was unplugged.

Notes:

The "xset q" mouse acceleration/threshold values do not change whilst I unplug and replug the mouse. For example, if I move the sliders all the way to the left, my mouse is very slow (as I'd expect) and the "xset q" values are "acceleration: 3/10 threshold: 1". When I unplug and reconnect the mouse, the observed sensitivity changes to being very high, but the "xset q" output remains the same. If I then enter "xset m 3/10 1" (the exact same numbers as in the current "xset q" output), the mouse becomes very slow again.

System affected:

I'm using Ubuntu Intrepid (64 bit version), updated only a few days ago. xserver-xorg-core is version 2:1.5.0-1ubuntu1. Machine is Dell Inspiron 1720 laptop, with nVidia graphics and proprietary "nvidia" driver in use. I will try re-testing with "nv" driver. USB mouse is Logitech wireless, "lsusb" output shows it as "046d:c50e Logitech, Inc. MX-1000 Cordless Mouse Receiver".

[Lambros Lambrou (lambros)]

Problem still occurs without the proprietary nVidia driver.

[Günter (guenter-grodotzki)]

same here. I upgraded yesterday to Intrepid Beta (32) and have that problem ever since:

[ 2062.962030] usb 3-1.2: USB disconnect, address 9
[ 2065.209655] usb 3-1.2: new low speed USB device using uhci_hcd and address 10
[ 2065.390934] usb 3-1.2: configuration #1 chosen from 1 choice
[ 2065.432102] input: Microsoft Corporation Microsoft � Laser Mouse 6000 as /class/input/input17
[ 2065.456260] input,hidraw2: USB HID v1.11 Mouse [Microsoft Corporation Microsoft � Laser Mouse 6000] on usb-0000:00:1d.1-1.2

the "faster mouse in splash screen" is a "problem" I had in Hardy, too, but I persume its just because gdm is ran under a different user (most probably login as "real root" and setting the mouse would solve that problem)

but every time I plug my mouse (or when I switch pc's via kvm-switch) I must reset the mouse acceleration.

[Bryce Harrington (bryce)]

Hi lambros,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[Lambros Lambrou (lambros)]

Hi,

Many thanks for looking into this, I think it could be a major irritation for a lot of people. After using Intrepid for a while now, I am now convinced the "second" issue is the root cause of the "first" issue I mentioned at the beginning. Sorry for the confusion!

[Lambros Lambrou (lambros)]

Steps I took to create this Xorg log file:

* Unplugged the USB mouse.
* Restarted the X Server with Ctrl-Alt-Backspace
* Logged on, and waited for things to settle down.
* Plugged the mouse back in.
* Wiggled the mouse to confirm it was too sensitive (it was! :-)
* Took a snapshot copy of my /var/log/Xorg.0.log, to attach here.

A bit more background info: my mouse is a wireless device, with a separate USB "dongle" that clips onto the mouse. When the mouse is not in use, I keep the dongle clipped onto the mouse, because that stops the battery from draining. Usually, I log in using just the keyboard, before unclipping the USB dongle and plugging it in to the PC. I think this problem would affect anybody who owns a mouse with a similar design, as well as people using a KVM switch or similar.

[Lambros Lambrou (lambros)]

Not sure whether or not I've customised my xorg.conf, so I'm attaching it anyway.

[Shane O'Connell (shaneoc)]

I am also seeing this problem. Whenever I unplug my USB mouse and plug it back in, the mouse acceleration is reset. If I simply open the mouse preferences dialog and then close it again, without changing any settings, then the acceleration goes back to the value I originally specified.

I'm using a Microsoft Wireless Notebook Optical Mouse 3000 (http://www.microsoft.com/hardware/mouseandkeyboard/productdetails.aspx?pid=070), and I also remove the USB dongle from the PC and put it into the mouse when not in use to save battery life, like Lambros described.

[Valentin Neacsu (valentin.neacsu)]

Same here on Intrepid x86, upgraded from Hardy.

[Lambros Lambrou (lambros)]

I'm pleased to report this problem is no longer affecting me. I have absolutely no idea what update has fixed it, but it is nonetheless now fixed for me! :-) I just confirmed it by setting my mouse sensitivity really slow, unplugging it, then re-plugging it. X server correctly kept the slow setting.

Many thanks,

Lambros

[Aseem (amohanty)]

I am still running into a variant of this problem. I am running a lenovo t60 with a docking station and a logitech marble mouse attached to the dock. I use xmodmap to remap some of the buttons. After about 10-12 minutes of usage, my device gets reset and I have to remap the buttons.

dmesg output:

[ 413.363421] usb 3-4.4: USB disconnect, address 4
[ 413.628298] usb 3-4.4: new low speed USB device using ehci_hcd and address 5
[ 413.725507] usb 3-4.4: configuration #1 chosen from 1 choice
[ 413.736829] input: Logitech USB Trackball as /devices/pci0000:00/0000:00:1a.7/usb3/3-4/3-4.4/3-4.4:1.0/input/input13
[ 413.780212] input,hidraw2: USB HID v1.10 Mouse [Logitech USB Trackball] on usb-0000:00:1a.7-4.4

lsusb output:
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 006: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
Bus 003 Device 003: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0
Bus 003 Device 002: ID 04b3:4485 IBM Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

This did not happen on Hardy, and gets very annoying as all of a sudden every 15 mins I lose my middle click and have to reset it with an xmodmap -e.

Thanks.
AM

[Aseem (amohanty)]

I should add that I also get all sorts of device descriptor errors:

[ 777.907447] usb 3-4.4: USB disconnect, address 5
[ 778.152230] usb 3-4.4: new low speed USB device using ehci_hcd and address 6
[ 778.266307] usb 3-4.4: configuration #1 chosen from 1 choice
[ 778.271836] input: Logitech USB Trackball as /devices/pci0000:00/0000:00:1a.7/usb3/3-4/3-4.4/3-4.4:1.0/input/input14
[ 778.335717] input,hidraw2: USB HID v1.10 Mouse [Logitech USB Trackball] on usb-0000:00:1a.7-4.4
[ 1090.940277] usb 3-4.4: reset low speed USB device using ehci_hcd and address 6
[ 1091.200274] usb 3-4.4: device descriptor read/64, error -32

[Musthafa Meeran (musthafameeran-deactivatedaccount)]

Problem is still there in Kubuntu Intrepid/Jaunty using Logitech USB Laser mouse.
As mentioned in comment 1, Even though the selected value is still shown in the mouse configuration page, I have to adjust the mouse pointer threshold every-time I login, by increasing/decreasing it a bit, to get back the normal acceleration set.
Also, in my laptop, whenever there is a power change (ac mode/battery mode), mouse speed increases again and I have to repeat the procedure mentioned above.

Could you please have a look at this?
Please let me know what details are needed to debug and fix this problem and I ll provide them.

Thanks a lot....

[gsmx (gsmx)]

Aseem:
Apologies for the late response, however, your problem seems to be unrelated to the one described here, I suggest you to report another bug. With the information you gave above plus the output of `lspci -vvnn` and your /var/log/Xorg.0.log file from after reproducing this issue.

Musthafa:
According to Lambros Lambrou the problem was fixed with an unknown update, are you sure you are up-to-date? If so, does the Jaunty beta fix your issue? If not, could you also please attach the output of `lspci -vvnn` and the contents of /var/log/Xorg.0.log?

[Musthafa Meeran (musthafameeran-deactivatedaccount)]

I just now tried again by unplugging & re-plugging my usb laser mouse
(logitech) and the problem is still there !! I had to re-adjust the mouse
settings to get the normal speed back.

I have Kubuntu Jaunty beta with KDE 4.2.2 and all the latest updates till
now. So it looks like it is not fixed completely, atleast for my mouse
hardware.

Could you please re-open this bug and help me in getting this fixed?

$ lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04

$ uname -a
Linux <hostname> 2.6.28-11-generic #39-Ubuntu SMP Thu Apr 2 03:00:35 UTC
2009 i686 GNU/Linux

Please find attached the log files. The dmesg output shows that I have
unplugged/plugged the mouse a few times.

Also, please let me know if you need any more logs/information which will
help in getting this fixed and I ll provide them as soon as I can.

Thanks a lot....

[Lambros Lambrou (lambros)]

I'm using Jaunty now, and my xserver-xorg is at version 1:7.4~5ubuntu16. Just to confirm: I am still no longer experiencing the original problem I reported (mouse sensitivity reverting to an incorrect setting on USB disconnect/reconnect).

However, I can reproduce Aseem's problem: if I run "xmodmap -e 'pointer = 3 2 1' " to swap my mouse buttons, and then disconnect/reconnect the USB mouse, I find that the pointer mapping is undone. So I concur with MarniX's assessment - Aseem's problem should be raised as a separate bug report.

I'm sorry to hear Musthafa is having similar problems to what I originally reported. I'm afraid I can't offer any explanation (it works fine for me now).

[gsmx (gsmx)]

Though the original bugfiler doesn't experience the problem anymore, Musthafa Meeran can still confirm the problem. And it does seem strange because in the logfile the same profile, acceleration and speed are set each time.

[T. Dalbo (tdalbo)]

I can also confirm the original problem, running Jaunty.

The thing is, my other desktop doesn't have this problem whatsoever. Both are up-to-date on software.

Attached are the two files you asked Musthafa.

[willjcroz (willjcroz)]

Also having this problem in Karmic (recently started happening). It seems to happen after a resuming from suspend.

Like the original post says, the accel/sens sliders under the mouse configuration applet are in the correct positions for my preferred settings but the mouse behaves in the (slower) default way until I move the sliders around a bit.

The same thing sometimes happens with the keyboard repeat rate settings also.

[adolf102 (adameumail)]

Same problem here happens on mouse unplug and re-plug. Happens every time. Mouse is Logitech RX1000

Distributor ID: Ubuntu
Description: Ubuntu 9.10
Release: 9.10
Codename: karmic
Linux adamo-laptop 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 04:38:19 UTC 2010 x86_64 GNU/Linux

log:
(II) config/hal: removing device Logitech USB Optical Mouse
(II) Logitech USB Optical Mouse: Close
(II) UnloadModule: "evdev"
(II) config/hal: Adding input device Logitech USB Optical Mouse
(**) Logitech USB Optical Mouse: always reports core events
(**) Logitech USB Optical Mouse: Device: "/dev/input/event7"
(II) Logitech USB Optical Mouse: Found 12 mouse buttons
(II) Logitech USB Optical Mouse: Found x and y relative axes
(II) Logitech USB Optical Mouse: Found scroll wheel(s)
(II) Logitech USB Optical Mouse: Configuring as mouse
(**) Logitech USB Optical Mouse: YAxisMapping: buttons 4 and 5
(**) Logitech USB Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Logitech USB Optical Mouse" (type: MOUSE)
(**) Logitech USB Optical Mouse: (accel) keeping acceleration scheme 1
(**) Logitech USB Optical Mouse: (accel) filter chain progression: 2.00
(**) Logitech USB Optical Mouse: (accel) filter stage 0: 20.00 ms
(**) Logitech USB Optical Mouse: (accel) set acceleration profile 0
(II) Logitech USB Optical Mouse: initialized for relative axes.

[adolf102 (adameumail)]

Quick workaround (instead of going to system-settings) is to run: xset m 1 1

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Hi Lambros,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 273837

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 273837 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/273837

[Lambros Lambrou (lambros)]

I can no longer reproduce this problem on Lucid. Marking "Fix Released".