[Bug 563100] Re: Mouse movement corrupted with Xinerama enabled

Alberto Milone alberto.milone at canonical.com
Tue Jun 22 09:34:46 BST 2010


@antony73: The fix is still in lucid-proposed, hence it's "Fix
Committed".

Please test the package in -proposed and let us know if it solves the
problem.

** Changed in: xorg-server (Ubuntu Lucid)
       Status: Fix Released => Fix Committed

-- 
Mouse movement corrupted with Xinerama enabled
https://bugs.launchpad.net/bugs/563100
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is a direct subscriber.

Status in X.Org X server: Unknown
Status in “xorg-server” package in Ubuntu: Fix Released
Status in “xorg-server” source package in Lucid: Fix Committed

Bug description:
Impact:  mouse movements are incorrect when a display is placed to the left of or above the "primary" display (negative coordinates in use)
How the bug is addressed: revert to having signed ints representing coordinates on screens so that negative coordinates can be properly used
Patch: http://bugs.freedesktop.org/attachment.cgi?id=35383
Testcase: see original report
Regression potential:  no obvious regression potential

=== Original report  ===

Binary package hint: xorg

The mouse is unusable on a second monitor using the nvidia drivers and Xinerama (Installed: 2:1.1-2).  Upon moving to the second screen, the mouse cursor movement is erratic (although it does respond vaguely to physical mouse movement).

The problem was introduced with lucid (and continues in beta 2).  The mouse works as expected on the second screen in both intrepid and karmic with exact same xorg.conf and nvidia drivers.

The problem appears even with only the minimal settings in xorg.conf to enable dual monitors.  The problem appears whether the second monitor is rotated or not rotated.  The problem does not occur with nvidia's TwinView implementation.

The mouse and all other aspects of X work fine in lucid *without* Xinerama enabled.  Enabling Xinerama causes no problems except this one.  The bug is not present in Debian unstable.

The new bug of course forces one to use separate X servers when wishing to rotate only one monitor in a set -- a limitation that was not present in prior releases of Ubuntu or other distributions.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xorg 1:7.5+5ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-20.30-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-20-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Apr 14 09:15:52 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406)
MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-20-generic root=/dev/mapper/vg0-root ro
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
Xrandr:
 Error: command ['xrandr', '--verbose'] failed with exit code 1: Xlib:  extension "RANDR" missing on display ":0.1".
 RandR extension missing
dmi.bios.date: 04/16/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F9
dmi.board.name: EP45-UD3P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd04/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EP45-UD3P
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro:             Ubuntu
 codename:           lucid
 architecture:       x86_64
 kernel:             2.6.32-20-generic







More information about the Ubuntu-sponsors mailing list