Description of problem: I have a logitech trackball that I have a custom xorg configuration for so I can emulate scrolling by holding one of the special buttons and then rolling the trackball. I've had this configuration since fc6 and it has worked fine, now all of a sudden its not working. It does however do what it would do in windows/OS x, where if i press the side buttons it will scroll the window up and down, which is cool that the driver now recognizes that, however I like my configuration _much_ better. Version-Release number of selected component (if applicable): xorg-x11-drv-mouse-1.2.3-4.fc9.x86_64
Created attachment 297119 [details] my xorg.0.log
Created attachment 297120 [details] my xorg.conf
Hmm, I thought this might be related to evdev, so I did a Section "Module" Disable "evdev" EndSection but for some reason it still loads. If i look at my Xorg.0.log I see it say "evdev will not be loaded", but it still loads it, and my config is still ignored.
still happening.
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
You're seeing a conflict between hotplugged input devices and the actual devices. These are added with the evdev driver, and default options. Furthermore, evdev grabs the device file, so any device added through hotplug won't feed into /dev/input/mice (i.e. all mice). In your case, this means that your mouse is still there, but since all devices stopped sending to /dev/input/mice it doesn't send any events. The only option for now is to add "Option "AutoAddDevices" "off" to your ServerLayout. This deactivates input device hotplugging and the mouse will use the options specified in the config. Eventually, evdev should get EmulateWheel support [1], but upstream doesn't have it yet. See also [2] Closing as NOTABUG, since it was caused by configuration error. [1] http://bugs.freedesktop.org/show_bug.cgi?id=4147 [2] https://bugzilla.redhat.com/show_bug.cgi?id=446627
*** Bug 457666 has been marked as a duplicate of this bug. ***