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

[Andy Whitcroft]

Binary package hint: compiz

Trying to force close a window, and blam. Possibly though it was the broken mumble window which triggered it.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-gnome 1:0.9.4-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Mon Feb 28 23:42:44 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/unity-window-decorator
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /usr/bin/unity-window-decorator
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
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-12-18 (72 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
XsessionErrors:
 (nautilus:17362): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (<unknown>:17359): dee-WARNING **: Transaction from com.canonical.Unity.ApplicationsPlace.SectionsModel is in the past. Ignoring transaction.
 (nautilus:17362): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (nautilus:17362): GConf-CRITICAL **: gconf_value_free: assertion `value != 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.