compiz crashed with SIGSEGV in pthread_mutex_lock()

[graingert]

Binary package hint: compiz

Compiz freezes on login - have to change to a different tty and kill compiz

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-core 1:0.9.4+bzr20110411-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 270.30 Fri Feb 25 14:34:55 PST 2011
 GCC version: gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu1)
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,imgjpeg,compiztoolbox,decor,gnomecompat,grid,imgpng,imgsvg,move,place,regex,resize,animation,text,titleinfo,mousepoll,thumbnail,session,wall,vpswitch,blur,dbus,wobbly,workarounds,expo,bicubic,ezoom,staticswitcher,fade,scale,unityshell,scaleaddon,scalefilter]
CompositorRunning: compiz
CrashCounter: 1
Date: Mon Apr 11 22:10:09 2011
DistUpgraded: Log time: 2011-01-30 01:07:31.621948
DistroCodename: natty
DistroVariant: ubuntu
DkmsStatus:
 nvidia-current, 270.30, 2.6.38-1-generic, x86_64: installed
 nvidia-current, 270.30, 2.6.38-7-generic, x86_64: installed
 nvidia-current, 270.30, 2.6.38-8-generic, x86_64: installed
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 nVidia Corporation G80 [GeForce 8800 GTS] [10de:0193] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: XFX Pine Group Inc. Device [1682:2251]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InstallationMedia_: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
JockeyStatus:
 firmware:dvb_usb - Firmware for DVB cards (Proprietary, Enabled, In use)
 xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-8-generic root=UUID=e9422aeb-1ee7-488b-b389-2903fef11563 ro quiet splash vt.handoff=7
ProcVersionSignature_: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Renderer: Unknown
SegvAnalysis:
 Segfault happened at: 0x7f0fa4cd1394 <pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
 PC (0x7f0fa4cd1394) ok
 source "0x10(%rdi)" (0x6fffffffd) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 pthread_mutex_lock () from /lib/x86_64-linux-gnu/libpthread.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 PrivateScreen::~PrivateScreen() ()
 PrivateScreen::~PrivateScreen() ()
 CompScreen::~CompScreen() ()
Title: compiz crashed with SIGSEGV in pthread_mutex_lock()
UpgradeStatus: Upgraded to natty on 2011-03-27 (15 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
version.compiz: compiz 1:0.9.4+bzr20110411-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu12
version.libdrm2: libdrm2 2.4.23-1ubuntu6
version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
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-4ubuntu6
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7

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