mozilla-lists.mbou...@spamgourmet.com wrote:
Paul B. Gallagher wrote:
David H. Durgee wrote:
I'm seeing something a bit strange here. Looking at about:plugins in
SeaMonkey I see:
Shockwave Flash
File: libflashplayer.so
Path: /usr/lib/adobe-flashplugin/libflashplayer.so
Version: 11.2.202.438
State: Enabled (STATE_VULNERABLE_UPDATE_AVAILABLE)
Shockwave Flash 11.2 r202
Yet when I look in the package manager I see it shows as 11.2.202.440,
which is the current release per Adobe. If I look at the file noted in
the path above I see the 11.2.202.440 string in it too, so why is
SeaMonkey reporting an older, vulnerable version?
The time stamp on the file shows 2015/01/23 18:16, so it is possible
that SeaMonkey has not been restarted since before it was installed. Is
there a way I can get SeaMonkey to reload plugins/add-ins short of a
shutdown/restart?
AFAICT the most current version is 16.0.0.296. But I'm on Windows 7, not
Linux. Useful links here:
<https://support.mozilla.org/en-US/questions/1035859>
I thought that version looked rather old as well. But this page (from
Adobe) lists current versions for each OS and browser:
https://www.adobe.com/software/flash/about/
and indeed for Mozilla on Linux, the latest is 11.2.202.440.
There shouldn't be any need to restart the whole OS. At worst,
restarting SeaMonkey should be sufficient to reload any plugins. A
couple of things which may be worth trying:
- Close all pages using Flash; maybe the plugin would be unloaded and
then reloaded next time you open a page which needs it..
- Disable Flash from the Add-ons Manager, then re-enable it; again,
maybe that will force a reload.
I'm no expert on Linux, but I think most Linux filesystems allow a file
which is in use (e.g. the Flash plugin in use by SeaMonkey) to be
overwritten (e.g. by the Flash updater), while the application already
using it keeps its handle on the original file. So looking at the file
with any other tool will see the new version, while SeaMonkey is still
using the old version. What happens "under the hood" is basically that
the new version of the file is written to disk, and the path updated to
reference that. But applications already using the file keep their
handle on the older version, which is not actually deleted until all
handles on it have been closed. This is what allows updates to be
applied to a running Linux system, and then affected applications can be
restarted after applying the update, minimising downtime.
The alternative, as Windows does, is to not allow files which are in use
to be replaced at all. In that case, SeaMonkey has to be closed while
Flash is being updated.
Mark.
Well, I have tried several things and none of them have corrected the
problem. I tried enabling and disabling the plugin, I restarted
SeaMonkey, I even shut SeaMonkey down and reinstalled the plugin from
the Synaptic Package Manager while it was shut down. Nothing helped!
I still show the same situation. The about:plugins shows the same as
above and inspecting the file shows the current release. So why is
SeaMonkey still insisting that the old version is installed.
Interestingly, here is FireFox on the same system:
Shockwave Flash
File: libflashplayer.so
Path: /usr/lib/adobe-flashplugin/libflashplayer.so
Version: 11.2.202.440
State: Enabled
Shockwave Flash 11.2 r202
MIME Type Description Suffixes
application/x-shockwave-flash Shockwave Flash swf
application/futuresplash FutureSplash Player spl
So they point to the same file, but only FireFox gets it right?
Dave
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
