using either xf86-input-mouse, or openbsd-input-ws, I have a problem that on the current modular server, the mouse flicks to the left side of screen. This happens when (a) the mouse sensitivity is high (b) I am moving the mouse over GTK apps (c) a lot of pane/button/border related changes happen. Eg, a GTK/Gnome application, drag over its border or an inner-pane border, which causes the border to flick colour AND buttons to bolden AND popups to happen. In these circumstances, the mouse appears to force to absolute_x position zero, no change in absolute_y.
because it happens irrespective of the two input codes, and because they are quite different codes, I believe this lies in the XInput changes inside the server.
this doesn't happen on the older modular-xorg state like 220.127.116.11. It does happen on 1.3.99
I can partially remediate the problem by xset m 1 10 -making the mouse have zero accelleration, and as slow as sludge. its not a complete fix: this still happens.
$ gcc -v
Using built-in specs.
Configured with: /home/nick/work/netbsd/src-current/tools/gcc/../../gnu/dist/gcc4/configure --enable-long-long --disable-multilib --enable-threads --disable-symvers --build=i386-unknown-netbsdelf4.99.28 --host=i386--netbsdelf --target=i386--netbsdelf --enable-__cxa_atexit
Thread model: posix
gcc version 4.1.3 20070620 prerelease (NetBSD nb1 20070620)
$ uname -a
NetBSD garlique.algebras.org 4.99.34 NetBSD 4.99.34 (GGM_ACPI) #2: Mon Nov 5 11:23:46 EST 2007 firstname.lastname@example.org:/data/Build/obj/usr/src/sys/arch/i386/compile/GGM_ACPI i386
it happens dualhead, AND single head.
here is a pointer to some debug info From Blair Sadewitz, which I think is relevant:
I've discussed this problem with Blair in the past. He doesn't have cycles to do a deep debug at this point. I'm just a l(user)
After reading bugs, and seeking advice, I believe this is a duplicate of 3113.
I have marked it duplicate and will comment on 3113: even after the patching, I still have this problem with NetBSD current and 1.4
*** This bug has been marked as a duplicate of bug 3113 ***