Bug 314534 – [breezy] odd metacity crash when terminating battstat applet

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 314534 - [breezy] odd metacity crash when terminating battstat applet


Summary:	[breezy] odd metacity crash when terminating battstat applet


Status:	RESOLVED DUPLICATE of bug 314442

Product:	metacity
Classification:	Other
Component:	general
Version:	2.11.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Metacity maintainers list
QA Contact:	Metacity maintainers list

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2005-08-26 03:28 UTC by Allison Karlitskaya (desrt)
Modified:	2005-08-29 20:14 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Allison Karlitskaya (desrt) 2005-08-26 03:28:11 UTC

I was just hacking on the applets a bit and I terminated the battstat applet
with ^C.  As expected, the "Exited unexpectedly" dialog was thrown up by the panel.

At this point, though, metacity also crashed.  This happens 100% (but it didn't
used to).

Version: 1:2.11.3-0ubuntu2

Here's a somewhat unhelpful trace (breezy doesn't have a debugging symbols
package for metacity).

Program received signal SIGSEGV, Segmentation fault.

+ Trace 62625

Thread NaN (LWP 22432)

#0 meta_accel_label_set_accelerator
#1 meta_window_place
#2 meta_window_constrain
#3 meta_window_activate
#4 meta_window_move_resize
#5 meta_window_move_resize_now
#6 meta_window_queue_calc_showing
#7 meta_window_should_be_showing
#8 meta_window_calc_showing
#9 meta_window_calc_showing
#10 g_child_watch_add
from /usr/lib/libglib-2.0.so.0
#11 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#12 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#13 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#14 main

Comment 1 Allison Karlitskaya (desrt) 2005-08-26 04:57:12 UTC

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) ...

Comment 2 Elijah Newren 2005-08-26 15:39:33 UTC

Sigh.  meta_window_place does NOT call meta_accel_label_set_accelerator so the
stack trace is corrupt.  Is there any chance you could recompile Metacity and
get a stack trace with debugging symbols?  Someone else reported a metacity
crash with 2.11.3 using version 2.2.8 of the GIMP but I couldn't reproduce...

Comment 3 Elijah Newren 2005-08-26 20:36:20 UTC

Marking as NEEDINFO as I can't reproduce with 2.11.3 (well, HEAD, but there have
been no changes since 2.11.3) and the stack trace is useless to me.  (Are there
any Ubuntu patches that might be screwing things up or am I just not aware of
all the necessary steps to duplicate?)

Comment 4 Elijah Newren 2005-08-29 20:14:30 UTC

Same stack trace has shown up in bug 314442, and is tracked downstream at
http://bugzilla.ubuntu.com/show_bug.cgi?id=14145.  Marking as a duplicate.  (I'd
still appreciate more information--is it the case that recompiling a stock Gnome
version of Metacity fixes this problem for you as Crispin seems to suggest?)

*** This bug has been marked as a duplicate of 314442 ***