Bug#482396: Double detecting the same input device
-----BEGIN PGP SIGNED MESSAGE-----
this days I just gave the newest version, 1:7.3+18, a try.
Unfortunatelly I found the bug NOT fixed. The xorg is still unusable.
So I did search for the old bug, perhaps I missed to give some
informationes. I found the bug archived. So I unarchived and reopened
the bug as it still exists and still is very important as it renders
xorg nearly unusable!
Please fix the xorg as the version in lenny is absolutelly unusable as
every mouse klick gets interpreted twice!
Ah, yes, and this was the last mail I wrote (I didn't get any answer for
Am So den 22. Jun 2008 um 17:29 schrieb Klaus Ethgen:
> Hi Brice,
> Am Sa den 21. Jun 2008 um 6:43 schrieb Brice Goglin:
> > > > You want to remove the first mouse section here. Otherwise X will get
> > > > the events for your trackpoint twice (once through /dev/input/mouse1,
> > > > and then again through /dev/input/mice).
> > >
> > > As I did downgrade to the stable xorg to have a working system I had to
> > > upgrade again to test the above.
> > >
> > > Unfortunately it is indeed untrue. I did not only commenting out the
> > > InputDevice line in the ServerLayout I did also commenting out the whole
> > > Trackpoint section. The result is (xsetpointer -l):
> > > 0: "Virtual core keyboard" [XKeyboard]
> > > 1: "Virtual core pointer" [XPointer]
> > > 2: "USB Maus" [XExtensionPointer]
> > > 3: "Synaptics Touchpad" [XExtensionPointer]
> > > 4: "USB Maus" [XExtensionPointer]
> > > 5: "Generic Keyboard" [XExtensionKeyboard]
> > You probably did not remove enough input device section, there are still
> > too many input devices above,
> I know that and that is exactly the Bug. There was only ONE Pointer
> device configured for the output above.
> > You *really* need to remove the ones that have conflicting
> > /dev/input/foobar device or so (with "mice" conflicting with
> > /dev/psaux and /dev/input/mouse*).
> I heard that and I did for the test. But it doesn't work. X just detects
> two USD mouses where only one is configured. That is a wrong behaviour.
> > We had dozens of bugs like this, all of them got fixed by fixing the
> > config file. So I am just closing this bug.
> Please don't. The bug still persists and hold me from upgrading to the
> newest X server.
> Also you didn't address the problem with the '|' char ('alt gr'+'<').
> Try to use that new X server on a IBM Thinkpad T43p and you will have
> the same problems I had.
> Klaus Ethgen http://www.ethgen.de/
> pub 2048R/D1A4EDE5 2000-02-26 Klaus Ethgen <Klaus@Ethgen.de>
> Fingerprint: D7 67 71 C4 99 A6 D4 FE EA 40 30 57 3C 88 26 2B
Ps. Crossposting to debian-devel. Maybe someone has more knowledge in
the Source of xorg to dive into the error than me.
Klaus Ethgen http://www.ethgen.de/
pub 2048R/D1A4EDE5 2000-02-26 Klaus Ethgen <Klaus@Ethgen.de>
Fingerprint: D7 67 71 C4 99 A6 D4 FE EA 40 30 57 3C 88 26 2B
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)