the plugin does not work in chromium-browser (7.0.536.2 (60818) Ubuntu 10.10 from ppa))

Bug #652959 reported by andrey i. mavlyanov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gecko-mediaplayer (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Binary package hint: gecko-mediaplayer

the gecko-mediaplayer plugin in maverick just not loading in chromium (firefox 3.6.x work just excellent!)

aim@aim-laptop:~$ apt-cache policy gecko-mediaplayer
gecko-mediaplayer:
  Installed: 0.9.9.2-1
  Candidate: 0.9.9.2-1
  Version table:
 *** 0.9.9.2-1 0
        500 http://archive.ubuntu.com/ubuntu/ maverick/multiverse amd64 Packages
        100 /var/lib/dpkg/status
aim@aim-laptop:~$ apt-cache policy chromium-browser
chromium-browser:
  Installed: 7.0.536.2~r60818-0ubuntu1~ucd~dev1
  Candidate: 7.0.536.2~r60818-0ubuntu1~ucd~dev1
  Version table:
 *** 7.0.536.2~r60818-0ubuntu1~ucd~dev1 0
        500 http://ppa.launchpad.net/chromium-daily/dev/ubuntu/ maverick/main amd64 Packages
        100 /var/lib/dpkg/status
     6.0.472.63~r59945-0ubuntu2 0
        500 http://archive.ubuntu.com/ubuntu/ maverick/universe amd64 Packages

please, let me know if you need any additional information

Revision history for this message
Kevin DeKorte (kdekorte-gmail) wrote :

Known chrome bug, due to problems in the chrome main loop, gecko-mediaplayer has been specifically disabled by the chrome team.

Revision history for this message
andrey i. mavlyanov (andrey-mavlyanov) wrote :

So, should I fill a bug report on gecko-mediaplayer then?

Revision history for this message
Julien Lavergne (gilir) wrote :

It was reported on chromium bug tracker : http://code.google.com/p/chromium/issues/detail?id=24507
The plugin is currently blacklisted because it crashes. A solution proposed is to disable gconf support in gecko-mediaplayer, which seems to fix the problem.

Changed in gecko-mediaplayer (Ubuntu):
status: New → Confirmed
importance: Undecided → High
Revision history for this message
andrey i. mavlyanov (andrey-mavlyanov) wrote :

Yes it was. But I've just renamed gecko*so into smth*so and works just fine (and many users of chrome reported that it works ok with new chrome/chromium). May be it's time to whitelist gecko-mplayer back? At least in Ubuntu's builds?

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.