Metacity consistently crashes when gajim pops up a dialog

what version of the package do you use? it matches the backtrace of
http://bugzilla.gnome.org/show_bug.cgi?id=311819 which is fixed with the current
version according to upstream

2.11.3-0ubuntu1

I experience the same with metacity 2.11.3-0ubuntu2 when the battery status
alert pops up the low battery dialog. Gnome-panel is 2.11.92-0ubuntu2 and
gnome-applets 2.11.92.1-0ubuntu1. Breezy with up-to-date with complete
ubuntu-desktop, though I have not restarted Gnome since this morning, France.

can anybody getting this crash rebuild metacity with DEB_BUILD_OPTIONS=nostrip set?

Yeh i rebuilt with nostrip and its not crashing

(In reply to comment #5)
> Yeh i rebuilt with nostrip and its not crashing

And with rebuilding the regular package? (I suspect the rebuilding itself,
compiled and linked with newer libraries.)

naw i rebuilt the standard package
and given metacity in the archive was only rebuilt a couple days ago i doubt its
linked to much different.

I also see crashes with the same backtrace. Rebuilding the package with either
'nostrip' set or without it set stops the crashes! (this is with 2.11.3-0ubuntu2).

See also http://bugzilla.gnome.org/show_bug.cgi?id=314442

OK so my rebuild fixed some crashes, such as from gajim, but ti still happens
randomly, just less so.

Trent: If you still get it after a rebuild, could you post a stack trace--with
debugging symbols? (and if so, what's the exact version of Metacity you're
running?)

(The stack trace is invalid as meta_window_place() doesn't call
meta_accel_label_set_accelerator(). It calls a bunch of static functions,
however, so that's probably the cause of the bad trace--but meta_window_place()
is too huge for me to really guess at what's going on. Besides, I have been
totally unable to duplicate this bug using any of the instructions provided at
the various different reports I have seen of it)

As posted upstream:

This is a _really_ recent regression. It didn't happen before I just
dist-upgraded my laptop and now it's happening there too. Here's the chunk of
log from dist-upgrade:

Preparing to replace libmetacity0 1:2.11.2-0ubuntu1 (using
.../libmetacity0_1%3a2.11.3-0ubuntu1_powerpc.deb) ...

Preparing to replace metacity 1:2.11.2-0ubuntu1 (using
.../metacity_1%3a2.11.3-0ubuntu1_powerpc.deb) ...

The problem also goes away for me when I dpkg-buildpackage one for myself.

Ryan: I foudn that building my own package *helped* but it didn't go away, just
happened less. I did build it with nostrip tho

I just saw this happen with gaim today. Also, bug #20517 looks related.

*** Bug 20517 has been marked as a duplicate of this bug. ***

Fixed by the patch in http://bugzilla.gnome.org/show_bug.cgi?id=315000
(uninitialized variable, which explains the difficulty in reproducing...)

I can verify that this patch fixes the problem on my breezy machine.

Yes, this would certainly do it! One of gcc's least useful attributes is that
it zero-initialises all variables when you use the debugging support. I
should've realised that might be an explanation when the crash mysteriously
vanished with -g, but *sigh*.

This bug sounds exactly like what I'm seeing on 2.11.3-0ubuntu2 too. It's really
irritating - it seems to happen every time I shut the lid and come back (ie,
when xscreensaver/unlock stuff is running) and also randomly when I'm working.
Every time metacity restarts, every window slides down the screen by the
distance of the title bar and across to the right a little, and I have to shift
them all back into place. </whine>

I'd love to see the fix uploaded :)

fixed with GNOME 2.12