I’ve been following bug reports about the gecko mediaplayer causing crashing and freezing with Google Chrome and Chromium and recently discovered a work around.
If one starts these browsers from the terminal like this:
google-chrome --without-gconf
or
chromium --without-gconf
the problems with gecko seem to go away. This is the first time I’ve tried it so I’ll report back if this solution doesn’t hold up. The devs say this is an upstream bug in Chrome.
Hi
Also had another thought, when we started getting it up and running
(into the OBS contrib) I created a start script that did user-agent
switching by adding the following script; http://pastebin.com/5MXGg5W2
Or does google-chrome already have a switcher? This was because apple
changed their site to be non-browser/os friendly.
–
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 2.6.27.45-0.1-default
up 1 day 2:20, 3 users, load average: 0.62, 0.34, 0.34
GPU GeForce 8600 GTS Silent - CUDA Driver Version: 195.36.15
I’m using gecko-mediaplayer 0.9.9.2-1.1 and gnome mplayer 0.9.9.2-4.1 from OBS. I thought that maybe the versions from OBS would work better than the packman versions.
It turns out that the --without-gconf option isn’t helping. I just got lucky the first few times I tried it. I think maybe this option needs to be used when building the gecko-mediaplayer package.
Any packagers on this forum that want to give it a try?
hello, i just found this thread using google and i also have this problem. i switched from chrome (where the plugin was working fine) to chromium today and noticed that the plugin isn’t recognized by the browser. i’ve made sure that the .so files were in the right folders without any luck.
has anyone found a solution or should i file a bug report to the chromium team?
gecko-mediaplayer automatically fakes the User-Agent when needed (there is a hardcoded web list that includes Apple’s).
I’m the packager in the OBS. But I’m not going to disable the gconf support since the problem is with Chrome and yesterday Chrome devs decided to blacklist the plugin in a hardcoded way (I don’t use Chrome, but I suppose you can’t override that through config).