Like the original reporter, deleting the pluginreg.dat works around the issue, but I had to do some searching to figure out the problem (and there's a lot of other confused users out there all the way back to the firefox 3 days.) (I'm using Fedora 25, with flash installed from Adobe's yum repository) Since Firefox just blocked a bunch of Flash 24 versions now that 25 is released, a bunch of Linux users including me are getting confusing messages where Firefox is reporting that the Flash plugin is out of date - even though we have upgraded flash and restarted Firefox. so which is already linked into the process? If I delete the file and restart Firefox then it is recreated with the correct version, but that should not be necessary every time I update the plugin.Ĭould there be a race condition when the plugin is updated, where Firefox uses the timestamp from the new file, but queries the version from the existing plugin. That suggests Firefox is not correctly updating the info in pluginreg.dat The timestamp in the file matches the mtime of the plugin ( 10:19:44) but the version is wrong. usr/lib64/flash-plugin/libflashplayer.so:$Ġ:application/x-shockwave-flash:Shockwave Flash:swf:$ 1 jwakely jwakely 1216 Apr 21 13:13 pluginreg.dat Source RPM : flash-plugin-11.2.įully Supported: Mozilla SeaMonkey 1.0+, Firefox 1.5+, Mozilla 1.7.13+ 1 root root 19294272 Apr 5 10:19 /usr/lib64/flash-plugin/libflashplayer.so $ ls -l /usr/lib64/flash-plugin/libflashplayer.so Firefox says I have 11.2.202.577 but that's wrong:
0 kommentar(er)
