Firefox maximized under/over panels after screen size/xrandr changes

Tried starting from command line with 'firefox -width 100 -height 100 (and a few different values) but that doesn't have any effect at all. Seems like it's always maximized.

Workaround found :) First I make it full-screen with F11. Then back again and now it's behind my top/bottom panels. Now I can grab the resize and actually resize it. When I maximize it again after this it's back to normal.

I found out that this is also an issue with Nautilus. There however the workaround cannot be used since you cannot use full-screen mode.

I also discovered from bug #2215698 that this is related to compiz.

I ran 'metacity --replace &' and that enabled me to resize my windows.

I experienced the same thing without a docking station on current Intrepid. I think it's related to having changed screen size, though, as I did connect an external VGA projector recently. In doing so, I ran xrandr --auto to detect the projector size (which is smaller than my screen), then after disconnecting it, ran xrandr --auto again.

I noticed the issue with Firefox, where the steps to reproduce are:
1. Open firefox on desktop #n and maximize it (works normally)
2. Open a URL on desktop #m (eg. in xchat or gnome-terminal)
3. Firefox flashes on the task bar
4. Switch to desktop #n

at which point Firefox is maximized under the panels.

Confirming this seems to be a compiz issue. Running compiz --replace gets it working properly again.

When the Firefox window is in this state, and I use the full-screen workaround to see the window title bar, i can see that the title bar is not in the focused state, and clicking on it doesn't change this. switching workspaces at that point gets it focused again.

on IRC we also found out that the window is in state maximized, but has somehow conflicting properties:

 1. unmaximized is enabled in the window menu (alt + space) - just like its supposed to be for maximized windows
 2. resize is _enable_ in window menu - even though it should be greyed out in maximized state; resizing doesnt work though.

On Thu, Sep 25, 2008 at 12:33:48PM -0000, Alexander Sack wrote:
> on IRC we also found out that the window is in state maximized, but has
> somehow conflicting properties:
>
> 1. unmaximized is enabled in the window menu (alt + space) - just like its supposed to be for maximized windows
> 2. resize is _enable_ in window menu - even though it should be greyed out in maximized state; resizing doesnt work though.

Resize is always enabled for me, even when windows are maximized, regardless
of whether I am experiencing this bug or not. I think compiz doesn't
disable it.

--
 - mdz

switching to metacity or compiz --replace gets it working properly again

Confirming this one with Fully updated Intrepid today.
compiz --replace does not fix the problem, 2x F11 is a better workaround ;)

Opening a link from last.fm or gnome-terminal brings Firefox into this state as well.

I thought this was fixed. I didn't have this bug a long time. About 2xF11 vs. compiz --replace: well 2xF11 brings you back to normal state but you must do it every time you open a link. compiz --replace fix the problem as long as firefox is running, if firefox is restarted, it goes again in fullscreen.

I hadn't seen this in a long time, but have been experiencing it recently on current Jaunty, again with a dual display setup (internal LCD @ 1680x1050 and external display @ 1920x1200).

I'm facing the same problem...... hasn'ta s solution been reached yet.......

This is what I did to solve the problem. I am using Ubuntu 8.10 x64 with Compiz enabled. First, I un-maximized my screen, I noticed that the un-maximized window was beyond the dimensions of the screen and the tool bar (it fit in the screen but just barely), so I hit f11 twice and moved the window around by holding down alt and clicking on the fire fox window. Then I dragged the window down to a size that would for sure fit in-between the menu bars and fit on the screen. I re-maximized the window and quit firefox, now when I relaunch it relaunches in a standard window mode that is not maximized. I think the problem is that the application tries to snap the window within the screen resolution, it is possibly related to the window interaction with Compiz as well and this is just the way that Firefox deals with it. Try this and see if this helps :) Good Luck

If you do as falcon1620 suggested, but then change to another tab and attempt to de-maximize, the window goes once again beyond the boundaries of the desktop. However, hitting F11 two times de-maximizes it to the size you set manually. Not a crippling bug, but annoying.

Ok here is what seems to be a better work around. Delete the .mozilla folder. This restored the defaults and then corrected the problem on startup. Anyone have some extra time on their hands and wouldn't mind going one by one deleting files to find the culprit? lol

Sloan

Kudos to Sloan for thinking of deleting the .mozilla folder!

I played around and found the culprit (for my system anyway): localstore.rdf, located in the .mozilla folder. Just delete the file, and firefox will create a new/fixed one when you use firefox. Now i get to keep my history, bookmarks, settings, etc...

I run 1024x768 and have exactly this issue. After playing around in localstore.rdf I found that these lines should be changed:

  <RDF:Description RDF:about="chrome://browser/content/browser.xul#main-window"
                   screenX="0"
                   screenY="0"
                   width="1024"
                   height="768"
                   sizemode="maximized" />

Into these:

  <RDF:Description RDF:about="chrome://browser/content/browser.xul#main-window"
                   width="800"
                   height="600"
                   screenX="4"
                   screenY="139"
                   sizemode="maximized" />

Which somehow fixed it. Apparently setting the width+height to a value too high (for instance the exact screen resolution) indirectly causes the issue. I don't know what the real problem is.

This is an ancient bug and should be closed due to age. Please log a new bug if this issue is occurring on supported releases of Ubuntu.

Thanks!