From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8 Description of problem: Some of my machines have 2 button serial mice. Unless gpm is running, they won't work in X. Any additional info will be provided if you need it. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Use a normal 2 button MS serial mouse 2. Don't have gpm running 3. reboot the machine Actual Results: mouse won't work in X Expected Results: Mouse will work in X Additional info: if gpm is running (or has been run since the last reboot), then the mouse will work in X! Possibly gpm is doing some initialisation thing which should be done in X as well? Worked perfectly with FC1.
Same thing here, although my serial mouse doesn't work during installation either (bug 119474). "service gpm start" loads the "sermouse" kernel module, for instance. But that is not enough if loaded manually. I've noticed that the mouse driver section in /etc/X11/xorg.conf and /etc/X11/XF86Config is wrong. And system-config-mouse doesn't correct it. The config files are not written to by the backend. Only /etc/sysconfig/mouse is correct.
Indeed, after I had configured /etc/X11/xorg.conf manually, my mouse works fine in X.
I have Logitech serial mice locally, and one Microsoft serial mouse. I've tested them all with 6.7.0, and all of them work properly, the Logitech mice using the "MouseMan" protocol, and the Microsoft mouse using the "Microsoft" protocol. The Logitech also works with a few of the other protocols in the past, however I haven't tested other protocols with 6.7.0, but they should work still also, as the X mouse driver hasn't been changed in any major way in ages. I believe this problem is entirely a configuration problem. I'm not sure wether we officially support serial mice in our config tools now or not. Reassigning to system-config-mouse component.
This is intentional; serial mice are to be routed through the input layer, so that config files don't need to be edited. Unfortunately, it's not getting set up right on install because of bug #121139 *** This bug has been marked as a duplicate of 121139 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.