xine_extractor crashed with SIGSEGV

Bug #268645 reported by ubuntu.diego
10
Affects Status Importance Assigned to Milestone
miro (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: miro

No idea what happened

ProblemType: Crash
Architecture: amd64
Date: Wed Sep 10 12:54:08 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/miro/xine_extractor
NonfreeKernelModules: nvidia
Package: miro 1.1.2-0ubuntu2
PackageArchitecture: amd64
ProcCmdline: /usr/share/miro/resources/../../../lib/miro/xine_extractor /home/username/Downloads/Miro/Mahalo-Daily/Mahalodaily-PeterThielFiresideChatWithMichaelArringtonAtTechCrunch50212.mov /home/username/.miro/icon-cache/extracted/Mahalodaily-PeterThielFiresideChatWithMichaelArringtonAtTechCrunch50212.mov.lgsmB.png
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: miro
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? () from /usr/lib/libxine.so.1
Title: xine_extractor crashed with SIGSEGV
Uname: Linux 2.6.24-19-rt x86_64
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev pulse pulse-access pulse-rt scanner video

Tags: apport-crash
Revision history for this message
ubuntu.diego (ubuntu-diego) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:build_frame_table (trak=0xd3b8d0, global_timescale=30000) at demux_qt.c:1718
parse_moov_atom (info=0xc7cb80, moov_atom=0x7f0cfc3f3010 "", bandwidth=1544000)
open_qt_file (info=0xc7cb80, input=0xc74b50, bandwidth=1544000) at demux_qt.c:2243
open_plugin (class_gen=0xc7c650, stream=0xc2e6f0, input_gen=0xc74b50) at demux_qt.c:3020
probe_demux (stream=0xc2e6f0, method1=<value optimized out>,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in miro:
importance: Undecided → Medium
Iain Lane (laney)
visibility: private → public
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: New → Incomplete
Bryce Harrington (bryce)
Changed in miro (Ubuntu):
status: Incomplete → New
status: New → 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.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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