Auto-protocol detection for driver mouse stopped working for Diamondback razor mouse. Reproducible: Always Steps to Reproduce: 1. Configure Xorg.conf to use driver mouse and use protocol auto. 2. StartX 3. Test all buttons using xev. Actual Results: The correct protocol doesn't get detected (unkown witch). Expected Results: Detect the correct protocl as in 1.4
Are you sure it's not another case of "I failed to read the upgrade guide and emerge xf86-input-evdev" ?
No I didn't use evdev... and you are right it's would indeed be a xf86-input-mouse bug. Actually evdev is sort of ok (other then the fact the scroll doesn't get mapped by automaticly, but this bug isn't about that). Also if i'd be using evdev and i don't have the xf86-input-evdev I wouldn't have a moveable mouse at all (but my mouse DID move) ... (doubt X will even start).
Please attach your Xorg.0.log file and post your "emerge --info" as well. Thanks in advance.
(No exactly like emerge --info, but should contain the same info, (if anything important is missing scream bloody murder) ) Compiler: CXX: x86_64-pc-linux-gnu-g++ 4.3.2 CXXFLAGS: -O2 -pipe -pipe -march=athlon64 -fpic -ftracer -msse -msse2 -m3dnow -mmmx -mfpmath=sse -ftree-vectorize -fomit-frame-pointer -Os LDFLAGS: -Wl,-O1 DATE: 2009-04-13T17:52:26+0200 Libraries: C++ Library: GNU libstdc++ 20080827 Ps. If someone can tell me how to see witch mouse-protocol has been autodetected, that might help.
Ow xorg.log contained no usefull information to my knowledge, as xorg never mentions anything about the mouse protocol (or the mouse).
Reopen this bug when you provide the requested information.
Sure sticking the head in the sand will help ... Typical solution "needinfo" ... whatever ... I'll just stay with the old xorg server and hope they one day will fix a bug. /me adds gentoo to the list of "bad" projects.
