compiz crashed during TwinView-setup using nvidia-settings with SIGSEGV in g_datalist_id_set_data_full()

[Thomas Reuss]

Setting up twinview (two external monitors) using nvidia-settings doesn't work.
nvidia-settings will freeze and cause compiz to crash.

Original Summary:
compiz crashed with SIGSEGV in g_datalist_id_set_data_full()

My system:
DELL Latitude E6420
Graphics card: nVidia Corporation GF119 [Quadro NVS 4200M] (rev a1)

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libnux-2.0-0 2.0.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
Uname: Linux 3.2.0-10-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Jan 23 09:06:22 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120121)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x7f4a9efacb55 <g_datalist_id_set_data_full+341>: mov 0x0(%r13),%esi
 PC (0x7f4a9efacb55) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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