compiz crashed with SIGSEGV in pthread_mutex_lock()

Bug #729504 reported by meghsinghnokha
48
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Unity
Triaged
Medium
Loïc Molinari
compiz (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: compiz

i have problem after install ubuntu 11.04

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 10:55:33 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202.1)
ProcCmdline: compiz --replace
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=en_US:en
SegvAnalysis:
 Segfault happened at: 0xb76ce33d <pthread_mutex_lock+29>: mov 0xc(%esi),%edi
 PC (0xb76ce33d) ok
 source "0xc(%esi)" (0x00000011) 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/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
meghsinghnokha (meghsinghnokha) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __pthread_mutex_lock (mutex=0x5) at pthread_mutex_lock.c:50
 g_source_unref_internal (source=0x99057a8, context=0x1, have_lock=0) at /build/buildd/glib2.0-2.28.1/./glib/gmain.c:1671
 Glib::Source::unreference (this=0x95a6d10) at main.cc:765
 ~RefPtr (this=0x954b540, __in_chrg=<value optimized out>) at /usr/include/glibmm-2.4/glibmm/refptr.h:207
 PrivateScreen::~PrivateScreen (this=0x954b540, __in_chrg=<value optimized out>) at /build/buildd/compiz-0.9.4/src/screen.cpp:4781

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in compiz (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
tags: added: compiz-0.9
visibility: private → public
Revision history for this message
bp (badpazzword) wrote :

I experienced the same problem signature in Natty after I installed Steam through PlayOnLinux (after logging in). I'm using the experimental FOSS 3D nVidia drivers, if that matters.

Yeah, I know... that's quite the stack of "bleeding edge/unstable" software.

Revision history for this message
Jack Leigh (leighman) wrote :

I have also experienced this caused by programs running in wine

Revision history for this message
sdaau (sd-imi) wrote :

As a note, I have submitted
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/748460
... a duplicate of this bug; my problem is in opening PDFs in evince by doubliclicking or right-clicking a PDF (that bug contains a description of my problem)

Now that unity has been under --replace, I left the PC for a while (meaning screensaver kicked in), and now, again it seems I got the freezing on double-clicking a PDF file -- but at this point, I could see the following being spit out in terminal right after the right-click failure:

----
$ ** (<unknown>:2167): DEBUG: MaximizeIfBigEnough: Evince window size doesn't fit

** (<unknown>:2167): WARNING **: Failed to fetch xid: Method "GetXid" with signature "" on interface "org.ayatana.bamf.window" doesn't exist
----

... Maybe in my case, it is ultimately a bug with Evince?

tags: added: bugpattern-needed
David Barth (dbarth)
Changed in unity:
milestone: none → 3.8
milestone: 3.8 → 3.8.4
assignee: nobody → Loïc Molinari (loic.molinari)
status: New → Triaged
importance: Undecided → Medium
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.