Bugzilla – Bug 385553
metacity fullscreen not using the whole screen area
Last modified: 2020-05-19 09:21:33 UTC
This is the metacity specific part of bug 343858. Federico had a patch: https://bugzilla.novell.com/attachment.cgi?id=190636 but it seems to be causing problems.
Can we make this bug a blocker? This is deeply annoying.
Ted, do you have a machine with the problematic Intel chipset? Would you be willing to test some packages with patches? :) Regardless of that, can you please provide the output of xprop -root | grep WORKAREA when you experience the problem with metacity? Also, can you please provide the output of "xdpyinfo" and "xrandr"?
My laptop is a Dell 700m. Chipset is 855GM When in GNOME(metacity) I hit the problem whenever I attempt to maximize a window when it is in the top left 1024x768 pixels of the screen. As soon, as the window moves outside of that area in any way I am able to fully maximize. Native resolution is 1280x800. Note that this also affects video playback as well. When totem is in the top left 1024x768, it will not draw the video, as soon as it moves out of that area, it draws the video. Requested output will follow shortly. Along with Screenshot demonstrating the problem. -Ted
Created attachment 215775 [details] output from (xprop -root | grep WORKAREA)
Created attachment 215776 [details] output from xdpyinfo
Created attachment 215777 [details] output from xrandr
Created attachment 215779 [details] Screenshot showing firefox maximized to only part of the screen
Thanks, Ted. I'll revise the patch and make some packages for you to test.
I also have this issue with a Dell E1505. 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) I usually just xrandr --output VGA --off to fix it, but this is obviously a problem for when I want to use a projector
Created attachment 216250 [details] output from xrandr
Created attachment 216251 [details] output from (xprop -root | grep WORKAREA)
Created attachment 216252 [details] output from xdpyinfo
Please download the packages here: http://www.gnome.org/~federico/misc/metacity/ Then, please do this: 1. Install the packages 2. Run this from a terminal: METACITY_DEBUG=1 METACITY_VERBOSE=1 METACITY_USE_LOGFILE=1 metacity --replace 3. Try to maximize a window or reproduce the bug. Please tell us if this works. If it doesn't, attach /tmp/metacity-XXXXX-debug-log-XXXXX to this bug; it contains some logging information that will be useful to see what's going on :)
Will test this this afternoon. I've been hitting a new bug though where the mouse freezes up as soon as I enter gnome. I will be re-installing later today and will post the update.
(In reply to comment #14 from Ted Bullock) > Will test this this afternoon. > > I've been hitting a new bug though where the mouse freezes up as soon as I > enter gnome. This is bug 388236, there are test packages in the bug (or possibly synced to factory now).
After applying measures from comment #13 it seems to work here. Not only do windows maximize properly, but also does the tray applet show correct resolution (1280x800) on mouseover as well offer a choice of screen resolution, screen rotation and refresh rate in the context menu. The created log still contains errors.
Created attachment 217096 [details] metacity log
(In reply to comment #9 from John Anderson) > I usually just xrandr --output VGA --off to fix it, but this is obviously a > problem for when I want to use a projector For me xrandr --auto works also as workaround
There is one problem left though. For me this _only_ works for the user that was active when I implemented the change. Other users get to see just background, no panel no icons. When I, again change DISPLAYMANAGER_RANDR_MODE_auto to 1280x800_60 68.90 1280 1301 1333 1408 800 804 808 816 -hsync -vsync from the default 1024x768_60 64.11 1024 1080 1184 1344 768 769 772 795 -HSync +Vsync it is working for other users as well, only the tray applets context menu then offers "Screen Rotation" as only option.
Thanks for the log file, CJP :) This indicates that everything is working fine. The rest of your problems are not related to Metacity. I submitted the attached patch to autobuild for openSUSE 11; it should hit Beta4, I think. * Wed May 21 2008 - federico@novell.com - Added metacity-bnc385553-buggy-intel-xinerama.diff to fix https://bugzilla.novell.com/show_bug.cgi?id=385553 - If there are just two overlapping monitors, make Metacity think that there is a single big monitor. This should fix maximized windows on laptops with buggy X drivers for Intel graphics chipsets.
So the version in factory right now does report that the resolution is correct for my laptop (1280x800). However, windows are still not maximizing to the fill the entire screen. That said, the panel is covering the entire bottom of the screen. Thoughts? -Ted
Ted, could you please run rpm -q --changelog metacity | head You should see something like * Fri May 16 2008 federico@novell.com - Added metacity-bnc385553-buggy-intel-xinerama.diff to fix https://bugzilla.novell.com/show_bug.cgi?id=385553 - If there are just two overlapping monitors, make Metacity think that there is a single big monitor. This should fix maximized windows on laptops with buggy X drivers for Intel graphics chipsets. If you get something else, then you need a newer package. If you *do* get something similar, could you please run METACITY_DEBUG=1 METACITY_VERBOSE=1 METACITY_USE_LOGFILE=1 metacity --replace again and attach /tmp/metacity-xxxx-debug-log-xxxx to this bug? Make sure you send the latest file, as you may have several of them in /tmp now :)
Created attachment 217890 [details] metacity log (from dell 700m/855gm) Ok, so it turns out that the package in factory now was last update updated May 13, so it didn't include your change. That said, I installed the updates you posted above. Result was not good, metacity died. See new attachment for log
@ Federico: In Comment #20 you state: "The rest of your problems ( from Comment # 19 ) are not related to Metacity" which isn't exactly helpful. Would you mind pointing me to the right direction ( Either open Bug on that, against what ?? Or else follow an existing one. ) Thanks
Whatever is intended here, it is now a real blocker. Updating a system previously clean installed from factory & updated just now renders UI completely inaccessible for both users ( root & casualprogrammer ) only the background is visible, no panel, no icons. For the system used to verify this fix in comment #19 the only functional user now has background and panel, but no icons and backround has no context menu.
I reverted the patch for now.
ok, back to major then
As suggested by Vuntz, I checked the broken installation if metacity is running at all. As I reported to him on IRC: casualprogrammer: vuntz: background=yes, panel=no, icons=no, context-menu=no, metacity_running=yes
Created attachment 218200 [details] metacity-bnc385553-buggy-intel-xinerama.diff Argh! My patch had a stupid bug which could cause crashes (array bounds overflow). This is the new patch I'm building...
Latest patch works great for me!
Confirmed on IRC that the new patch works :) I've submitted this to autobuild for openSUSE 11.0. * Mon May 26 2008 - federico@novell.com - Updated metacity-bnc385553-buggy-intel-xinerama.diff for https://bugzilla.novell.com/show_bug.cgi?id=385553 - Deal with buggy Intel graphics drivers. Fix an array bounds overrun in the last version of the patch. Casualprogrammer, can you please install from here while the packages get built for updates: http://www.gnome.org/~federico/misc/metacity/ If you find any further problems, please file new bugs for them --- I'm 99% convinced that Metacity is fixed for this general Intel 915 issue :)
works here too :-) also works for newly added users. only the tray icon says we are at 1024x786 and doesn't offer a choice of resolutions, while choosing "Screen Resolution" from the control center shows 1280x800
Yeah, the tray icon is likely to be broken; that may be bug #385171. I'll talk to you on IRC about this.
The bug has made it to RC1 somehow :-( Installing rpm from comment #31 still fixes it, although packages are named identical, what gives ??
OK, I just checked - indeed the patch didn't make it for RC1. It will be in openSUSE 11.0 final (it's in now). Sorry about the identically-named patches; I expected the build system to bump the revision number automatically, but it seems that that doesn't happen if you build things by hand...
*** Bug 396044 has been marked as a duplicate of this bug. ***
This is an autogenerated message for OBS integration: This bug (385553) was mentioned in https://build.opensuse.org/request/show/807148 Backports:SLE-12-SP4 / atril+caja+caja-dropbox+caja-extensions+caja-terminal+engrampa+eom+filemanager-actions+galculator+gtk2-engine-murrine+gucharmap+libfakekey+libmatekbd+libmatemixer+libmateweather+marco+mate-applet-softupd+mate-applets+mate-backgrounds+mate-branding-openSUSE+mate-calc+mate-common+mate-control-center+mate-desktop+mate-eiciel+mate-icon-theme+mate-icon-theme-faenza+mate-indicator-applet+mate-media+mate-menu+mate-menus+mate-netbook+mate-notification-daemon+mate-panel+mate-polkit+mate-power-manager+mate-screensaver+mate-sensors-applet+mate-session-manager+mate-settings-daemon+mate-system-monitor+mate-terminal+mate-themes+mate-user-guide+mate-user-share+mate-utils+mathjax+metacity+mozo+pluma+python-Unidecode