GNOME Bugzilla – Bug 575076
Maximised windows are covered by top panel, cover bottom panel
Last modified: 2010-01-14 18:31:47 UTC
Please describe the problem: See screenshot. Can not get to any menus or buttons when it works like this. Steps to reproduce: 1. Have a maximised window to test with, e.g. Firefox 2. Run ./gnome-shell --replace 3. Maximised windows cover/ are covered by top/bottom panel Actual results: See #3 Expected results: The windows should be maximized within the boundaries of the panels Does this happen every time? Yup Other information: Will add screenshot in a sec
Created attachment 130510 [details] This is an image of the entire screen
that's not "maximized", it's "fullscreen". the fact that it covers the bottom panel in that mode is correct, and the fact that it *doesn't* cover the top panel is being fixed as part of bug 571827. *** This bug has been marked as a duplicate of 571827 ***
Ketil said IRC that the window was actually a maximized window not a fullscreen l; on the other hand, he said that after runnning gnome-shell synaptic was permanently fullscreen (not maximized) even after rebooting, so something is going on weird. Don't think it's a straightforward dup.
Just adding that I tried something else: Maximizing windows within gnome-shell works like it should. Having windows maximized while launchin gnome-shell makes the bug visible. Noting also that I use Ubuntu 8.04, 32 bit, on Intel graphics.
Just managed to fix the Synaptic fullscreen problem described by Owen. Compiz Fusion settings (CCSM): Workarounds -> Disable and reenable Support for legacy full screen windows. I haven't touched CCSM or other Compiz settings for months, so I have no idea what did this, but nice to have it sorted. Other than that, the other problems remain, AFAIK
I can't reproduce this; starting gnome-shell with a maximized firefox doesn't behave any differently for me than starting firefox from within gnome-shell. (Unfortunately, something seems to have gone bad on my machine; starting firefox at all now creates all sorts of texture confusion, with my terminals getting streaky and diagonal, and bits of firefox showing up in the desktop window, etc :-/)
Seems to work for me also at this point. A quick test worked anyway.
I get the correct behaviour from a maximised window (trying firefox in maximum window size, for instance), but not from a window in full-screen mode. I tested this with alien-arena (set to run in full-screen mode at 1024 x 768, which isn't my standard resolution), and get some weird behaviour: Use case 1: - go to overlay - search for alien-arena - double-click on the icon, or just press "Return" - alien-arena starts out in full-screen mode, but seems to have been pushed down by the top panel. Seems to work OK. - the resolution has changed, and this is visible in the change to the text of the "Activities" label. The notification area, clock and my name have disappeared (presumably off to the right). - when I exit it, it seems to have been attached to the workplace I'd previously be using. Use case 2: - go to overlay - search for alien-arena - drag the application onto a workspace - the resolution changes, and I see a zoomed-in view of part of the overlay screen, and the music starts. There's no sign of the game. - if I press "Return" I move to the same behaviour as in case 1 (all works, but pushed down). - on one occasion, when trying to exit, another window on the same workspace appeared in front of the alien-arena window, and I had to minimise it to exit the game, but I've been unable to reproduce this. Use case 3: - go to overlay - search for alien-arena - drag the application onto a workspace - the resolution changes, and I see a zoomed-in view of part of the overlay screen, and the music starts. There's no sign of the game - if I attempt to select a different workspace to the one onto which I dragged the application, I sometimes discover that I've lost mouse control, though I seem to have at least some keyboard control. I've tried this several times, and got several behaviours: none of which made very much sense, and one of which required me to restart X (I was stuck in the game with no keyboard control). I've also managed to get back to the overlay screen and reselect the workspace to which I originally dragged the app, in which case things seemed fine. There's clearly weird stuff going on, particularly in case 3, so I guess we need to ask ourselves what behaviour should take place when a user drags an application to a particular workspace which wants to go fullscreen. I suspect that we can't tell until it starts, but I don't think it's fair to force a user to do this (assuming they want to start the app in a new workspace): 1. go to overlay 2. create a new workspace 3. select that workspace 4. go back to overlay 5. double click on the app (assuming that they realise it's going to go fullscreen in the first place). The alternative is to have some sensible behaviour when we drag an application which _may_ go fullscreen. This might be worth an email discussion - I'll leave it in your hands, folks. -Mike.
comment 7 says it works for the OP, comment 8 is actually bug 584526: (In reply to comment #8) > I tested this with alien-arena (set to run in full-screen mode at 1024 x 768, > which isn't my standard resolution), and get some weird behaviour: