You are not logged in.
This one of the most strange problem I have ever encountered. I have installed beid from the AUR. This is a tool providing an extension for Firefox for the use of the Belgium identity card (we can identify with it on some official Belgian website with the use of a USB tool that read the card, a smart card reader). But when I installed it, the flash plugin no longer works in chromium and I have the following error:
[19:19:0207/232532:ERROR:webplugin_delegate_proxy.cc(407)] PluginMsg_Init returned false
[19:19:0207/232532:ERROR:webplugin_impl.cc(269)] Couldn't initialize plug-inAfter some experiment I have seen that the culprit is the library: /usr/lib/libbeiddialogs.so. Remove it and the problem is solved (exept taht I can no longer use beid of course).
Probably most of you outside Belgium do not even have heard of that library. But this is precisiley what puzzled me. How can such specific library destinated to such specific tool crash Flash in Chromium? It may be related to SSL but I am lost. Note that no problem arise in Firefox at all. The beid package insytall a firefox extension in /usr/share/mozilla/extensions/ the problem persists when I delete it. How /usr/lib/libbeiddialogs.so can have any influence on Chromium+Flash is mysterious.
Last edited by olive (2013-02-08 08:04:34)
Offline
Chrome must be looking at the extensions in /usr/share/mozilla/extensions for some reason. Perhaps some extensions will work in chrome. What happens if you take the beld extension and move it to ~/.mozilla/firefox/random named directory.default/extensions/ ?
I trust Microsoft about as far as I can comfortably spit a dead rat.
Cinnamon is a wonderful desktop
"Faith is the substance of things hoped for, the evidence of things not seen."
Offline
Chrome must be looking at the extensions in /usr/share/mozilla/extensions for some reason. Perhaps some extensions will work in chrome. What happens if you take the beld extension and move it to ~/.mozilla/firefox/random named directory.default/extensions/ ?
After some tests, this is actually the other way around. Chromium works fine if I remove ~/.mozilla. Apparently the flash plugin look for somethin in ~/.mozilla and crashes (note that it does not crash in firefox). That begin to make sense at least since I have used the extension in firefox. The problem is now how can I prevent the flashplugin from reading ~/.mozilla when used in chromium?
Last edited by olive (2013-02-07 23:36:40)
Offline
Try installing the Pepper API flashplugin for Chromium. You can find it in the AUR.
I laugh, yet the joke is on me
Offline
Try installing the Pepper API flashplugin for Chromium. You can find it in the AUR.
Yes that does work. I have installed the PEPPER flash plugin and disabled the common flash plugin in chromium (I have to keep it since I use Firefox too). I put this thread as solved although the reason why does flash need to read ~/.mozilla (especially when not used in some mozilla products) remain obscure. The command
[xxxxxx@pcolivier ~]$ strings /usr/lib/mozilla/plugins/libflashplayer.so | grep .mozilla
/.mozilla/firefox/
/.mozilla/firefox/profiles.iniReveal that this flash indeed does something with ~/.mozilla
Last edited by olive (2013-02-08 08:05:47)
Offline