Re: is mplayerplugin dead.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[email protected] wrote:
> 
>1 is this has been a persistant problem for a long long time. I you
>look on google and to to different sites distros you will see them all
>saying the same thing. Manytimes in other languages.

Can't be that long firefox 2.0.0.3 has not been out for more than 4
months. And like I said, if people don't open a bug report the problem
doesn't exist.

>2 Maybe there is a special way it's compiled for Fedora. Since I don't
>have fedora the best I could do is ask what spacific compiling options
>are given or maybe they have some special patch they are using. But I
>can give you what compiling options I have used if that will also help.

I only test with Fedora, as I only have one machine that I work on for
this and that is the distro I choose to work with. If there is a
reproducable problem over and over, then I have tried to get that distro
working with VMWare, but even then most of the time it is something else.

>3 is if there is anyway you would like me to try and trace the problem
>down let me know and I will do it for you. I'm not a programmer but if
>you give me some simple instructions I can follow them and report back.

Run firefox from a terminal and give me the output with a test case that
you can reproduce 100% of the time. Test with mplayer running x11 mode
and preferably compile mplayer without the -gui option and have all
other plugins and extensions disabled (this causes several crashes)
About:plugins will tell you what you have loaded. VLC and totem and xine
and mozplugger and plugger ALL need to go and should not be listed on
the about:plugins location.


> (firefox-bin:16837): GLib-WARNING **: g_main_context_prepare(): main
> loop already active in another thread
> 
> GLib-ERROR **: file gmain.c: line 2008 (g_main_dispatch): assertion
> failed: (source)
> aborting...
> /usr/lib/firefox/run-mozilla.sh: line 131: 16837 Aborted                
> "$prog" ${1+"$@"}
> 
> 
> Let me know. Like I said if fedora has some special fix and you can let
> me know I could post it out to all the others that are waiting for a
> answer.

I'm pretty sure that this is a Firefox bug or a plugin conflict. I find
it hard to believe that the plugin is at fault since a we don't call any
g_main_* functions in the plugin and we only queue things to the g_main
loop by using g_idle_add.

Ok, as I test I downloaded firefox 2.0.0.5 from the mozilla.com site, I
extracted it in my home directory and then I compiled mplayerplug-in
(gtk2 mode) and installed it just into the firefox instance
~/firefox/plugins (I copied the xpt and so files here)...

I started it like this

cd ~
cd firefox
./firefox http://www.quicktime.com

And then clicked on the Darjeeling links to get here

http://www.apple.com/trailers/fox_searchlight/thedarjeelinglimited/hd/

And then I opened the 480p link

Seems to work totally fine.

If you want to send me some info from this run and the output of the
about:plugins location, don't cut anything out, most of the time it is
quite easy to read the output and see where it fails. You may also want
to set debug=1 in the mplayerplug-in.conf file.

The errors you are seeing are not from the plugin, they are from
firefox. When the plugin errors usually it will show where in the plugin
it crashed especially if you don't strip the binaries.

Kevin
- --
Get my public GnuPG key from
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7D0BD5D1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Remi - http://enigmail.mozdev.org

iD8DBQFGp9en6w2kMH0L1dERArKUAJ4poWrQaOOILxOcu14uHmw+OMYJXQCcCF85
OgX0+YeC9ubXprVWAeIJ4NY=
=WWhN
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/