Ubuntu

Mouse cursor wraps around current screen when animated using Xinerama

Reported by Kris Willis on 2009-06-03
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-173 (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: xorg

I'm running a 3 screen setup over two Nvidia cards using Xinerma. When the cursor is animating it can not be moved from the screen that it is currently on, when attempting to drag it to another screen it wraps around to the other side of the current screen and continues to do so until the cursor changes back to a static one.

This bug was not present in 8.10 and has appeared since upgrading to 9.04.

-----------

Release: 9.04

apt-cache policy
xorg:
  Installed: 1:7.4~5ubuntu18
  Candidate: 1:7.4~5ubuntu18
  Version table:
 *** 1:7.4~5ubuntu18 0
        500 http://gb.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: xserver-xorg 1:7.4~5ubuntu18
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-11-generic (buildd@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009
SourcePackage: xorg
Uname: Linux 2.6.28-11-generic x86_64
Xrandr:

glxinfo:

[lspci]
00:00.0 RAM memory [0500]: nVidia Corporation MCP61 Memory Controller [10de:03ea] (rev a1)
     Subsystem: Elitegroup Computer Systems Device [1019:2602]
01:06.0 VGA compatible controller [0300]: nVidia Corporation NV34 [GeForce FX 5200] [10de:0322] (rev a1)
     Subsystem: CardExpert Technology Device [10b0:0401]
02:00.0 VGA compatible controller [0300]: nVidia Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1)
     Subsystem: ASUSTeK Computer Inc. Device [1043:8229]

Bryce Harrington (bryce) on 2009-06-06
affects: xorg (Ubuntu) → nvidia-graphics-drivers-180 (Ubuntu)
Pete (pete123) wrote :

Using the 173.14.18 legacy driver I also have this problem. Oddly the mouse never seems to get stuck on the central screen. However, sometimes the mouse will be on the middle screen, while highlighting text the mouse will act like it is located on either one of the outer screens performing the action there (for example selecting text on the inner monitor could result in highlighting an area of the desktop on the left or right screen). When attempting to move the cursor from the central screen it will then warp (presumably by one screen width) and get stuck wrapping on an edge screen.

However, on a newer machine where the 185.19 beta driver can be used this bug is not a problem. In both cases the machines are using the patched xserver from the m0sia ppa to resolve the cursor left on each screen (bug #357901).

Kris, do you have the chance to try the Nvidia 185.19 beta driver?

Also, when your cursor becomes stuck if you drag a window the first screen crossing it makes the cursor moves as expected but the window itself warps now, followed by crossing the next boundary with the window snapping to the cursor position and the cursor becomes un-stuck?

Pete, unfortunately my two cards are a FX 5200 and 7300 LE so the new beta drivers are not designed for them from what I have read.

I have just tried dragging a window while my cursor is stuck in a loop and I can move the window to my other screens along with the cursor - But because while dragging, the cursor changes from animated to a static clenched fist, this further points to the animation being the problem.

Pete (pete123) wrote :

I wasn't aware that you could use the FX 5200 with 180.xx driver release. Maybe you are using the 173.14.xx release too?

I'm don't think I'm able to try it the other way, i.e 173.14.xx on the newer system as I don't think that release supports the 9 series GPUs.

If anyone else is reading this with 7/8 series GPUs someone needs to test to see if this bug is present in 173.14.xx but not in 180/185.

Pete (pete123) wrote :

I think this may well be related (bug #363375).

Bryce Harrington (bryce) wrote :

I've posted a new version of the -nvidia driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get nvidia-graphics-drivers-180 - 185.18.14 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: New → Incomplete
Pete (pete123) wrote :

My problem only occurs on the system with the Geforce 5 series cards (which are now stuck with the legacy 173.14.xx driver).

On a newer system I've been using the 180/185 series driver from the nvidia installer without this issue ever being apparent.

Bryce Harrington (bryce) wrote :

Okay, sounds like this bug was misfiled to -180.

affects: nvidia-graphics-drivers-180 (Ubuntu) → nvidia-graphics-drivers-173 (Ubuntu)
Changed in nvidia-graphics-drivers-173 (Ubuntu):
status: Incomplete → Confirmed
Pete (pete123) wrote :

I can now confirm this also occurs on 185.19 (although it seems to be less frequently)

After having just upgraded my cards to a pair of 9600GTs, I can confirm that this bug also exists in the 180.44 drivers.

Bryce Harrington (bryce) on 2009-09-02
tags: added: jaunty
Bryce Harrington (bryce) on 2009-10-09
description: updated
schmolch (saschaheid) wrote :

Is there any solution for this in a more recent nvidia-driver or does anyone know a cursor-theme that is not animated?

Pete (pete123) wrote :

I personally haven't had this problem since reinstalling Karmic with driver 190.42, have you tried any of the 190.x series?

schmolch (saschaheid) wrote :

No i have not since i did not see a newer version in synaptic.
I guess i will look again.

schmolch (saschaheid) wrote :

I installed 190.42 from a repository and rebooted. nvidia-settings confirms its updated but the bug is still there.

schmolch (saschaheid) wrote :

So is this a nvidia-bug or a Xorg-bug?

schmolch (saschaheid) wrote :

Is this Xorg-Bug reported to the Xorg guys yet?

schmolch (saschaheid) wrote :

Still not fixed in Lucid.
So nobody gives a fuck that xinerama is broken.
Awesome!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers