totem-gstreamer/xine integration with firefox

Bug #21131 reported by Dave Morley
12
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Invalid
Medium
Sebastien Bacher

Bug Description

My wife was trying to watch a live feed from www.qvcuk.com (watch qvc live tab)
totem-gstreamer promptly reported:
Totem could not play 'fd://0'.
there were no decoders found to handle the stream, you might need to install the
corresponding plugins.
I then installed Totem-xine which solved this problem. How ever I can no longer
watch any movie trailers as totem crashes out and takes firefox with it, some of
the trailers are mpeg files which both gstreamer and xine support. Yet if I
download the film trailer first it will play in totem-gstreamer or xine without
a hitch. I have also open totem and typed in the url and it will play the files.

I am therefore assuming there is a problem with it's integration with firefox
rather than a problem specifically with totem.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. It does the same message here with the gstreamer version,
but the xine version reads it fine. What version of totem do you use (the
"about" dialog has it)?
Could you get a backtrace of the crash with gdb:
- gdb -p `pidof firefox-bin`
(gdb) continue
... go to the page and get the crash
(gdb) thread apply all bt

How do you download the file to try on your box?

Revision history for this message
Sebastien Bacher (seb128) wrote :

does it crash while reading the file or when changing the page?

Revision history for this message
Dave Morley (davmor2) wrote :

Sorry I am a newish linux user and this is my first bug report. I am running
breezy badger, Totem-gstreamer is 1.2.0 and gstreamer is 0.8.11. To download
an mpeg file for test I used
http://dc5video.debian.net/mpeg/2005-07-14/02-Ubuntu_Talk-Mark_Shuttleworth.mpeg.
 I copy and paste the link into Totems 'Movie/open location box' and I have also
simply right clicked the file and 'save link as' either of these methods and the
file works in totem as a normal player. How ever if I left click on the file to
watch it in the browser it crashes totem and firefox. With totem-xine running
rather than totem-gstreamer the play window appears but the file doesn't play,
but again if I download the file it works as above.

The player sometimes crashes imediately (mainly totem-gstreamer) or will open up
the player window and nothing happens (mainly totem-xine). If you then click on
the back icon in firefox the whole lot crashes this happens with both
totem-gstreamer or totem-xine. The whole lot crashes also if you close the
player window.

I will try and get the crash backtrace you requested but it might take a while
as I already pointed out I am still a relative new comer to linux.

Revision history for this message
Dave Morley (davmor2) wrote :

this is the result from my gdb log

Loaded symbols for /usr/lib/mozilla-firefox/plugins/libtotem_mozilla.so
Reading symbols from /usr/lib/libdbus-glib-1.so.1...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libdbus-glib-1.so.1
Reading symbols from /usr/lib/libdbus-1.so.1...
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libdbus-1.so.1
Reading symbols from /usr/lib/libgstgconf-0.8.so.0...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libgstgconf-0.8.so.0
Reading symbols from /usr/lib/libgstinterfaces-0.8.so.0...
(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgstinterfaces-0.8.so.0
Reading symbols from /usr/lib/libgstreamer-0.8.so.1...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libgstreamer-0.8.so.1

Hope it helps. This was trying to watch the afformentioned
http://dc5video.debian.net/mpeg/2005-07-14/02-Ubuntu_Talk-Mark_Shuttleworth.mpeg.
 If you need more of the log I can do it again and send the whole thing now I
know what I'm doing.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your comments. The backtrace is not the useful part, it just list the
libs used. Could you get the part after typing "thread apply all bt" on the
(gdb) line when it crashes?

Revision history for this message
Dave Morley (davmor2) wrote :

these are the threads:

Thread 8 (Thread 1082132832 (LWP 12849)):
#0 0x00002aaaad4ec5d2 in poll () from /lib/libc.so.6
#1 0x00002aaaab1744cf in PR_Poll () from /usr/lib/mozilla-firefox/libnspr4.so
#2 0x00002aaaaf1ae496 in NSGetModule ()
   from /usr/lib/mozilla-firefox/components/libnecko.so
#3 0x00002aaaaadecd4c in nsThread::Main ()
   from /usr/lib/mozilla-firefox/libxpcom.so
#4 0x00002aaaab175a64 in PR_Select ()
   from /usr/lib/mozilla-firefox/libnspr4.so
#5 0x00002aaaab29d0fa in start_thread () from /lib/libpthread.so.0
#6 0x00002aaaad4f5383 in clone () from /lib/libc.so.6

After threat 6 it's a load of 0000000000000000 (). Hope it's of use.

Revision history for this message
Dave Morley (davmor2) wrote :

also found these further down the line:
#215 0x00002aaaad65f0e0 in __check_rhosts_file () from /lib/libc.so.6
#241 0x00002aaaab3a7660 in stack_cache_maxsize () from /lib/libpthread.so.0
#345 0x00001afacf698d9a in ?? ()
#350 0x00002aaaab1759d0 in PR_Select ()
   from /usr/lib/mozilla-firefox/libnspr4.so
sorry about that i didn't think it might change after #150

Revision history for this message
Tollef Fog Heen (tfheen) wrote :

I can't reproduce the crash on i386 or amd64.

The gstreamer issue is asily reproduced on both.

Revision history for this message
Dave Morley (davmor2) wrote :

Is there a way I can post you a screen shot just to show what I get when I try
to play the mpeg.

Revision history for this message
David Farning (dfarning) wrote :

Adding a screen shot is a great idea when you can't explain a bug. I like to
install kSnapShot which can be found via apt or synaptic. Then you can include
the image via 'Create a New Attachment.'

Revision history for this message
Dave Morley (davmor2) wrote :

Created an attachment (id=4742)
This is all I get. If I press back it kills firefox.

This image demonstrates the problem I get on my 64bit machine but also on my
Wife's x86 ibm thinkpad R50e

Revision history for this message
Dave Morley (davmor2) wrote :

Created an attachment (id=4743)
same thing only using totem-gstreamer rather than totem-xine

This is the bug with totem-gstreamer rather than totem-xine as in the previous
entry. This mpeg file however will play either in totem-xine or
totem-gstreamer if you simply type in the url into (totem movie/open location)
box. It only crashes out when in firefox.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Could those who has the problem, attach the output of 'cat /proc/cpuinfo' to
the bug?

Revision history for this message
Daniel Holbach (dholbach) wrote :

And try to change the videosink in gstreamer-properties?

Revision history for this message
Dave Morley (davmor2) wrote :

change videosink in gstreamer-properties? I have no idea how to do that. and my
'cat /proc/cpuinfo' doesn't change at all. Below is a before and after.

processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 12
model name : AMD Athlon(tm) 64 Processor 3400+
stepping : 0
cpu MHz : 2411.759
cache size : 512 KB
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow
bogomips : 4767.74
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp

Revision history for this message
Daniel Holbach (dholbach) wrote :

run 'gstreamer-properties' (without the quotes) in a terminal and change the
video preferences and see if they make a difference.

Revision history for this message
Dave Morley (davmor2) wrote :

I have taken great care to ensure I have tried every combination of
gstreamer-properties but with no effect.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Same issue than #14882

This bug has been marked as a duplicate of bug 21110.

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.