I thought I had 1 plug in, but after loading codecs etc for viewing web-based videos, I notice that Firefox now has 9 plug-ins, including mplayer. I have no idea how this happened.
Actually there appears to be 3 mplayer plugins. One is 3.55, labelled mplayerplug-in 3.55, describing itself as a Video Player plug-in for QuickTime. The next is QuickTime Plug-in 7.45, also describing itself as mplayer 3.55 Video PLayer Plug-in for QuickTime. The last is labelled ‘Real Player 9’, also describing itself as Mplayer 3.55, a Video Player plug-in for QuickTime.
No, wait, now that I look closely, 6 of the 9 plug-ins are mplayer 3.55, but all with different titles or labels.
I found that vlc will open it. When you click the link and it says ‘open with’ go to /usr/bin and try kaffeine or vlc.
You need somthing that will handle i-player formats. There may be a plug-in/codec for mplayer.
Quite possibly - but that doesn’t really tell me why it crashes so quickly in Firefox, nor increase my understanding of how to experience these data in Firefox.
try running firefox from the command-line i.e. open a console & type firefox & press enter. when it crashes,it will have some form of answer as to why it crashed there.
More accurately, on testing Konqueror against a selection of 14 of the links, in every instance Konqueror invokes VLC which plays OK for about 90 seconds. At that point there is a break in the programme that was originally transmitted. About 10 seconds later the stated programme begins in the form of total gibberish - as if 2 of these tracks were being played together at double speed.
So neither Firefox nor Konqueror works on my system on this web-site
Not on my system it doesn’t. I am immediately returned to the command prompt after typing ‘firefox’ and hitting enter. An instance of firefox is invoked, displaying the home page. When I browse to the iPlayer Coverted site and click on a link all firefox windows close immediately, but there is no information in my terminal session.
I get exactly the same result (immediate close to FF) as the OP, when clicking a link on referenced website/page. Running from command-line gave this message:
/usr/bin/firefox: line 126: 5475 Segmentation fault $MOZ_PROGRAM "$@"
Not that this adds much to the thread, but I do recall hearing that the BBC’s i-player can be very Linux unfriendly (I might be mistaken on this though).
Have you tried playing audio on a different website?
XEyedBear adjusted his/her AFDB on Thursday 30 Jul 2009 20:36 to write:
>
> deltaflyer44;2019706 Wrote:
>> try running firefox from the command-line i.e. open a console & type
>> firefox & press enter. when it crashes,it will have some form of answer
>> as to why it crashed there.
>>
>> Andy
>
> Not on my system it doesn’t. I am immediately returned to the command
> prompt after typing ‘firefox’ and hitting enter. An instance of firefox
> is invoked, displaying the home page. When I browse to the iPlayer
> Coverted site and click on a link all firefox windows close immediately,
> but there is no information in my terminal session.
>
>
Get the same here with that converter site.
Firefox closes with a segfault in npviewer plugin.
Have you tried it in Windows, does that site work?
Why don`t you just use the BBC site and iplayer?
Works fine for me in ff.
HTH
–
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum
What!? Play audio from a different web-site??? Have you lost your sense of reason? You’ll be asking me to spell words without using the letter ‘u’ or ‘s’ next,
Looking at all the entries so far, it looks as if Firefox is not the problem; there is something else that is interfering with the reception of the signal. Is there a congestion issue on the line which would create something similar to the original symptoms?
brunomcl adjusted his/her AFDB on Saturday 01 Aug 2009 21:16 to write:
>
> Maybe you could try updating to FF3.5.1 from mozilla’s repo.
>
>
Already way ahead of you there.
Been on 3.5.1 since it came out, all codecs and everything as up to date as
possible.
It is something wrong with either ff or the player plugin, the site works OK
in konqueror with kmplayer plugin so could be realplayer, plugin or
browser???
–
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum
john hudson adjusted his/her AFDB on Saturday 01 Aug 2009 22:56 to write:
>
> Looking at all the entries so far, it looks as if Firefox is not the
> problem; there is something else that is interfering with the reception
> of the signal. Is there a congestion issue on the line which would
> create something similar to the original symptoms?
>
>
Well I just tried ff and it crashed but konqueror played OK.
And if they are both using the browser plugin dir ( which I presume they are
then it could be my default choice of pkayers in each browser here, will see
if I can narrow it down further in the morn.
–
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum
Err, you don’t seem to have been looking at my entry. Segmentation fault is a program/memory problem. I am puzzled as to how you arrive at a line/signal reception problem. It’s seems to me to be an an application level issue.