GNOME Bugzilla – Bug 167251
Maximize vertically works incorrectly on Xinerama
Last modified: 2005-05-26 17:08:02 UTC
Please describe the problem: On Xinerama with displays on non-uniform height, trying to maximize windows vertically on the smaller display works fine, but on the larger one windows are completely maximized when using it. After unmaximizing, the windows remain properly vertically maximized. Steps to reproduce: 1. Configure Xinerama so that displays are of non-uniform height 2. Try to vertically maximize a window on the larger display 3. Unmaximize the window to actually get the desired effect Actual results: Window is first maximized completely. Expected results: Only vertical maximization. Does this happen every time? Yes. Other information:
Ok, on Gnome 2.10 (metacity 2.10) on Ubuntu Hoary preview with a 2x1600x1200 MergedFB desktop this same bug still occurs but in a weirder fashion: Any window whose right edge is within perhaps 5-10 pixels of the right edge of either of the screens is first completely maximized when trying to vertically maximize, and reverts to only vertical maximization once unmaximized. Windows not bordering on the right edge of either screen seem to vertically maximize fine.
the problem is that onscreen contraints aren't xinerama-aware; they're based on the root window width and height. With non-uniform xinerama heights its also possible to drag the window completely off the screen into the void region.
I'll just clarify that the new triggers of the bug I noted in comment #1 occur with 2 same-sized screens (both 1600x1200).
I can confirm the behaviour described in comment #1. Here's a snippet from my Device section in xorg.conf: Driver "nvidia" Option "ConnectedMonitor" "CRT, TV" Option "TwinView" Option "TwinViewOrientation" "Clone" Option "MetaModes" "1280x960,NULL; 640x480,640x480; 800x600,800x600; 1024x768,1024x768" I can reproduce the bug in all modes, even 1280x960 (which is not cloned).
I suspect this may be a duplicate of bug 302204. Could someone with Xinerama try the patch in that bug and report whether that fixes the issue?
This fixes it for me (2 x 2048x1536). Thanks
Cool, I'll mark as a duplicate then, thanks Ignacy. *** This bug has been marked as a duplicate of 302204 ***