Mouse cursor not erased from last position when moving screens

[John Costella]

[FIXED: I used Hardware Drivers to install the latest NVidia drivers (didn't fix it, but didn't kill my display like the recent NVidia driver auto-update did), and then ran 'sudo nvidia-settings' to overwrite my xorg.conf file with its preferred settings -- note that running it from System / Administration didn't do the 'sudo' and caused all sorts of grief because it can't save to xorg.conf.]

I've been running the same (manually edited) xorg.conf with an Nvidia display on a Dell Precision M65 with twin screens (inbuilt is 1920 x 1200; external is 1680 x 1050) since Gutsy.

I finished upgrading to Jaunty on Saturday, and on the single built-in laptop screen, everything is ok.

Docking the machine at work today, when sliding the mouse left and right between the two screens, the last mouse cursor bitmap is left on the screen that the mouse exits. When re-entering that screen, the "orphaned" mouse cursor bitmap is removed (i.e. at any one time, there is one "orphan" mouse cursor image, on the screen that the mouse is not currently on).

Never had this problem before, but it has been a real pain for us to get these Dell Nvidia cards working properly on any version of Ubuntu or Kubuntu. (Unfortunately, no one else here uses the twin screens -- they just use my manually hacked xorg.conf to get the damn screens working at all.)

Thanks
John

[Yahooguntu (yahooguntu)]

I can confirm this bug in a fresh install of Jaunty with the 180 driver.

[Sense Egbert Hofstede (sense)]

Thank you for helping with making Ubuntu better by reporting this bug.
It has been a long time since you've said you could fix this bug by changing the Xorg.conf configuration file with nvidia-settings. However, if the default configuration would cause ugly cursor behaviour it is still a bug.
Could you please confirm if this bug still occurs with the default configuration and a new version of Ubuntu?

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.