GNOME Bugzilla – Bug 331476
Window is located incorrectly in xinerama mode
Last modified: 2007-02-02 09:30:58 UTC
Please describe the problem: When using xinerama (desktop stretched to two physical displays), GCompris window tries to position itself incorrectly between two screens (displays). Program should be located only in one window. Now user is able to see lots of black space and a half of GCompris window in left screen. The right screen doesn't even show the rest of the GCompris window, but a normal portion of desktop instead, so half of the Gcompris screen disappears. Steps to reproduce: 1. Configure X in xinerama mode; two displays, same resolutions in both. 2. Start GCompris 3. Actual results: I see only half of the window, positioned incorrectly between two screens. Expected results: See the window centered in one screen. Does this happen every time? Always Other information: I'm using GCompris 6.5.3 in Ubuntu 5.10, Gnome 2.12.1, X.org 6.8.2. Graphics card is Matrox G450 dualhead with Matrox binary HAL library.
Created attachment 59540 [details] Screenshot of the xinerama situation
Created attachment 59541 [details] xorg.conf
GCompris uses xrandr to run in fullscreen. We don't manage xinerama at all. I don't see what we can do. Does this problem appear only with GCompris or other application have the same issue when going in fullscreen?
(In reply to comment #3) > Does this problem appear only with GCompris or other application have the same > issue when going in fullscreen? I don't use many programs in fullscreen mode, but at least these work as expected: tvtime, (g)mplayer, xine, Mozilla Firefox in fullscreen mode. GCompris is the first one hiding parts of its screen. The most usual problem is, that popups, messages etc. pop up between two screens. Thanks for pointing out the technic you use. There seems to be (at least) one this kind of bug in x.org bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=1423
Now GCompris uses xvidmode intead of xrandr. Can you please test again and tell me if this improves the situation.
I tested version 8.2.2 and it works fine with xinerama mode. Problem solved! I'll try to close the bug.