ubuntu-x-swat team mailing list archive

["Jamin W. Collins" <jcollins@xxxxxxxxxxxxxxxx>]

Looks like the mouse is temporarily disconnected and the device entries
removed for it.  Then the mouse reconnects and the device entries are
recreated.  Here's the listing for /dev/input/ shortly after the mouse
stops working:

$ ls -l /dev/input/
total 0
drwxr-xr-x 2 root root    140 2009-11-25 19:47 by-path
crw-r----- 1 root root 13, 64 2009-11-25 06:04 event0
crw-r----- 1 root root 13, 65 2009-11-25 06:04 event1
crw-r----- 1 root root 13, 66 2009-11-25 06:04 event2
crw-r----- 1 root root 13, 67 2009-11-25 06:04 event3
crw-r----- 1 root root 13, 68 2009-11-25 06:04 event4
crw-r----- 1 root root 13, 69 2009-11-25 06:04 event5
crw-r----- 1 root root 13, 70 2009-11-25 06:04 event6
crw-r----- 1 root root 13, 71 2009-11-25 06:04 event7
crw-r----- 1 root root 13, 72 2009-11-25 06:04 event8
crw-r----- 1 root root 13, 73 2009-11-25 06:04 event9
crw-r----- 1 root root 13, 63 2009-11-25 06:04 mice
crw-r----- 1 root root 13, 32 2009-11-25 06:04 mouse0
crw-r----- 1 root root 13, 33 2009-11-25 06:04 mouse1
crw-r----- 1 root root 13, 34 2009-11-25 06:04 mouse2

Then a short while later, the mouse reconnects as I can see the
bluetooth led flashing:

$ ls -l /dev/input/
total 0
drwxr-xr-x 2 root root     60 2009-11-25 19:47 by-id
drwxr-xr-x 2 root root    160 2009-11-25 19:47 by-path
crw-r----- 1 root root 13, 64 2009-11-25 06:04 event0
crw-r----- 1 root root 13, 65 2009-11-25 06:04 event1
crw-r----- 1 root root 13, 74 2009-11-25 19:47 event10
crw-r----- 1 root root 13, 66 2009-11-25 06:04 event2
crw-r----- 1 root root 13, 67 2009-11-25 06:04 event3
crw-r----- 1 root root 13, 68 2009-11-25 06:04 event4
crw-r----- 1 root root 13, 69 2009-11-25 06:04 event5
crw-r----- 1 root root 13, 70 2009-11-25 06:04 event6
crw-r----- 1 root root 13, 71 2009-11-25 06:04 event7
crw-r----- 1 root root 13, 72 2009-11-25 06:04 event8
crw-r----- 1 root root 13, 73 2009-11-25 06:04 event9
crw-r----- 1 root root 13, 63 2009-11-25 06:04 mice
crw-r----- 1 root root 13, 32 2009-11-25 06:04 mouse0
crw-r----- 1 root root 13, 33 2009-11-25 06:04 mouse1
crw-r----- 1 root root 13, 34 2009-11-25 06:04 mouse2
crw-r----- 1 root root 13, 35 2009-11-25 19:47 mouse3

As you can see there are a few entries updated and created at 19:47 when
the mouse reconnected.  However, even after this reconnect the X cursor
is un responsive.  I've managed to rectify the X cursor responsiveness
by manually adding the following section to xorg.conf:

Section "InputDevice"
  Identifier  "Configured Mouse"
  Driver    "mouse"
  Option    "CorePointer"
  Option    "Device"    "/dev/input/mice"
  Option    "Protocol"    "IMPS/2"
  Option    "ZAxisMapping"    "4 5"
EndSection

Why X doesn't appear to be reading from /dev/input/mice without this
section is beyond me.

-- 
bluetooth mouse fails to reconnect
https://bugs.launchpad.net/bugs/458781
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-mouse in ubuntu.