unity-window-decorator crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECT()

[Mark Shuttleworth]

Binary package hint: compiz

This is a regular crash for me. Might be a dup of the other one, will check the stack trace.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-gnome 1:0.9.4-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i686
Architecture: i386
CrashCounter: 1
Date: Thu Mar 3 16:37:13 2011
ExecutablePath: /usr/bin/unity-window-decorator
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100201)
ProcCmdline: unity-window-decorator
ProcEnviron:
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 SHELL=/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x805bc9b: mov 0x224(%eax),%eax
 PC (0x0805bc9b) ok
 source "0x224(%eax)" (0x00000224) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__OBJECT () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Title: unity-window-decorator crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECT()
UpgradeStatus: Upgraded to natty on 2010-07-25 (221 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (nautilus:8810): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (unity-window-decorator:8921): Gtk-WARNING **: cannot open display: :0.0
 (gwibber:8813): GStreamer-CRITICAL **: gst_debug_add_log_function: assertion `func != NULL' failed

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #724874, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.