After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 140423 - Window sizes not restored properly when loading a session.
Window sizes not restored properly when loading a session.
Status: RESOLVED INCOMPLETE
Product: metacity
Classification: Other
Component: general
2.7.x
Other Linux
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2004-04-18 16:51 UTC by mjrauhal
Modified: 2009-01-19 20:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description mjrauhal 2004-04-18 16:51:20 UTC
Background: I have two 1600x1200 screens (non-xinerama). I'm not marking this as
multihead though, since I don't think it should be relevant.

Problem: I have, on the first screen, two Galeon browser windows that are
vertically maximized and take half the horizontal space. I also have an
Evolution window that matches one of the browser windows.

The session is saved as such (well, there are a few gnome-terminals also on both
screens, but they come out fine). However, when I log in, the galeon windows end
up not vertically maximized, but rather there's a free space about the size of a
window title bar below the windows. Also, the Evolution window is a bit larger
than it should be in both dimensions.

When copying the saved galeon session to .galeon/session_crashed.xml, galeon
restores the session with the windows maximized, so I don't think the problem is
there. Also Evolution windows are sized just fine when launched from the launch
button in panel (dragged from the menu).

This seemed to work with Sawfish before I upgraded to gnome 2.6.
Comment 1 Thomas Thurman 2008-02-18 01:01:25 UTC
Reporter: Can you tell us whether you are still having similar problems?
Comment 2 Christoph Wurm 2009-01-19 20:21:13 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!