compiz crashed with SIGSEGV in pthread_mutex_lock()

Bug #729506 reported by Pete Graner
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: compiz

Clicked on "restart compiz" after a crash (which I reported lp #729505) and I got the window borders for about 5 sec then it crashed again with a different error. This was in "Classic Desktop" mode.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-core 1:0.9.4-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic-pae 2.6.38-rc6
Uname: Linux 2.6.38-5-generic-pae i686
Architecture: i386
Date: Sat Mar 5 00:36:17 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
ProcCmdline: /usr/bin/compiz
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb76e033d <pthread_mutex_lock+29>: mov 0xc(%esi),%edi
 PC (0xb76e033d) ok
 source "0xc(%esi)" (0x23c3820f) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 pthread_mutex_lock () from /lib/libpthread.so.0
 ?? () from /lib/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: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Pete Graner (pgraner) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

visibility: private → public
tags: removed: need-i386-retrace
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.