compiz crashed with SIGSEGV in pthread_mutex_lock()

Bug #734436 reported by Andreas Moog
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: compiz

Had to xkill an invisible window and got this crash soon after.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-core 1:0.9.4-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7
Uname: Linux 2.6.38-6-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sun Mar 13 19:32:52 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
ProcCmdline: compiz
ProcCwd: /home/andreas/Documents
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=en_US:en
SegvAnalysis:
 Segfault happened at: 0x7f352adf3374 <pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
 PC (0x7f352adf3374) ok
 source "0x10(%rdi)" (0x00000078) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 pthread_mutex_lock () from /lib/libpthread.so.0
 ?? () from /lib/libglib-2.0.so.0
 ~RefPtr (this=0x10ccab0, __in_chrg=<value optimized out>) at /usr/include/glibmm-2.4/glibmm/refptr.h:207
 PrivateScreen::~PrivateScreen (this=0x10ccab0, __in_chrg=<value optimized out>) at /build/buildd/compiz-0.9.4/src/screen.cpp:4781
 PrivateScreen::~PrivateScreen (this=0x10ccab0, __in_chrg=<value optimized out>) at /build/buildd/compiz-0.9.4/src/screen.cpp:4783
Title: compiz crashed with SIGSEGV in pthread_mutex_lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare

Revision history for this message
Andreas Moog (ampelbein) wrote :
tags: removed: need-amd64-retrace
Andreas Moog (ampelbein)
visibility: private → public
tags: added: compiz-0.9
Revision history for this message
sdaau (sd-imi) wrote :

Dunno if mine is the same - like on other bugs with Natty, for me the problem is that sometimes evince will not open when a PDF is double-clicked or right-click, and parts of the desktop freeze (stop responding to clicks) ... unity --replace & usually helps here, but then I get this (or other) crashes..

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.