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

[Id2ndR]

Binary package hint: compiz

Not sure how to reproduce, but the stack trace may indicate in which circumstances it crashed.

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 x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CheckboxSubmission: 1085bd3e1d3dc5fdefc443fc7f3687c2
CheckboxSystem: f78c696d4c0399fa91f9da1b540d7fd0
Date: Sun Apr 3 14:05:10 2011
DistroCodename: natty
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/unity-window-decorator
ProcCmdline: /usr/bin/unity-window-decorator
ProcEnviron:
 LANGUAGE=fr_FR:fr:en_GB:en
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature_: Ubuntu 2.6.38-7.39-generic 2.6.38
SegvAnalysis:
 Segfault happened at: 0x415baf: movq $0x0,0x318(%rax)
 PC (0x00415baf) ok
 source "$0x0" ok
 destination "0x318(%rax)" (0x00000318) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: unity-window-decorator crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to natty on 2011-03-01 (32 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 #727041, 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.