Why chrome doesn't see plugins installed into /usr/local/lib/browser_plugins?

Mark Atkinson atkin901 at gmail.com
Fri Nov 30 14:39:07 UTC 2012


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

On 11/16/2012 16:57, Yuri wrote:
> On my system chrome has different set of plugins than firefox.
> Firefox has many more. It looks like chrome only picks them from 
> ~/.mozilla/plugins, while firefox also looks for them in 
> /usr/local/lib/browser_plugins. Some plugins only get installed
> into the latter directory, for ex. www/plugger installs
> /usr/local/lib/browser_plugins/plugger/npplugger.so and it doesn't
> appear in chrome at all unless one makes a symbolic link in
> ~/.mozilla/plugins.
> 
> So why chrome isn't looking in /usr/local/lib/browser_plugins?
> 
> Yuri


It may be looking there, but you really can't tell unless you run
chrome from a terminal with:

chrome --debug-plugin-loading

and analyze the output.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlC4xPEACgkQrDN5kXnx8ybdlACgjf+I561c4lQCpYFcSreiG6Mf
WV8Amwdm3R7bxmM/uCUDOKSdKpG8WJpC
=rSi2
-----END PGP SIGNATURE-----



More information about the freebsd-chromium mailing list