compiz crashed with SIGSEGV in pthread_mutex_lock()

[Basile]

compiz doesn't work

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-core 1:0.9.4-0ubuntu7
ProcVersionSignature: Ubuntu 2.6.38-7.37-generic-pae 2.6.38
Uname: Linux 2.6.38-7-generic-pae i686
Architecture: i386
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CrashCounter: 1
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: Off
 modes: 1280x800
 edid-base64: AP///////wBMo0JCAAAAAAAQAQOAHhN4Cof1lFdPjCcnUFQAAAABAQEBAQEBAQEBAQEBAQEB7hoAgFAgEDAMQDMAL74QAAAZAAAADwAAAAAAAAAAACOHAmQAAAAA/gBTQU1TVU5HCiAgICAgAAAA/gBMVE4xNDFXMS1MMDYKAGM=
DRM.card0.VGA.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1920x1200 1600x1200 1280x1024 1280x960 1024x768 800x600 800x600 640x480
 edid-base64: AP///////wBMLT4ENDJZTSITAQMONCB4Ku6Ro1RMmSYPUFQjCACpQIGAgUABAQEBAQEBAQEBKDyAoHCwI0AwIDYABkQhAAAaAAAA/QA4PB5REQAKICAgICAgAAAA/ABTeW5jTWFzdGVyCiAgAAAA/wBITEpTODAwNDQxCiAgACc=
Date: Tue Mar 22 23:44:50 2011
DistUpgraded: Log time: 2011-03-22 20:20:32.772128
DistroCodename: natty
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Device [1179:ff00]
   Subsystem: Toshiba America Info Systems Device [1179:ff00]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
InstallationMedia_: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
MachineType: TOSHIBA SATELLITE M100
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=ru_RU:en
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic-pae root=UUID=60daa7b6-c055-4c38-ad77-75f9263b94f7 ro quiet splash vt.handoff=7
ProcVersionSignature_: Ubuntu 2.6.38-7.37-generic-pae 2.6.38
Renderer: Unknown
SegvAnalysis:
 Segfault happened at: 0xb70f433d <pthread_mutex_lock+29>: mov 0xc(%esi),%edi
 PC (0xb70f433d) ok
 source "0xc(%esi)" (0x0000000f) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 pthread_mutex_lock () from /lib/i386-linux-gnu/libpthread.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 Glib::Source::unreference() const () from /usr/lib/libglibmm-2.4.so.1
 PrivateScreen::~PrivateScreen() ()
 PrivateScreen::~PrivateScreen() ()
Title: compiz crashed with SIGSEGV in pthread_mutex_lock()
UpgradeStatus: Upgraded to natty on 2011-03-22 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 01/02/2007
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V2.60
dmi.board.name: HAQAA
dmi.board.vendor: TOSHIBA
dmi.board.version: Null
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV2.60:bd01/02/2007:svnTOSHIBA:pnSATELLITEM100:pvrPSMA0E-0SL01CRU:rvnTOSHIBA:rnHAQAA:rvrNull:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: SATELLITE M100
dmi.product.version: PSMA0E-0SL01CRU
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.4-0ubuntu7
version.libdrm2: libdrm2 2.4.23-1ubuntu5
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu11
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu6

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