GNOME Bugzilla – Bug 108634
maximized state not saved in session
Last modified: 2011-02-14 13:05:16 UTC
A Debian user reports (http://bugs.debian.org/174291) When I start galeon after it has crashed, the window is positioned a few pixels higher and to the left of where it should be. The window had been maximized to the full height and width of the screen, and positioned at (0,0). But when it comes up after a crashed session, it is always up and to the left, far enough that the window manager's bar across the top of the window is not accessible, and I have to use a keyboard shortcut to move it since the mouse can't grab the title bar. I've been able to reproduce this with galeon 1.3.3 (and fvwm as wm) as follows: - maximize window - kill -11 the galeon process - close crash dialog - restart galeon - choose "restore session the window is now a bit to the left and top, outside the destop.
We don't seem to be saving whether or not the window is maximized in the session. When the session is restored, the window size is handled wrong.
Well, this is kind of maybe related, so I'll mention this here: My Galeon windows are only vertically maximized, yet they seem to be restored as being a bit shorter; in fact, the size difference is about the same as the title bar's height. The position is restored correctly (looking at the top left corner). Galeon 1.3.17 here, and running an Ubuntu system upgraded from Debian Sid, though the problem was present before said upgrade too.
Thanks for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. Galeon developers won't be fixing or back porting any fixes for this version. Please upgrade to latest stable Galeon version to receive bug fixes. We are sorry it could not be fixed for your version.