maximize/unmaximize doesn't restore window size

[Adam Reviczky]

Binary package hint: metacity

If i click on maximize, the window is maximized (all fine). But if i click than on unmaximize, the window is switching back to the original window size for one sec and gets back at maximized size but with rounded borders and at the state of unmaximized. From that on i cannot restore the original window size, only by scale the window size by hand.

This happens for a while on an up-to-date gutsy (atm with):

ii libmetacity0 1:2.19.13-0ubuntu1 library of lightweight GTK2 based Window Manager
ii metacity 1:2.19.13-0ubuntu1 A lightweight GTK2 based Window Manager
ii metacity-common 1:2.19.13-0ubuntu1 Shared files of lightweight GTK2 based Window Manager

Note: seems that not all programs are affected. Programs with that problems are for example: nautilus, pidgin, epiphany.

[Sebastien Bacher (seb128)]

Thank you for your bug. Do you still have the bug? Could you get a debug log as described on the http://live.gnome.org/Bugsquad/TriageGuide/ProductSpecificGuidelines wiki?

[Adam Reviczky (reviczky)]

Yes, i still have the bug.
But the problem is, that it is more randomly, i couldn't find it out yet whats wrong and how.
With nautilus it happens always, with epiphany mostly, and the with the others sometimes i have no problems and sometimes i do.
I'll look into the wiki and post more soon.

[Adam Reviczky (reviczky)]

Since with nautilus i can reproduce this, i did what is written in the wiki, but got nothing.

Here is the output (i couldn't find the logfile):

METACITY_VERBOSE=1
METACITY_USE_LOGFILE=1 metacity --replace

***MEMORY-WARNING***: metacity[27275]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon...
GTK Accessibility Module initialized

[Sebastien Bacher (seb128)]

the log file is likely stored in /tmp and indicated on the command line, no?

[Adam Reviczky (reviczky)]

There is no log in tmp neither on stdout.

I can specific the bug a bit more. It happens when you start a program at fullscreen and than click on unmaximize.

[Pedro Villavicencio (pedro)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

[David Balažic (xerces8)]

Here is a simple way to reproduce the bug:
 - boot the gutsy desktop i386 CD
 - start the "install" icon on dektop
 - maximize the installer wizard
 - unmaximize it

Result:
 - the original size is not restored, but it is still on the maximum size

[David Balažic (xerces8)]

The above was on a HP Compaq nw8440 laptop (vesa gfx, no 3D effects).

On a PC with radeon 8500 (radeon driver, 3D effects) the bug does not happen, as the window is not maximizable there.

Same thing in vmware (vmware0405 driver, no 3D), that is install wizard can be maximized, but not restored correctly.

[Pedro Villavicencio (pedro)]

That's not a metacity bug, rather a bug in ubiquity, please report the bug there if is not already reported.thanks.

[Donn Morrison (donn-morrison)]

I can confirm this bug on metacity 2.20.0 (Ubuntu Gutsy) on a Lenovo T61 Thinkpad.

I've attached the metacity log as requested. It is quite long (~10MB uncompressed), but I stopped it just after I was able to reproduce the bug. In my case, this happens mostly in Firefox and Thunderbird, although I've noticed it with other applications as well. I have a keyboard shortcut mapped to toggle the maximization state of a window, which I use frequently. I've tried to reproduce it but can never get it to happen except by chance.

I must add that it is rather annoying.

Please re-open this bug.

Thank you,
Donn