peter at cs.unisa.edu.au
Mon May 26 15:57:02 PDT 2008
On Mon, May 26, 2008 at 04:57:59PM +0200, Thomas Ilnseher wrote:
> > > I downgraded to 1.1.5-r2, which finally solved any problems. Therefore
> > > xf86-input-evdev-1.2.0 is to blame.
> > You should also be able to upgrade to evdev 2.0 from git, it is a bit more
> > resistant to funky devices.
> Ok, will do this first. There is a new problem with 1.1.5:
> when the mouse isn't moved for some minutes, it disconnects itself.
> => xorg crashes.
it's a bluetooth mouse, right? when it disconnects, the kernel device probably
disappears. evdev 1.1 does its own hotplugging internal to the driver and
interferes with the x server's hotplugging. this probably causes the crash.
you really need 1.2 or greater to avoid this.
> I don't think the mouse is that funky. it got 2 rel axes (X and Y), a
> hwheel, (a vwheel that's not physically available, but in the
> descriptors grrr...), and 5 mouse buttons.
some devices also have a tendency to report absolute axes, which can overwrite
the relative axes. so what may happen in your case is that X is interpreted as
absolute axis, which doesnt make much sense on a mouse.
a log of the server will tell us that.
More information about the xorg