[Pkg-chromium-maint] Bug#590145: chromium-browser: Upstream ban on gecko-mediaplayer plugin must be removed

Jonathan Nieder jrnieder at gmail.com
Mon Jul 26 21:47:45 UTC 2010

forwarded 590145 http://crbug.com/24507

Hi Dimitar,

Dimitar Kavlakov wrote:

> The plugin "gecko-mediaplayer" was blacklisted in the upstream some
> time ago because of bug #24507, that is speciffic to several other
> Linux distributions. Debian was never amongst the distributions where
> this bug appeared

That means <http://crbug/24507>:

| Repro: install gecko-mediaplayer, visit digg.com.  Page hangs.
| Renderer thread asks for plugins:
| Browser asks plugin to intialize, and it hangs inside glib.
| This is yet another instance of "query plugins out of process"
| Plugins load in two stages: first we dlopen() them to query metadata,
| then later in response to a page request we actually instantiate them.
| The blacklist we had in place only happened at the latter point;
| gecko-mediaplayer causes us to hang in the first step.  So move the
| blacklist check earlier to succesfully blacklist it.

http://code.google.com/p/gecko-mediaplayer/issues/detail?id=64 says:

| As a bug on the Chrome bug tracker says, this is a bug in Chrome.  I believe the 
| underlying problem is that Chrome sometimes hangs if something starts a nested gtk 
| message loop, which gecko-mediaplayer appears to be doing via gconf in this call 
| stack:
| --without-gconf appears to fix it with the svn tip of gecko-mediaplayer.

>                                            i can assure that the
> plugin continues to work fine on Debian with all stable and
> development versions of Chromium

That’s good to hear.  To clarify: does digg.com work?  And just in
case you know: is gecko-mediaplayer for Debian built --without-gconf?


More information about the Pkg-chromium-maint mailing list