Comment 75 for bug 583760

I had this problem a while ago and rolled back nouveau and the problem went away (well it didn't happen again - but of course that's no certainty that the bug was not present in the earlier versions)

The old nouveau that appears to be OK is:
xorg-x11-drv-nouveau-0.0.15-17.20091105gite1c2ef
(that's the one I rolled back to when the mouse problem first showed itself)

5 days ago I did a full update that included:
kernel-2.6.32.16-141.fc12.x86_64 and
xorg-x11-drv-nouveau-0.0.15-21.20091105gite1c2efd.fc12.x86_64
and the problem has happened again today (for the first time since the rollback)

Xorg.0.log info:

First nVidia message is:
nVidia Corporation GeForce 8600 GTS rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf4000000/33554432, I/O @ 0x0000b000/128, BIOS @ 0x????????/131072

I use a USB mouse, log says:
Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)

I also have a USB Bamboo that the log finds BEFORE the mouse:
Wacom BambooFun 6x8
(I don't use the pen)

The rest of the log looks like status dumps without any error messages.

In my case it's a dual display and acts even stranger when the problem occurs (randomly?):
The left display shows the mouse correctly (but jerky)
In the right display (which has the menu bar) the mouse works but it is invisible
More strange: the mouse image is partially still shown on the edge of the left screen while using the right screen

When the screen saver comes on the mouse is still visible in the left screen
It doesn't fix the problem when the screen comes back
(thought I'd mention that because I've seen it said elsewhere)

It maybe happens when mplayer is playing fullscreen
(so a fullscreen app may be needed to activate the bug)
Of course when the problem wasn't there I was using the current mplayer version constantly also

The first dmesg error was:
[drm] nouveau 0000:01:00.0: EvoCh 0 Mthd 0x0000 Data 0x00000400 (0x0002 0x01)

followed by lots of the cursor messages (both 'hiding' and 'unhiding')