compiz crashed with SIGSEGV in g_type_check_instance()

[etab3ta]

After the last upgrade I have this crash and at the same time the unity launcher, when in "autohide", is allways hidden, also if I go with the cursor in the left edge(the Launcher Reveal Pressure" value is "1"). If the "Hide launcher" is on the "Never" , the launcher is visible and work right.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-core 1:0.9.7.0+bzr3035-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Tue Mar 13 08:28:28 2012
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120112)
ProcCmdline: compiz
ProcEnviron:
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb70874d1 <g_type_check_instance+33>: mov (%eax),%edx
 PC (0xb70874d1) ok
 source "(%eax)" (0x00001dc2) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 g_type_check_instance () 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
 g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libbamf3.so.0
 bamf_marshal_VOID__STRING_STRING () from /usr/lib/i386-linux-gnu/libbamf3.so.0
Title: compiz crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: Upgraded to precise on 2012-02-13 (28 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #930575, 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.