Comment 1 for bug 325581

Update: After doing some more digging, I grow increasingly suspicious that the root cause is not in evdev, but rather in HAL. It looks like HAL may be reporting the wrong thing and then evdev just acts on the bad information. (Please see the attached lshal output.)

I'm not sure about this analysis; comments from those with more experience would be appreciated. I've tried putting some things in /etc/hal/fdi/policy/ to make the device look less mouse-like, so far without success. (The attached output is from a fresh boot with no such modifications.)