Ubuntu
ffmpeg-debian package

totem-mozilla-viewer crashes on choosing "About"

Bug #78624 reported by RafG on 2007-01-09

Affects		Status	Importance	Assigned to	Milestone
	ffmpeg-debian (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

Binary package hint: totem-xine

Steps to reproduce:
1. Watch the QuickTime movie on http://www.apple.com/iphone/ipod/ with Firefox and the Totem plugin.
2. While it's playing, right-click the movie and choose 'About'.
3. The Totem plugin crashes (its place on the page is replaced by a white rectangle).

Revision history for this message

John Vivirito (gnomefreak) wrote on 2007-01-09:

Thanks for your bug report. Could you please try to obtain a
backtrace by following the instructions on
http://wiki.ubuntu.com/DebuggingProgramCrash.
This will greatly aid us in tracking down your problem.

Changed in totem:
status:	Unconfirmed → Needs Info

Revision history for this message

RafG (raf-g) wrote on 2007-01-09:

Crash report Edit (5.5 MiB, text/plain)

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-01-10:

The crash is due to xine-lib, from apport and gdb:

"Core was generated by `/usr/lib/totem/totem-mozilla-viewer --xid 42025261 --width 512 --height 512 --u'.
Program terminated with signal 11, Segmentation fault.
#0 0xb60bc342 in ff_h264_idct_add_mmx2 () from /usr/lib/xine/plugins/1.1.2/xineplug_decode_ff.so
...
"

Reassigning

Changed in totem:
status:	Needs Info → Unconfirmed

Sebastien Bacher (seb128) on 2007-03-22

Changed in xine-lib:
importance:	Undecided → Medium
status:	Unconfirmed → Confirmed

Revision history for this message

Reinhard Tartler (siretart) wrote on 2008-07-08:

crash in the ffmpeg plugin, reassigning again.

Revision history for this message

Reinhard Tartler (siretart) wrote on 2008-09-14:

does this still happen in intrepid?

you can also test the backported packages from https://launchpad.net/~motumedia/+archive if you didn't upgrade to intrepid yet.

Changed in ffmpeg:
status:	Confirmed → Incomplete

Revision history for this message

Javier Jardón (jjardon) wrote on 2008-12-22:

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!