compiz crashed with SIGSEGV in g_datalist_id_set_data_full()

[OpenSage]

compiz crashed with SIGSEGV in g_datalist_id_set_data_full() It crashed when i was changing key bindings and there was a conflict i was trying to ignore the initiate for the (super + m) key binding. I wanted it for the magnifier, but it was already being used by Full Screen Negative and by Unity for the Dash Music search.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libnux-2.0-0 2.0.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Thu Feb 2 21:25:03 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f3808e9ac85 <g_datalist_id_set_data_full+341>: mov 0x0(%r13),%esi
 PC (0x7f3808e9ac85) ok
 source "0x0(%r13)" (0xaaaaaaaaaaaaaaa8) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 g_datalist_id_set_data_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 unity::PanelTray::~PanelTray() () from /usr/lib/compiz/libunityshell.so
 unity::PanelTray::~PanelTray() () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in g_datalist_id_set_data_full()
UpgradeStatus: Upgraded to precise on 2012-02-03 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[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 #916228, 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.