On Thu, 2008-02-28 at 08:56 -0800, Andrew Farris wrote: > David G. Mackay wrote: > > After a recent set of updates, the mouse stopped working in X. > > Investigating the problem, I noticed that there are now two mice showing > > for info mice in the qemu console. Doing a set_mouse 0 in the qemu > > console restores the mouse function. Other VMs (i. e., non f9-alpha > > VMs) are not experiencing this behavior. Can anyone give me an idea of > > which component to file a bz entry in? > > > > Dave > > This probably has to do with the new system of auto configuring input devices > (hal, xorg auto devices, managed evdev), just like the keyboard problems in the > list at present. There is a bug re vmware mouse misbehavior [1] and keyboards > [2] that are related. You could confirm that adding Option "NoAutoAddDevices" > to your xorg.conf ServerFlags also fixes the problem (while not forcing > set_mouse 0). > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=434807 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=434669 Very interesting. I added the serverflags section and set option NoAutoAddDevices to true. This did indeed correct the problem. However, info mice still showed two mice, with the vmmouse selected. Then I noticed that my xorg.conf was using the VMMOUSE module, even though I'm running qemu-kvm. Changing it to use Mouse0 and the mouse driver also corrected the problem. Dave -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
