On Sat, 31 Jan 2015 01:53, Carlos E. R. wrote:
On 2015-01-30 21:23, Yamaban wrote:
On Fri, 30 Jan 2015 13:52, Carlos E. R. wrote:
Delete the file pluginreg.dat in your FF profile dir, it will be recreated by FF at the next restart of FF, with fresh information.
This is a case that should not happen, but is sometimes does anyway.
Thanks. You missed the post from I. Petrov, instructing me to edit that file. Changing the timestamp of the flash plugin in the file forced FF to re-evaluate it.
I did, and FF is working fine now :-)
Isn't deleting the entire file too drastic, or is it recreated fully without destroying something important? Side effects?
I'm following the work Mozilla Devs for more than a decade now, and I try to give nondestructive advise only, so without grepping the relevant bugzilla entries it's a bit long to explain what exactly FF does at startup. The long and the short is: there are some files in the profile that only exist to speedup the start of FF. And "pluginreg.dat" is one of them. What happens if this file is found, is that FF uses this information WITHOUT verfying, to display the state of the plugins. If this file is not found, FF starts plugin-container for each plugin, just to extract the version info for every plugin FF finds. On a fast multi-core machine with enough RAM and a SSD, you will have trouble to measure the time, but think a netbook, 1Ghz single core, 1.5GB RAM, and a slow 60GB HDD (rotating rust), and you measure that in ca. 0.3 sec per plugin minimum. That is why this file can be removed without harm. For further info the MozillaZine Knowlegdebase is a good startpoint. http://kb.mozillazine.org/Flash - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org