Re: allowing flash player
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/futuresplashFutureSplash 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
Re: allowing flash player
David H. Durgee wrote: 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 TypeDescriptionSuffixes application/x-shockwave-flashShockwave Flashswf application/futuresplashFutureSplash Playerspl So they point to the same file, but only FireFox gets it right? Dave I decided to try something, I shut down SeaMonkey and edited the pluginreg.dat file in the SeaMonkey profile to match the FireFox one regarding flash. Now it reports the proper version number, so that appears to be the source of my problem. Now the question is why didn't SeaMonkey get the right version number when it was updated? Dave ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: allowing flash player
David H. Durgee wrote: I decided to try something, I shut down SeaMonkey and edited the pluginreg.dat file in the SeaMonkey profile to match the FireFox one regarding flash. Now it reports the proper version number, so that appears to be the source of my problem. Now the question is why didn't SeaMonkey get the right version number when it was updated? In my experience, the Flash updaters often fail to remove previous versions, so SeaMonkey will see two or more and have to choose. I don't know if it chooses well, but when I have a moment and I think of it, I usually go and delete the old files, which seems to do no harm. On my Win7 system, the path is: C:\Windows\SysWOW64\Macromed\Flash\ And the current files are: NPSWF32_16_0_0_296.dll FlashUtil32_16_0_0_296_Plugin.exe FlashPlayerPlugin_16_0_0_296.exe If you've also installed it for IE, you'll see the following as well: FlashUtil32_16_0_0_296_ActiveX.exe FlashUtil32_16_0_0_296_ActiveX.dll Flash32_16_0_0_296.ocx Of course, the version numbers will differ; that's how you can tell them apart. -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: allowing flash player
David H. Durgee wrote: Gerd Schweizer wrote: Paul B. Gallagher schrieb: You can test here, and if you pass, your installation is current and you can ignore the scams: Test Adobe Flash: https://www.adobe.com/software/flash/about/ Test Shockwave: https://www.adobe.com/shockwave/welcome/ Thank You, it's current 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? Adobe pulled the plug on the Linux version of Flash. They still patch that version for security bugs but that is it. Maybe Flash will finally die as industry moves towards HTML 5. -- Take care, Jonathan --- LITTLE WORKS STUDIO http://www.LittleWorksStudio.com ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: allowing flash player
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. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: allowing flash player
Gerd Schweizer wrote: Paul B. Gallagher schrieb: OK, then can you give us the URL of a page where a Flash video doesn't play, and also describe exactly what happens instead, including any error messages? Are there some pages where Flash videos do play, or do all fail? Are you using an ad blocker? not initiating by me? As i tried to get an url i could see another film there. May i send an url, when the problem happens again? You certainly have my permission to do what I asked you to do -- send a URL. -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: allowing flash player
Gerd Schweizer wrote: Paul B. Gallagher schrieb: You can test here, and if you pass, your installation is current and you can ignore the scams: Test Adobe Flash: https://www.adobe.com/software/flash/about/ Test Shockwave: https://www.adobe.com/shockwave/welcome/ Thank You, it's current 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? Dave ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: allowing flash player
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 -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: allowing flash player
Paul B. Gallagher schrieb: OK, then can you give us the URL of a page where a Flash video doesn't play, and also describe exactly what happens instead, including any error messages? Are there some pages where Flash videos do play, or do all fail? Are you using an ad blocker? not initiating by me? As i tried to get an url i could see another film there. May i send an url, when the problem happens again? -- Liebe Grüße, Gerd Satelliten FAQ, DVB-T, Katzen, Mopped, Garten, Heimwerken: http://www.satgerd.de/ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: allowing flash player
Paul B. Gallagher schrieb: You can test here, and if you pass, your installation is current and you can ignore the scams: Test Adobe Flash: https://www.adobe.com/software/flash/about/ Test Shockwave: https://www.adobe.com/shockwave/welcome/ Thank You, it's current -- Liebe Grüße, Gerd Satelliten FAQ, DVB-T, Katzen, Mopped, Garten, Heimwerken: http://www.satgerd.de/ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: allowing flash player
Gerd Schweizer wrote: Paul B. Gallagher schrieb: You can test here, and if you pass, your installation is current and you can ignore the scams: Test Adobe Flash: https://www.adobe.com/software/flash/about/ Test Shockwave: https://www.adobe.com/shockwave/welcome/ Thank You, it's current OK, then can you give us the URL of a page where a Flash video doesn't play, and also describe exactly what happens instead, including any error messages? Are there some pages where Flash videos do play, or do all fail? Are you using an ad blocker? -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: allowing flash player
A Williams schrieb: actual = means current. The German word is Aktuell. Thank You for that correction. -- Liebe Grüße, Gerd Satelliten FAQ, DVB-T, Katzen, Mopped, Garten, Heimwerken: http://www.satgerd.de/ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: allowing flash player
A Williams wrote: Gerd Schweizer wrote: Paul B. Gallagher schrieb: Gerd Schweizer wrote: In Germany the tv organizations offer cinemas in the internet till one week after sending. But they need the flash player. How can i tell seamonkey to allow the actual flash player? It's alreaday installed. What makes you think it's not allowed? Flash works fine here, has for years. A discussion here some time ago. Some sites deny the access with the text my flash player wouldn't be actual. After installing the actual version (ends with already installed) the same result. Flashblock i don't know, also i don't use whitelists. actual = means current. The German word is Aktuell. Yes, several languages I know do that, including French and Russian. But it's good you posted that for the non-translators. -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: allowing flash player
Gerd Schweizer wrote: Paul B. Gallagher schrieb: Gerd Schweizer wrote: In Germany the tv organizations offer cinemas in the internet till one week after sending. But they need the flash player. How can i tell seamonkey to allow the actual flash player? It's alreaday installed. What makes you think it's not allowed? Flash works fine here, has for years. A discussion here some time ago. Some sites deny the access with the text my flash player wouldn't be actual. After installing the actual version (ends with already installed) the same result. Flashblock i don't know, also i don't use whitelists. A common scam used to propagate malware is when sites tell you your Flash is out of date and tell you to go to their own site to upgrade. You should only upgrade from Adobe's own site. You can test here, and if you pass, your installation is current and you can ignore the scams: Test Adobe Flash: https://www.adobe.com/software/flash/about/ Test Shockwave: https://www.adobe.com/shockwave/welcome/ -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: allowing flash player
Gerd Schweizer wrote: Paul B. Gallagher schrieb: Gerd Schweizer wrote: In Germany the tv organizations offer cinemas in the internet till one week after sending. But they need the flash player. How can i tell seamonkey to allow the actual flash player? It's alreaday installed. What makes you think it's not allowed? Flash works fine here, has for years. A discussion here some time ago. Some sites deny the access with the text my flash player wouldn't be actual. After installing the actual version (ends with already installed) the same result. Flashblock i don't know, also i don't use whitelists. actual = means current. The German word is Aktuell. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: allowing flash player
Paul B. Gallagher schrieb: Gerd Schweizer wrote: In Germany the tv organizations offer cinemas in the internet till one week after sending. But they need the flash player. How can i tell seamonkey to allow the actual flash player? It's alreaday installed. What makes you think it's not allowed? Flash works fine here, has for years. A discussion here some time ago. Some sites deny the access with the text my flash player wouldn't be actual. After installing the actual version (ends with already installed) the same result. Flashblock i don't know, also i don't use whitelists. -- Liebe Grüße, Gerd Satelliten FAQ, DVB-T, Katzen, Mopped, Garten, Heimwerken: http://www.satgerd.de/ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
allowing flash player
In Germany the tv organizations offer cinemas in the internet till one week after sending. But they need the flash player. How can i tell seamonkey to allow the actual flash player? It's alreaday installed. -- Liebe Grüße, Gerd Satelliten FAQ, DVB-T, Katzen, Mopped, Garten, Heimwerken: http://www.satgerd.de/ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: allowing flash player
Gerd Schweizer wrote: In Germany the tv organizations offer cinemas in the internet till one week after sending. But they need the flash player. How can i tell seamonkey to allow the actual flash player? It's alreaday installed. What makes you think it's not allowed? Flash works fine here, has for years. Exactly what happens when you try to play these? How about a sample URL? -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: allowing flash player
Paul B. Gallagher wrote: Gerd Schweizer wrote: In Germany the tv organizations offer cinemas in the internet till one week after sending. But they need the flash player. How can i tell seamonkey to allow the actual flash player? It's alreaday installed. What makes you think it's not allowed? Flash works fine here, has for years. Exactly what happens when you try to play these? How about a sample URL? Are you using the Flashblock extension? If you are using Flashblock then you may need to add the site you want to view video content to Flashblock's whitelist. To add a site to Flashblock's whitelist go to the browser menu and click on Tools-Add-ons Manager-Extensions You will see the extension Flashblock. Click on Flashblock's Preferences and then select Whitelist and add the site you want to use flash on. For example if you want to use flash on Youtube you would add the web address for Youtube (www.youtube.com) to the whitelist for flashblock. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
