Ubuntu
xine-lib package

totem-xine crashes on Quicktime play

Bug #91459 reported by kaotiks@gmail.com on 2007-03-11

Affects		Status	Importance	Assigned to	Milestone
	xine-lib (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: totem-xine

While launching the movie at http://talkingasshole.cf.huffingtonpost.com/talkingasshole.mov, the totem-xine player crashed with no apparent cause, all proper codecs are installed and all settings are optimal for playback.

Revision history for this message

kaotiks@gmail.com (kaotiks) wrote on 2007-03-11:

Crash Report Edit (2.7 MiB, text/plain)

Crash Report

Revision history for this message

Reinhard Tartler (siretart) wrote on 2008-05-19:

Thanks for taking your time to report this bug. You have reported a crash in the xine-lib library. In order to be able to actually fix this bug, we must be able to

  * reproduce it
  * check if it happens with the latest version
  * understand where it actually crashes

You can help with the first point by attaching an example file to this bug report. Please note that a proper attachment is preferred over a link to some remote site. Remote side that are password protected or otherwise restriced (like services like rapidshare.com and similar) are absolutely not acceptable.

For the 2nd point, the MOTUMedia team provide updated packages for xine-lib and ffmpeg in their PPA for past ubuntu releases. See http://launchpad.net/~motumedia/+archive for instructions how to enable that archive. Please add this repository to your /etc/apt/sources.list, update your system and make sure, that you have both packages 'ffmpeg-dbg' and 'libxine1-dbg' installed (use 'sudo apt-get dist-upgrade && sudo apt-get install libxine1-dbg ffmpeg-dbg'). This way, you can produce meaningful backtraces that help us with point 3. You can read https://wiki.ubuntu.com/Backtrace about how to create proper backtraces that help developers identifying the exact location of the crash.

Thank you for your cooperation.

Changed in xine-lib:
status:	New → Incomplete

Revision history for this message

Connor Imes (ckimes) wrote on 2008-08-05:

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!