Bug 13780 - xf86-video-mga 1.9.100: Mouse position wrong when using rdp and dual-head
Summary: xf86-video-mga 1.9.100: Mouse position wrong when using rdp and dual-head
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/mga (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Tilman Sauerbeck
QA Contact: Xorg Project Team
URL: http://bugs.debian.org/cgi-bin/bugrep...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-22 05:09 UTC by Brice Goglin
Modified: 2018-06-12 19:08 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Brice Goglin 2007-12-22 05:09:29 UTC
Reported by Alexander Elbs recently on the Debian BTS, he's using 1.9.100 on a MGA G400/G450 (rev 82). See the URL above for the full config and log. He says:

"my two outputs are configured this way:

xrandr --output VGA1 --preferred --right-of VGA2
xrandr --output VGA1 --mode 1280x1024 --rate 75
xrandr --output VGA2 --mode 1280x1024 --rate 75

When I use krdc (rdesktop) to a windows client or nxclient to
another linux box the mouse pointer gets set to the wrong
position when the mouse pointer should be inside that
window.
It seems the mouse pointer is shifted one screen to the right:
When the rdp window is on the left screen and the mouse pointer
inside it I can see the pointer on the right screen. The pointer
behaves normally otherwise e.g. it changes its form at the edge 
of a (remote) window, but its very hard to find that edge of
course :)
As soon as I leave the rdp window the mouse pointer jumps back to
its correct position.

With 'xrandr --output VGA1 --same-as VGA2' I don't get this behaviour:
everything works fine."
Comment 1 Adam Jackson 2018-06-12 19:08:32 UTC
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.