miro.real crashed with SIGSEGV in pthread_mutex_lock()

Bug #347589 reported by firebird76
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
miro (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: miro

Description: Ubuntu jaunty (development branch)
Release: 9.04

miro:
  Installiert: 2.0.3-1ubuntu1
  Kandidat: 2.0.3-1ubuntu1
  Versions-Tabelle:
 *** 2.0.3-1ubuntu1 0
        500 http://archive.ubuntu.com jaunty/universe Packages
        100 /var/lib/dpkg/status
     2.0.3-0pcf1 0
        500 http://ftp.osuosl.org intrepid/ Packages
     2.0.2-0pcf1 0
        500 http://ftp.osuosl.org intrepid/ Packages
     2.0.1-0pcf1 0
        500 http://ftp.osuosl.org intrepid/ Packages
     2.0-0pcf1 0
        500 http://ftp.osuosl.org intrepid/ Packages
     1.2.8-0pcf1 0
        500 http://ftp.osuosl.org intrepid/ Packages

crashed on start.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/miro.real
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: miro 2.0.3-1ubuntu1
ProcCmdline: /usr/bin/python /usr/bin/miro.real
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: miro
StacktraceTop:
 pthread_mutex_lock () from /lib/libpthread.so.0
 PR_Lock (lock=0x0) at ptsynch.c:206
 ?? () from /usr/lib/xulrunner-1.9.1b3/libxul.so
 ?? () from /usr/lib/xulrunner-1.9.1b3/libxul.so
 ?? () from /usr/lib/xulrunner-1.9.1b3/libxul.so
Title: miro.real crashed with SIGSEGV in pthread_mutex_lock()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax fuse libvirtd lpadmin mythtv netdev plugdev sambashare scanner vboxusers video

Revision history for this message
firebird76 (firebird76) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:pthread_mutex_lock () from /lib/libpthread.so.0
PR_Lock (lock=0x0) at ptsynch.c:206
XPCJSRuntime (this=0x87d4d70,
XPCJSRuntime::newXPCJSRuntime (aXPConnect=0x87d4c80)
nsXPConnect (this=0x87d4c80) at nsXPConnect.cpp:92

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in miro:
importance: Undecided → Medium
Iain Lane (laney)
visibility: private → public
Revision history for this message
mafix (mafix) wrote :

i have the same error on my computer..

jaunty amd64, with nvidia - probably it is a nvidia problem?
or could there be something wrong in the alternativ settings?

miro doesn't start up.

also tried the packages directly from getmiro.com.

Changed in miro (Ubuntu):
status: New → Confirmed
Bryce Harrington (bryce)
Changed in miro (Ubuntu):
importance: Medium → Undecided
Revision history for this message
Bryce Harrington (bryce) wrote :

I'm going through old miro bug reports and found this one against an earlier version of miro in an previous Ubuntu release. Since miro is a universe component, our focus is primarily on the current development version (currently Lucid).

There haven't been many miro bugs reported recently, so my hope is that whatever caused your crash has since been fixed. But if this is incorrect and you are still seeing it with the newest miro, can you also include your log files from after reproducing the crash? These are located at:

~/.miro/miro-log
~/.miro/miro-downloader-log

Also please list the steps to reproduce the problem, or if crashes randomly what frequency it happens.

Changed in miro (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

We're closing this bug since it is has been some time with no response. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in miro (Ubuntu):
status: Incomplete → Invalid
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.