Bug#452411: xserver-xorg-input-evdev: Logitech MX510 USB mouse doesn't work after unplug/replug
On Thu, Nov 15, 2007 at 00:25:58 +0100, Philou wrote:
> I noticed that my Logitech MX510 USB mouse stops responding after i
> unplug and re-plug it. (I first noticed that when suspend to disk/ram
> with tuxonice made my USB mouse stopped working upon resume.
> Upon resume, everything seems OK, as far as i can tell :
> lsusb sees the mouse correctly and i can't see anything wrong when using
> udevmonitor ( symlinks are ok, and points correctly to /dev/input/event3
> which is what i have in my xorg.conf.
> Everything used to be OK, on that part, when using 184.108.40.206. Now,
> even when going back to 220.127.116.11, it behaves the same, no mouse upon
> unplug/replug so i thought that it may be not be kernel related
> PC is ASUS P4C800-E ( 3.0 GHz x86) running Debian SID, latest packages.
> Section "InputDevice"
> Identifier "Configured Mouse"
> Driver "evdev"
> Option "CorePointer"
> # Option "Name" "Logitech USB-PS/2 Optical Mouse"
> Option "Device" "/dev/input/event3"
> Option "Buttons" "10"
> Option "ZAxisMapping" "4 5"
> # Option "Protocol" "ExplorerPS/2"
When you unplug/replug the mouse, it might get a different device node,
so specifying /dev/input/event3 in xorg.conf is broken. It'd probably
work if you specified a persistent path, using the symlinks under
/dev/input/by-id/, or if you used X input-hotplug support with hal.