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

[dmiranda]

Binary package hint: compiz

unity crashes

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-gnome 1:0.9.4git20110322-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
NonfreeKernelModules: wl
Architecture: i386
CheckboxSubmission: 523487039d9464607924e4e677ae5d5d
CheckboxSystem: 669b662da410063cc918e0f60cf6cddf
CrashCounter: 1
Date: Sat Apr 2 22:52:56 2011
DistroCodename: natty
DistroVariant: ubuntu
ExecutablePath: /usr/bin/unity-window-decorator
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InstallationMedia_: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: /usr/bin/unity-window-decorator
ProcEnviron:
 LANGUAGE=pt_BR:pt_PT:en_US:en
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature_: Ubuntu 2.6.38-7.39-generic 2.6.38
SegvAnalysis:
 Segfault happened at: 0x805bc27: movl $0x0,0x228(%eax)
 PC (0x0805bc27) ok
 source "$0x0" ok
 destination "0x228(%eax)" (0x00000228) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__OBJECT () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: unity-window-decorator crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECT()
UpgradeStatus: Upgraded to natty on 2011-03-08 (25 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu1

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