when I play a video via Textured Video and move the window onto the border between my two screens, I get the video splitted in the half and the two halfs placed onto the wrong sides of the screen. It beginns, when approx. 50% of the window are place on the second screen.
I'll attach a screenshot, that should explain it better. You can see the offset in the picture and the red line marks the approximate place, where the two screens touch.
Created attachment 24405 [details]
Screenshot of the bug
Please provide more info according to http://intellinuxgraphics.org/how_to_report_bug.html, like driver version and Xorg.0.log.
Are you using composite window manager like compiz?
Ok - here we go:
Chipset: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller
system architecture: i686
kernel version: 2.6.29
Linux distribution: Debian
Machine or mobo model: Fujitsu Lifebook E8410
Display connector: LVDS + DVI-D
Steps to reproduce:
1.) Setup Dualhead:
xrandr --output LVDS --mode 1680x1050 --output TMDS-1 --mode 1280x1050 --right-of LVDS
2.) Run totem/xine/whatever XV enable player available
3.) move the video window over the border between the two screens
Created attachment 24445 [details]
Xorg.0.log of current session (the bug is still there ;-)
I just ran into the same bug, and also came up with a fix which I've posted here:
If you want to test the fix, that would be great, (and please report back if it doesn't work for you).
Otherwise, I'll be closing this bug as soon as the fix lands in the repository. I do expect that the fix will be in the upcoming 2.7 release of the driver.
Thanks for your report,
Just applied the patch to git version 375b2e40fcb17e94538a75392950e2533c1bb031 and it works as expected. I still have to test head, but yesterday head just gave me a white window.
(In reply to comment #6)
> Just applied the patch to git version 375b2e40fcb17e94538a75392950e2533c1bb031
> and it works as expected. I still have to test head, but yesterday head just
> gave me a white window.
Thanks for confirming the fix. It's in both master and the 2.7 branch now.