[opensuse] Firefox is blocking outdated flash, it says.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, In my 13.1, Firefox is suddenly blocking outdated flash plugin, it says, yet I have the most recent YOU update. Telcontar:~ # rpm -qa | grep flash flash-player-gnome-11.2.202.440-94.1.x86_64 flash-player-11.2.202.440-94.1.x86_64 pullin-flash-player-12.3-4.1.2.x86_64 flash-player-kde4-11.2.202.440-94.1.x86_64 Telcontar:~ # Firefox about:plugins says: File: libflashplayer.so Path: /usr/lib64/browser-plugins/libflashplayer.so Version: 11.2.202.438 State: Enabled (STATE_VULNERABLE_UPDATE_AVAILABLE) Shockwave Flash 11.2 r202 What is wrong? Do we need yet another flash update? - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlTK6x0ACgkQtTMYHG2NR9XddgCeOKbMoaAxGbNczb3PI4OY7CpD SiQAmQGDvZ1GlW1Jbv8UX5/z/vRzxnS7 =X329 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday, January 30, 2015 03:23:14 AM Carlos E. R. wrote:
Hi,
In my 13.1, Firefox is suddenly blocking outdated flash plugin, it says, yet I have the most recent YOU update.
Telcontar:~ # rpm -qa | grep flash flash-player-gnome-11.2.202.440-94.1.x86_64 flash-player-11.2.202.440-94.1.x86_64 pullin-flash-player-12.3-4.1.2.x86_64 flash-player-kde4-11.2.202.440-94.1.x86_64 Telcontar:~ #
Firefox about:plugins says:
File: libflashplayer.so Path: /usr/lib64/browser-plugins/libflashplayer.so Version: 11.2.202.438 State: Enabled (STATE_VULNERABLE_UPDATE_AVAILABLE) Shockwave Flash 11.2 r202
Happening to me in 12.3 too, but it allows me tyo active it and have it remembered, so that it works for a while, and then spits up again. In some videos I casn click on the blank window and activate it. This jsut begun today. -- Bob Rea mailto:gapetard@stsams.org http://www.petard.us http://www.petard.us/blog http://www.petard.us/gallery What do you say to Jesus when he comes again? Where have you been? You said you were coming right back. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, No problems for me (I'm on 12.3), but at least the plugin-container must be restarted after the update. My package however differs from this on Patrick don't know why. rpm -q flash-player flash-player-11.2.202.440-2.115.1.x86_64 Best Regards, I. Petrov On 01/30/2015 05:18 AM, Robert Rea wrote:
On Friday, January 30, 2015 03:23:14 AM Carlos E. R. wrote:
Hi,
In my 13.1, Firefox is suddenly blocking outdated flash plugin, it says, yet I have the most recent YOU update.
Telcontar:~ # rpm -qa | grep flash flash-player-gnome-11.2.202.440-94.1.x86_64 flash-player-11.2.202.440-94.1.x86_64 pullin-flash-player-12.3-4.1.2.x86_64 flash-player-kde4-11.2.202.440-94.1.x86_64 Telcontar:~ #
Firefox about:plugins says:
File: libflashplayer.so Path: /usr/lib64/browser-plugins/libflashplayer.so Version: 11.2.202.438 State: Enabled (STATE_VULNERABLE_UPDATE_AVAILABLE) Shockwave Flash 11.2 r202
Happening to me in 12.3 too, but it allows me tyo active it and have it remembered, so that it works for a while, and then spits up again. In some videos I casn click on the blank window and activate it. This jsut begun today.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJUyvwQAAoJEH8sJoKRFRU5iqoP/1stRf/yqAEmsX0Zaxg031oB fxmLuG8Ds8MugmbGWdYo9b0Kpfl77eLF9SYoamdKO0NXBkFMoAWFGSc6JnN9U4YL kc4X5/p7R/e3xOPz/TQoSD19Zrm66W1jI1KL7Qaixw9BAaGrIO5oMJERr+1P6DCT FC10U5gs2JWP9MVXozk2XkfCFE8l2K2igIipAiP8hCmnRuX0SbdTOMsFc2Fq5moT JJ/81nRhXr/6QhRQ7auLdvHQDK/XMDI4zrgUuE7rX5Sw52upzt5cBqtpoMOOjLM3 ZsTNBmocb8v9DD3TOuib5EpS7kBjBq4lKZj+Vk8jVILjY0g1Ce4h3GmI6f2HLg8A MFokIllib5NDAuPHR7Bdvyc6IVcQIDwTj8rA++mUFmYnAMnO5ExX2Uv+Uty/KbHb wSMnjUhfVTeyZSgK0sqYuru00JnbNSprqebxoEQUVVJRyDU0I2CIoT757NnBrprP T2PLsj6vKklcD4SOftVLZlfJibNaecknZ471eQ6z1fXcayq0AI3wRVDwhm9Dvx1j HhkgWBuU9Sn5ybCleibRiLdwkzqWFLqLKBZNxcB+hMqlTxk3sHD4CezLTXITLQZF C3TIyQ6lBFtUaYdwN6xu2s04Lkf5YTL6WIQL72kwjIBHo9tcOKHD47nzYQTETI/f jeJEpi2FmxmhcEo6dCUu =DsoG -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 30 Jan 2015 04:35, I.Petrov <ico@...> wrote:
Hello,
No problems for me (I'm on 12.3), but at least the plugin-container must be restarted after the update. My package however differs from this on Patrick don't know why.
rpm -q flash-player flash-player-11.2.202.440-2.115.1.x86_64
Best Regards, I. Petrov
On 01/30/2015 05:18 AM, Robert Rea wrote:
On Friday, January 30, 2015 03:23:14 AM Carlos E. R. wrote:
Hi,
In my 13.1, Firefox is suddenly blocking outdated flash plugin, it says, yet I have the most recent YOU update.
Telcontar:~ # rpm -qa | grep flash flash-player-gnome-11.2.202.440-94.1.x86_64 flash-player-11.2.202.440-94.1.x86_64 pullin-flash-player-12.3-4.1.2.x86_64 flash-player-kde4-11.2.202.440-94.1.x86_64 Telcontar:~ #
Firefox about:plugins says:
File: libflashplayer.so Path: /usr/lib64/browser-plugins/libflashplayer.so Version: 11.2.202.438 State: Enabled (STATE_VULNERABLE_UPDATE_AVAILABLE) Shockwave Flash 11.2 r202
Happening to me in 12.3 too, but it allows me tyo active it and have it remembered, so that it works for a while, and then spits up again. In some videos I casn click on the blank window and activate it. This just begun today.
Excerpt from my FX.default.profile/blocklist.xml , dated 2015-01-28 22:39:04 GMT: [code] <blocklist xmlns="http://www.mozilla.org/2006/addons-blocklist" lastupdate="1422484744000"> ... <pluginItem os="Linux" blockID="p826"> <match name="filename" exp="libflashplayer\.so" /> <versionRange minVersion="11.2.202.425" maxVersion="11.2.202.439" severity="0" vulnerabilitystatus="1"> </versionRange> <infoURL>https://get.adobe.com/flashplayer/</infoURL> </pluginItem> [/code] If I read that right, all versions between .425 and .439 (edges included) are declared vulnerable, and blocked. So, version .438 is blocked, while .440 works. And, yes a restart of firefox after the plugin update is needed, else firefox does not read in the info on the plugin, just killing the plugin-container will not help. Does this give some enlightment? - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Yes you are right, I admit that the plugin-container was a blind shot :). Thanks for the enlightenment ... This just showed me how further warnings can be avoided :). Best Regards, I. Petrov On 01/30/2015 06:13 AM, Yamaban wrote:
On Fri, 30 Jan 2015 04:35, I.Petrov <ico@...> wrote:
Hello,
No problems for me (I'm on 12.3), but at least the plugin-container must be restarted after the update. My package however differs from this on Patrick don't know why.
rpm -q flash-player flash-player-11.2.202.440-2.115.1.x86_64
Best Regards, I. Petrov
On 01/30/2015 05:18 AM, Robert Rea wrote:
On Friday, January 30, 2015 03:23:14 AM Carlos E. R. wrote:
Hi,
In my 13.1, Firefox is suddenly blocking outdated flash plugin, it says, yet I have the most recent YOU update.
Telcontar:~ # rpm -qa | grep flash flash-player-gnome-11.2.202.440-94.1.x86_64 flash-player-11.2.202.440-94.1.x86_64 pullin-flash-player-12.3-4.1.2.x86_64 flash-player-kde4-11.2.202.440-94.1.x86_64 Telcontar:~ #
Firefox about:plugins says:
File: libflashplayer.so Path: /usr/lib64/browser-plugins/libflashplayer.so Version: 11.2.202.438 State: Enabled (STATE_VULNERABLE_UPDATE_AVAILABLE) Shockwave Flash 11.2 r202
Happening to me in 12.3 too, but it allows me tyo active it and have it remembered, so that it works for a while, and then spits up again. In some videos I casn click on the blank window and activate it. This just begun today.
Excerpt from my FX.default.profile/blocklist.xml , dated 2015-01-28 22:39:04 GMT: [code] <blocklist xmlns="http://www.mozilla.org/2006/addons-blocklist" lastupdate="1422484744000"> ... <pluginItem os="Linux" blockID="p826"> <match name="filename" exp="libflashplayer\.so" /> <versionRange minVersion="11.2.202.425" maxVersion="11.2.202.439" severity="0" vulnerabilitystatus="1"> </versionRange> <infoURL>https://get.adobe.com/flashplayer/</infoURL> </pluginItem> [/code]
If I read that right, all versions between .425 and .439 (edges included) are declared vulnerable, and blocked.
So, version .438 is blocked, while .440 works.
And, yes a restart of firefox after the plugin update is needed, else firefox does not read in the info on the plugin, just killing the plugin-container will not help.
Does this give some enlightment?
- Yamaban. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQIcBAEBAgAGBQJUyxDVAAoJEH8sJoKRFRU5k3YP/1IPD+H0p/NTOf8EYfzSMjDt 9W8ng2GYnp5DzOhOzg/5yTWK84LwxgsnkBH1tUAwQ48/PNn9p+G4u/6328zAJ+gG ktJG76EQtIZ5YshnJvjqzFBkXXWaxP5bAvheoBf6T8fnVKj5QHw8tZXQRyChEy4C bviSnDoitAil1iJh3k5pJRcKj/I8gyKWnzVUIhEBrEk9IyA4CFSsTBzCeX1GVOMx 4DxEK/TeNXHkijlMPQ3Xz1UB8cCC4DKJT5ao4RqXhrvb8FRP2zWviWAslAq1EZSZ ihdR+45Lx+xxVnqoRz4j1mXDDCWBo1uOSt+qb+BdS+W+TL60NEHq7a/nWQaEshn1 OShtSIhuDRy4uX81rGKhbUSkw2nlM3j3iyVpdMYG9od22O0XdqVaQzcDeQDdO1px BKzZsnjSzJ88ljS1PGxF6bRKG4SA3ZOfHrw7q2x4KtX1pB6joZ+xzL4n7WZ7Uzjx PffV8+85FPIPHf/jOMYxL4tOECkczEOAul3fVUL4CCQjnZde1pqrUAeG9zOLIk4C dRTpVb0I/gM/OL91I6bPtkj0SAVXMmyDeFJzBS1r7ur+2nEpTAlK5PcD2TC20bPw KK2M6eXoAdpj2iqYyUQVRzmZ9bfDGjySUMMt5rgkRkLOlF9tErG6selN/35lzBul Q28TvGMqqJSD23Ay+ft8 =TF/t -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-01-30 05:13, Yamaban wrote:
So, version .438 is blocked, while .440 works.
And, yes a restart of firefox after the plugin update is needed, else firefox does not read in the info on the plugin, just killing the plugin-container will not help.
Does this give some enlightment?
I restarted FF (again) and FF still says I have Version: 11.2.202.438. But the rpm is 11.2.202.440. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [01-30-15 07:33]:
On 2015-01-30 05:13, Yamaban wrote:
So, version .438 is blocked, while .440 works.
And, yes a restart of firefox after the plugin update is needed, else firefox does not read in the info on the plugin, just killing the plugin-container will not help.
Does this give some enlightment?
I restarted FF (again) and FF still says I have Version: 11.2.202.438. But the rpm is 11.2.202.440.
Firefox has a problem dealing with removal of user installed plugins and has for some years. There is ongoing work/discussion in their bug reports about it. That said, I would try removing the current plugin, restarting firefox and reinstalling the "correct" plugin. ps: might open the rpm and check the version reported as filename might be incorrect. gud luk, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-01-30 13:42, Patrick Shanahan wrote:
* Carlos E. R. <> [01-30-15 07:33]:
Firefox has a problem dealing with removal of user installed plugins and has for some years. There is ongoing work/discussion in their bug reports about it.
But it is not user installed, it is system installed. I see no "flash*" file installed in the ~/mozilla/* tree. However, I started FF as another user, and this one gets version 440. So the system library is correct, my user is getting it wrong somehow. Or rather FF is being stupid and getting the right file and incorrect info.
That said, I would try removing the current plugin, restarting firefox and reinstalling the "correct" plugin.
I doubt that reinstalling the rpm will do anything, as another user sees the correct version.
ps: might open the rpm and check the version reported as filename might be incorrect.
I looked inside the text strings of the binary library... correct. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2015-01-30 14:00, Carlos E. R. wrote:
However, I started FF as another user, and this one gets version 440. So the system library is correct, my user is getting it wrong somehow. Or rather FF is being stupid and getting the right file and incorrect info.
I wonder if there is a web page that loads a flash that checks the version :-? Bingo! Right click on a flash animation, about box, and it says that it is running 440. http://www.adobe.com/software/flash/about/ "You have version 11,2,202,440 installed" So I'll just tell FF to ignore warnings. FF is indeed running the correct version. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Edit manually pluginsreg.dat in your mozilla profile directory. There is a line with the flash-player version which you see in the about:plugins page (11.2.202.438 in your case). Below there is a line which starts with a timestamp 142205500000 (or similar) change it to e.g. 132205500000 and restart firefox. This should solve your problem as should force firefox to check for new plugins when starts. Best Regards, I. Petrov On 01/30/2015 03:00 PM, Carlos E. R. wrote:
On 2015-01-30 13:42, Patrick Shanahan wrote:
* Carlos E. R. <> [01-30-15 07:33]:
Firefox has a problem dealing with removal of user installed plugins and has for some years. There is ongoing work/discussion in their bug reports about it.
But it is not user installed, it is system installed.
I see no "flash*" file installed in the ~/mozilla/* tree.
However, I started FF as another user, and this one gets version 440. So the system library is correct, my user is getting it wrong somehow. Or rather FF is being stupid and getting the right file and incorrect info.
That said, I would try removing the current plugin, restarting firefox and reinstalling the "correct" plugin.
I doubt that reinstalling the rpm will do anything, as another user sees the correct version.
ps: might open the rpm and check the version reported as filename might be incorrect.
I looked inside the text strings of the binary library... correct.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJUy4OOAAoJEH8sJoKRFRU55IYP/A7EADsYQ0bjyaun5n8wDWcz D00s2hXypgpXL7PUa1Adlkng9IqQ1Y7JxTGSVi7ODdp1zMU1PlIWLr0aviQEGBRT d33KhI5EkRgDuLLvjFZKTcqLHsPhD1f8JMwye4ZeiUE/9nf768kV9oOTqqjwDQu7 yCa1HUWmCk1Kwlt7xQl8xQ2wBjjCKVbPeLLOSdJfpo8w5sZbQX72NQaQWIEbZMhf vGnIoSTdWgvi0Nq8vYrQpcEcW9KKXm8PqlY/M3U95x1DJpq56Hsybyn6pgxsRPar W1n0JVJ5mAexwnaW6lGXXnwvmaLL5jwaJjCDeoINRDBnIRAf5NQi5TSzC4QQjCRX JryrqlMJfdWdLryHWb6+gwLfHlXpbe1IzF1jbvD6yozEtQOjj/B44q+1IrtYQois Woa66s+7UfS3Qj7tiaqVq9k35W0mESL+NOrYGFyuy+Tx/xUTysvLIXcdoHNpJFC+ 8ExyhOZEqKApJuCZvcCVjtbiW3Qn6s9gFBvCzsntNer7VChlUzbJKr/s2zb+jwD/ KtFRLPMCn4Ktv12FUpq313vM6BtiKl126mrYdXwovbGxT6dBGyaG9WN7/Mk4jCGt eDFD6ivKlnaxjaexvgIPWKghLXJrMnFf2XN2yPfeOijcxf3mAUDQpAIRGPU6cLoH VkC3DWrh1SovN52FNVju =Psk+ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-01-30 14:13, I.Petrov wrote:
Hello,
Edit manually pluginsreg.dat in your mozilla profile directory. There is a line with the flash-player version which you see in the about:plugins page (11.2.202.438 in your case). Below there is a line which starts with a timestamp 142205500000 (or similar) change it to e.g. 132205500000 and restart firefox. This should solve your problem as should force firefox to check for new plugins when starts.
Bingo! It had: libflashplayer.so:$ /usr/lib64/browser-plugins/libflashplayer.so:$ 11.2.202.438:$ 1422055012000:0:0:0:$ Shockwave Flash 11.2 r202:$ Shockwave Flash:$ 2 0:application/x-shockwave-flash:Shockwave Flash:swf:$ 1:application/futuresplash:FutureSplash Player:spl:$ libnpjp2.so:$ I changed it as you say, restarted firefox, and now it says: Shockwave Flash File: libflashplayer.so Path: /usr/lib64/browser-plugins/libflashplayer.so Version: 11.2.202.440 State: Enabled Shockwave Flash 11.2 r202 and the regdat file says: libflashplayer.so:$ /usr/lib64/browser-plugins/libflashplayer.so:$ 11.2.202.440:$ 1422055012000:0:0:0:$ Shockwave Flash 11.2 r202:$ Shockwave Flash:$ The digits I edited are back to their old values, but the version string has changed to the correct one. Interesting! -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 01/30/2015 07:00 AM, Carlos E. R. wrote:
On 2015-01-30 13:42, Patrick Shanahan wrote:
* Carlos E. R. <> [01-30-15 07:33]: Firefox has a problem dealing with removal of user installed plugins and has for some years. There is ongoing work/discussion in their bug reports about it. But it is not user installed, it is system installed.
I see no "flash*" file installed in the ~/mozilla/* tree.
However, I started FF as another user, and this one gets version 440. So the system library is correct, my user is getting it wrong somehow. Or rather FF is being stupid and getting the right file and incorrect info.
That said, I would try removing the current plugin, restarting firefox and reinstalling the "correct" plugin. I doubt that reinstalling the rpm will do anything, as another user sees the correct version.
ps: might open the rpm and check the version reported as filename might be incorrect. I looked inside the text strings of the binary library... correct.
The bottom line is that flash for Linux is no longer supported beyond what you already have installed. It's a pain in the asphalt but you will just have to muddle through with what's available. I watched a flash video just a few minutes ago and I had to tell Firefox to use what it already had. It just doesn't seem to remember from start to the next start that you want it to use what flash plugin it has installed. There is no fix. There will be no fix. [ unless someone can crack flash and write a whole new plugin from scratch. ] At some point you may never be able to watch a flash video again in Linux. We will just have to learn to live without it. -- “Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century.” - Joan Rivers _ _... ..._ _ _._ ._ ..... ._.. ... .._ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 30/01/2015 15:37, Billie Walsh a écrit :
able to watch a flash video again in Linux. We will just have to learn to live without it.
fisrt hope than anybody move to html5 :-) in the midtime use an emulator. The simpler is PlayOnLinux that have a preconfigured Firefox whith the last flash (windows version under wine, that is very difficult to configure directly) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-01-30 15:37, Billie Walsh wrote:
The bottom line is that flash for Linux is no longer supported beyond
Tell that to my water supplier. Not videos, but actual menus. And 50% cpu load. It works now, It was FF fault, not flash. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Am 30.01.2015 um 15:56 schrieb Carlos E. R.:
On 2015-01-30 15:37, Billie Walsh wrote:
The bottom line is that flash for Linux is no longer supported beyond
Tell that to my water supplier. Not videos, but actual menus. And 50% cpu load.
You're in Spain, no? I've never seen so many useless flash sites like here and I've never seen so much inability even in big companies. Sometimes I wonder why internet even works here. In fact my former electricity supplier had a website that was only accessible with internet exploder. As they, of course, did not react on my complaint, I have changed the supplier. Now I pay less and have a quite decent website to see my bills... YOU must tell them. Otherwise they think they are great geniuses and instead of doing their work take another mojito on the beach :-) The consumer is the boss! You. -- Daniel Bauer photographer Basel Barcelona http://www.daniel-bauer.com room in Barcelona: https://www.airbnb.es/rooms/2416137 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday 30 January 2015, Daniel Bauer wrote:
Am 30.01.2015 um 15:56 schrieb Carlos E. R.:
On 2015-01-30 15:37, Billie Walsh wrote:
The bottom line is that flash for Linux is no longer supported beyond
Tell that to my water supplier. Not videos, but actual menus. And 50% cpu load.
You're in Spain, no? I've never seen so many useless flash sites like here and I've never seen so much inability even in big companies. Sometimes I wonder why internet even works here.
In fact my former electricity supplier had a website that was only accessible with internet exploder. As they, of course, did not react on my complaint, I have changed the supplier. Now I pay less and have a quite decent website to see my bills...
YOU must tell them. Otherwise they think they are great geniuses and instead of doing their work take another mojito on the beach :-)
The consumer is the boss! You.
Hehe, I remember one story where we called our Bank's support (AFAIR Deutsche Bank) to tell them about a flash related problem with a certain website of them. But the support could reproduce it because they had the policy to not allow their employees to have flash installed ... and they didn't fixed it. cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-01-30 16:15, Ruediger Meier wrote:
Hehe, I remember one story where we called our Bank's support (AFAIR Deutsche Bank) to tell them about a flash related problem with a certain website of them.
But the support could reproduce it because they had the policy to not allow their employees to have flash installed ... and they didn't fixed it.
LOL. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Friday 30 January 2015, Ruediger Meier wrote:
On Friday 30 January 2015, Daniel Bauer wrote:
Am 30.01.2015 um 15:56 schrieb Carlos E. R.:
On 2015-01-30 15:37, Billie Walsh wrote:
The bottom line is that flash for Linux is no longer supported beyond
Tell that to my water supplier. Not videos, but actual menus. And 50% cpu load.
You're in Spain, no? I've never seen so many useless flash sites like here and I've never seen so much inability even in big companies. Sometimes I wonder why internet even works here.
In fact my former electricity supplier had a website that was only accessible with internet exploder. As they, of course, did not react on my complaint, I have changed the supplier. Now I pay less and have a quite decent website to see my bills...
YOU must tell them. Otherwise they think they are great geniuses and instead of doing their work take another mojito on the beach :-)
The consumer is the boss! You.
Hehe, I remember one story where we called our Bank's support (AFAIR Deutsche Bank) to tell them about a flash related problem with a certain website of them.
But the support could reproduce it because they had the policy to not I ment could NOT ... of course.
allow their employees to have flash installed ... and they didn't fixed it.
cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-01-30 17:52, Ruediger Meier wrote:
I ment could NOT ... of course.
I knew. My mind silently supplied the missing word so that the meaning was as you intended. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2015-01-30 16:08, Daniel Bauer wrote:
Am 30.01.2015 um 15:56 schrieb Carlos E. R.:
On 2015-01-30 15:37, Billie Walsh wrote:
The bottom line is that flash for Linux is no longer supported beyond
Tell that to my water supplier. Not videos, but actual menus. And 50% cpu load.
You're in Spain, no? I've never seen so many useless flash sites like here and I've never seen so much inability even in big companies. Sometimes I wonder why internet even works here.
Money. People have offered services to businesses to create presence in Internet, so they do. Shiny sites, often with static information. With mailboxes they never even retrieve.
In fact my former electricity supplier had a website that was only accessible with internet exploder. As they, of course, did not react on my complaint, I have changed the supplier. Now I pay less and have a quite decent website to see my bills...
Try Chrome. Most of the sites I need work with FF, and those that don't work with Chrome. But yes, I know at least one that wants IE: Securitas Direct. And it is not based in Spain. The other day they emailed a link to a new test site that asks for login, on a different domain, so it could be a phishing attempt. Yes, I emailed them, complaining. No answer. But at least it works in Linux. Many gadgets require you use Windows for maintenance. Like Samsung or TomTom. Even if the gadgets have Linux inside.
YOU must tell them. Otherwise they think they are great geniuses and instead of doing their work take another mojito on the beach :-)
"Yo paso". That's a lost cause here. In fact this water company doesn't do anything over internet. The flash box is just a list of phones and addresses. Street addresses, no email. Fax. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Am 30.01.2015 um 15:37 schrieb Billie Walsh:
The bottom line is that flash for Linux is no longer supported beyond what you already have installed. It's a pain in the asphalt but you will just have to muddle through with what's available. I watched a flash video just a few minutes ago and I had to tell Firefox to use what it already had. It just doesn't seem to remember from start to the next start that you want it to use what flash plugin it has installed. There is no fix. There will be no fix. [ unless someone can crack flash and write a whole new plugin from scratch. ] At some point you may never be able to watch a flash video again in Linux. We will just have to learn to live without it.
Flash is dead. Is was a pain since it appeared, like most closed-source software is a pain and will be even more in future, because it's goal is not to serve the user but the selling, controlling, data-stealing organization behind it. As for now we still do have a "secure" lash plugin on linux. If this wouldn't work anymore in future there is big brothers chrome with it's own implementation (I guess sucking even more data, but letting it run under an otherwise empty and moreorless rights-less user just for those dinosaur pages that wouldn't work in a better browser will do it) I'm pretty sure that there will be no more need for flash plugins quite soon. html5 is so much better. and free. -- Daniel Bauer photographer Basel Barcelona http://www.daniel-bauer.com room in Barcelona: https://www.airbnb.es/rooms/2416137 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/30/2015 05:01 PM, Daniel Bauer wrote:
It's a pain in the asphalt but ~ ................
- using TW : Google-Chrome browser seems to work well : believe it has built-in flash that Chromium does not have ............ regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday 30 January 2015, ellanios82 wrote:
On 01/30/2015 05:01 PM, Daniel Bauer wrote:
It's a pain in the asphalt but ~
................
- using TW : Google-Chrome browser seems to work well : believe it has built-in flash that Chromium does not have
Yep and it's even up-to-date version 16.0.0.291. It's because Adobe sold the sources somehow to google. http://blogs.adobe.com/flashplayer/2012/02/adobe-and-google-partnering-for-f... Well, snd that's why they are not interested to update the ns plugin (for other browsers) anymore ... cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/30/2015 06:37 AM, Billie Walsh wrote:
The bottom line is that flash for Linux is no longer supported beyond what you already have installed. It's a pain in the asphalt but you will just have to muddle through with what's available. I watched a flash video just a few minutes ago and I had to tell Firefox to use what it already had. It just doesn't seem to remember from start to the next start that you want it to use what flash plugin it has installed. There is no fix. There will be no fix. [ unless someone can crack flash and write a whole new plugin from scratch. ] At some point you may never be able to watch a flash video again in Linux. We will just have to learn to live without it.
FWIW, my granddaughter complained that Firefox on her Ubuntu 14.04 laptop was throwing the flash version warning. This was just last night. So I pulled an update, which fixed the problem without even rebooting the box. I don't know what Ubuntu did with flash, but it seems to work. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/30/2015 09:37 AM, Billie Walsh wrote:
The bottom line is that flash for Linux is no longer supported beyond what you already have installed. It's a pain in the asphalt but you will just have to muddle through with what's available.
One thing I came across recently. Many sites have both flash and HTML5 videos available. Many browsers, including Firefox default to flash. You can change the default to HTML5 by going to www.youtube.com/html5. That will change it for Youtube. I don't know if it affects other sites. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-01-30 16:42, James Knott wrote:
That will change it for Youtube. I don't know if it affects other sites.
Nope. Static videos have often alternatives, but not all flash are videos. Some sites use menus in flash. I have see training sites on flash. For instance, Cisco used that method some years ago, I don't know now. TV/Radio stations usually have "players" for audio or video online, and they often use flash for this. Commercials served by google sometimes are flash based. I don't see any actual tendency to remove flash from sites any time soon. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Am 30.01.2015 um 17:15 schrieb Carlos E. R.:
On 2015-01-30 16:42, James Knott wrote:
That will change it for Youtube. I don't know if it affects other sites.
Nope.
From the german mailing list about a similar topic: in about:config in Firefox change media.mediasource.enabled to true hth -- Daniel Bauer photographer Basel Barcelona http://www.daniel-bauer.com room in Barcelona: https://www.airbnb.es/rooms/2416137 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Fri, 30 Jan 2015 17:15:26 +0100 "Carlos E. R." <robin.listas@telefonica.net> пишет:
I have see training sites on flash. For instance, Cisco used that method some years ago, I don't know now.
NetApp and Oracle have many (I believe, all I have used) web trainings in flash.
On 01/30/2015 11:15 AM, Carlos E. R. wrote:
That will change it for Youtube. I don't know if it affects other sites. Nope.
What is it that gets changed so that HTML5 is selected? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 30.01.2015 um 18:03 schrieb James Knott:
On 01/30/2015 11:15 AM, Carlos E. R. wrote:
That will change it for Youtube. I don't know if it affects other sites. Nope.
What is it that gets changed so that HTML5 is selected?
not sure but I guess it's just a cookie that tells youtube to send the html5-content instead of flash. Imbedded youtube-players on other sites can read that cookie, too. Check my earlier post about about:config. -- Daniel Bauer photographer Basel Barcelona http://www.daniel-bauer.com room in Barcelona: https://www.airbnb.es/rooms/2416137 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Fri, 30 Jan 2015, Billie Walsh wrote:
The bottom line is that flash for Linux is no longer supported beyond what you already have installed.
Ahem, who do you think provided the updates to .438 and now .440 then? Adobe _still_ obviously does fix security problems so it seems. But that's it. Enjoy while it lasts. And, again I have .440 available for 12.1-12.3 in my home repo if you're lagging with the upgrade to 13.x
It's a pain in the asphalt but you will just have to muddle through with what's available. I watched a flash video just a few minutes ago and I had to tell Firefox to use what it already had. It just doesn't seem to remember from start to the next start that you want it to use what flash plugin it has installed.
You seem rather confused here. Do you have multiple flash-plugins installed? If so: clean up. Remove them all! I recommend you remove alternative plugins (gnash etc.) too. Install the latest 11.2.202.440. All fixed. And install the prefbar addon so you can switch on flash only when wanted. And Noscript. <comment elided> -dnh -- * Linux Viruscan..... Windows 95 found. Remove it? (Y/y) -- Unknown source -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/31/2015 12:22 AM, David Haller wrote:
Hello,
The bottom line is that flash for Linux is no longer supported beyond what you already have installed. Ahem, who do you think provided the updates to .438 and now .440 then? Adobe _still_ obviously does fix security problems so it seems. But
On Fri, 30 Jan 2015, Billie Walsh wrote: that's it. Enjoy while it lasts. And, again I have .440 available for 12.1-12.3 in my home repo if you're lagging with the upgrade to 13.x
It's a pain in the asphalt but you will just have to muddle through with what's available. I watched a flash video just a few minutes ago and I had to tell Firefox to use what it already had. It just doesn't seem to remember from start to the next start that you want it to use what flash plugin it has installed. You seem rather confused here. Do you have multiple flash-plugins installed? If so: clean up. Remove them all! I recommend you remove alternative plugins (gnash etc.) too. Install the latest 11.2.202.440. All fixed. And install the prefbar addon so you can switch on flash only when wanted. And Noscript.
<comment elided> -dnh
According to the Adobe website: "*NOTE*: Adobe Flash Player 11.2 will be the last version to target Linux as a supported platform. Adobe will continue to provide security backports to Flash Player 11.2 for Linux." I do have the latest and greatest installed. Firefox still wants a newer version that will never come. The Windows version of Flash Player is now 16.0.0.296. This is what Firefox is programmed to want. -- “Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century.” - Joan Rivers _ _... ..._ _ _._ ._ ..... ._.. ... .._ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 31 Jan 2015 13:22, Billie Walsh wrote:
On 01/31/2015 12:22 AM, David Haller wrote:
On Fri, 30 Jan 2015, Billie Walsh wrote:
The bottom line is that flash for Linux is no longer supported beyond what you already have installed.
Ahem, who do you think provided the updates to .438 and now .440 then? Adobe _still_ obviously does fix security problems so it seems. But that's it. Enjoy while it lasts. And, again I have .440 available for 12.1-12.3 in my home repo if you're lagging with the upgrade to 13.x
It's a pain in the asphalt but you will just have to muddle through with what's available. I watched a flash video just a few minutes ago and I had to tell Firefox to use what it already had. It just doesn't seem to remember from start to the next start that you want it to use what flash plugin it has installed. You seem rather confused here. Do you have multiple flash-plugins installed? If so: clean up. Remove them all! I recommend you remove alternative plugins (gnash etc.) too. Install the latest 11.2.202.440. All fixed. And install the prefbar addon so you can switch on flash only when wanted. And Noscript.
<comment elided> -dnh
According to the Adobe website:
"*NOTE*: Adobe Flash Player 11.2 will be the last version to target Linux as a supported platform. Adobe will continue to provide security backports to Flash Player 11.2 for Linux."
I do have the latest and greatest installed. Firefox still wants a newer version that will never come.
The Windows version of Flash Player is now 16.0.0.296. This is what Firefox is programmed to want.
False. Wrong. FF handles each operating system for each own. Open the blocklist.xml from your FF profile dir and see for your self: Look at the matches for the filenames: For MacOS only: <pluginItem blockID="p94"> <match name="filename" exp="Flash\ Player\.plugin" /> <versionRange minVersion="0" maxVersion="10.2.159.1" severity="0"> </versionRange> <infoURL>https://get.adobe.com/flashplayer/</infoURL> </pluginItem> For MS Windows only: <pluginItem blockID="p160"> <match name="filename" exp="NPSWF32\.dll" /> <versionRange minVersion="0" maxVersion="10.2.9999" severity="0" vulnerabilitystatus="1"> </versionRange> <infoURL>https://get.adobe.com/flashplayer/</infoURL> </pluginItem> For Linux only: <pluginItem os="Linux" blockID="p826"> <match name="filename" exp="libflashplayer\.so" /> <versionRange minVersion="11.2.202.425" maxVersion="11.2.202.439" severity="0" vulnerabilitystatus="1"> </versionRange> <infoURL>https://get.adobe.com/flashplayer/</infoURL> </pluginItem> For MacOS and Windows combined: <pluginItem blockID="p828"> <match name="filename" exp="(NPSWF32.*\.dll)|(Flash\ Player\.plugin)" /> <versionRange minVersion="15.0.0.243" maxVersion="16.0.0.287" severity="0" vulnerabilitystatus="1"> </versionRange> <infoURL>https://get.adobe.com/flashplayer/</infoURL> </pluginItem> Each OS is handled as needed. ATM the version numbers for MacOS and Windows are the same, thus a combined entry is used. But Linux has only limited support by Adobe and thus a other version number, and gets a own entry. Please, check first, then reply to a mail. - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-01-31 13:22, Billie Walsh wrote:
I do have the latest and greatest installed. Firefox still wants a newer version that will never come.
False. Read the thread for the solution. I solved it. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
* Carlos E. R. <carlos.e.r@opensuse.org> [01-29-15 21:26]:
In my 13.1, Firefox is suddenly blocking outdated flash plugin, it says, yet I have the most recent YOU update.
Telcontar:~ # rpm -qa | grep flash flash-player-gnome-11.2.202.440-94.1.x86_64 flash-player-11.2.202.440-94.1.x86_64 pullin-flash-player-12.3-4.1.2.x86_64 flash-player-kde4-11.2.202.440-94.1.x86_64 Telcontar:~ #
Firefox about:plugins says:
File: libflashplayer.so Path: /usr/lib64/browser-plugins/libflashplayer.so Version: 11.2.202.438 State: Enabled (STATE_VULNERABLE_UPDATE_AVAILABLE) Shockwave Flash 11.2 r202
openSUSE Tw rpm -qa |grep flash pullin-flash-player-12.3-7.1.x86_64 flash-player-kde4-11.2.202.440-1.1.x86_64 flash-player-11.2.202.440-1.1.x86_64 Firefox about:plugins File: libflashplayer.so Path: /usr/lib64/browser-plugins/libflashplayer.so Version: 11.2.202.440 State: Enabled Shockwave Flash 11.2 r202
What is wrong? Do we need yet another flash update?
Don't know, but haven't seen any probs here... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 В Fri, 30 Jan 2015 03:23:14 +0100 (CET) "Carlos E. R." <carlos.e.r@opensuse.org> пишет:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
In my 13.1, Firefox is suddenly blocking outdated flash plugin, it says, yet I have the most recent YOU update.
Telcontar:~ # rpm -qa | grep flash flash-player-gnome-11.2.202.440-94.1.x86_64 flash-player-11.2.202.440-94.1.x86_64 pullin-flash-player-12.3-4.1.2.x86_64 flash-player-kde4-11.2.202.440-94.1.x86_64 Telcontar:~ #
Firefox about:plugins says:
File: libflashplayer.so Path: /usr/lib64/browser-plugins/libflashplayer.so Version: 11.2.202.438
Did you restart firefox ater flash update?
State: Enabled (STATE_VULNERABLE_UPDATE_AVAILABLE) Shockwave Flash 11.2 r202
What is wrong? Do we need yet another flash update?
- -- Cheers Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlTK6x0ACgkQtTMYHG2NR9XddgCeOKbMoaAxGbNczb3PI4OY7CpD SiQAmQGDvZ1GlW1Jbv8UX5/z/vRzxnS7 =X329 -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTK+hsACgkQR6LMutpd94yAcQCgiyfcGWPH0xssOuYoBpVrYlEd 0QcAn3RpsjvlNVELfSLiYd3sTpTnvp2C =hWzN -----END PGP SIGNATURE-----
On 2015-01-30 04:27, Andrei Borzenkov wrote:
В Fri, 30 Jan 2015 03:23:14 +0100 (CET) "Carlos E. R." <> пишет:
Telcontar:~ # rpm -qa | grep flash flash-player-gnome-11.2.202.440-94.1.x86_64 flash-player-11.2.202.440-94.1.x86_64 pullin-flash-player-12.3-4.1.2.x86_64 flash-player-kde4-11.2.202.440-94.1.x86_64 Telcontar:~ #
Firefox about:plugins says:
File: libflashplayer.so Path: /usr/lib64/browser-plugins/libflashplayer.so Version: 11.2.202.438
I looked at an hexdump of "/usr/lib64/browser-plugins/libflashplayer.so". I see: |mms:.view-source| |:.serverString.L| |NX 11,2,202,440.| |hasAudio.hasStre| That's the version string, and it is correct, 440. Yet FF says 438. Not only I restarted FF, I restarted the entire graphical session. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Fri, 30 Jan 2015 13:52, Carlos E. R. <robin.listas@...> wrote:
On 2015-01-30 04:27, Andrei Borzenkov wrote:
В Fri, 30 Jan 2015 03:23:14 +0100 (CET) "Carlos E. R." <> пишет:
Telcontar:~ # rpm -qa | grep flash flash-player-gnome-11.2.202.440-94.1.x86_64 flash-player-11.2.202.440-94.1.x86_64 pullin-flash-player-12.3-4.1.2.x86_64 flash-player-kde4-11.2.202.440-94.1.x86_64 Telcontar:~ #
Firefox about:plugins says:
File: libflashplayer.so Path: /usr/lib64/browser-plugins/libflashplayer.so Version: 11.2.202.438
I looked at an hexdump of "/usr/lib64/browser-plugins/libflashplayer.so". I see:
|mms:.view-source| |:.serverString.L| |NX 11,2,202,440.| |hasAudio.hasStre|
That's the version string, and it is correct, 440. Yet FF says 438.
Not only I restarted FF, I restarted the entire graphical session.
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. - Yamaban.
This thread seems to have omitted info about which openSUSE release(s) the Flash security breach(es) apply to. On http://software.opensuse.org/package/flash-player only for TW is 440 shown. For 13.2 it's 411 and for 13.1 it's 310. What's the scoop? Why is latest Flash older for older yet supported releases? Are they all the same player version and just the rpm version is different? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 31 Jan 2015 01:40, Felix Miata wrote:
This thread seems to have omitted info about which openSUSE release(s) the Flash security breach(es) apply to. On http://software.opensuse.org/package/flash-player only for TW is 440 shown. For 13.2 it's 411 and for 13.1 it's 310. What's the scoop? Why is latest Flash older for older yet supported releases? Are they all the same player version and just the rpm version is different?
AFAIK only the version included in the "GoldMaster" of the release is shown, and the "update-repo" is fully ignored, no matter what package. Even more giggle worthy is the state of the versions shown for Factory. There you will find nearly any version, but the actual. Maybe that could be GSOC project, to get the "update-repo" state shown here, too? - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-01-31 01:40, Felix Miata wrote:
This thread seems to have omitted info about which openSUSE release(s) the Flash security breach(es) apply to.
Nope. I said: cer> In my 13.1, Firefox is suddenly blocking outdated flash plugin, it says, cer> yet I have the most recent YOU update. So, 13.1. And it is also in my signature. But the update applies to all oS releases. I think even 14.1 got it.
On http://software.opensuse.org/package/flash-player only for TW is 440 shown. For 13.2 it's 411 and for 13.1 it's 310. What's the scoop? Why is latest Flash older for older yet supported releases? Are they all the same player version and just the rpm version is different?
I have version 440 on oS 13.1. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. composed on 2015-01-31 02:02 (UTC+0100):
Felix Miata wrote:
This thread seems to have omitted info about which openSUSE release(s) the Flash security breach(es) apply to.
Nope. I said:
cer> In my 13.1, Firefox is suddenly blocking outdated flash plugin, it says, cer> yet I have the most recent YOU update.
Must have been yesterday, out with the trash I emptied after midnight.
So, 13.1. And it is also in my signature.
Among the 36 thread posts remaining in my trash I found no clue who started the thread, and mistakely thought to what it applied would be among such a large number of posts. You might have considerered a subject line with your OS version. Not everyone remembers which version(s) every regular here runs, and in successful archive searches it's commonly vital to know which OS version is being discussed to actually locate the information sought.
But the update applies to all oS releases. I think even 14.1 got it.
14.1? No such on https://en.opensuse.org/openSUSE:Roadmap Do you mean Tumbleweed aka pre-beta 13.3?
On http://software.opensuse.org/package/flash-player only for TW is 440 shown. For 13.2 it's 411 and for 13.1 it's 310. What's the scoop? Why is latest Flash older for older yet supported releases? Are they all the same player version and just the rpm version is different?
I have version 440 on oS 13.1.
The following, in addition to what I wrote about software.opensuse.org, is what lead me to write: # grep PRETTY /etc/os-release PRETTY_NAME="openSUSE 13.1 (Bottle) (i586)" # rpm -qa | flash-player | grep -v pullin flash-player-11.2.202.310-2.1.6.i586 # zypper ref; zypper se -s flash-player | grep 586 | grep -v pullin i | flash-player | package | 11.2.202.310-2.1.6 | i586 | Non-OSS | flash-player-gnome | package | 11.2.202.310-2.1.6 | i586 | Non-OSS | flash-player-kde4 | package | 11.2.202.310-2.1.6 | i586 | Non-OSS Only one available? That cannot be right. As if Flash itself wasn't a bad enough problem, people ought to be able to get what they need reliably about installed packages from their package manager instead of this confusion. X wasn't and isn't running here, so no opportunity to goto about:plugins. I'm trying to get a new RAID configured, reading here during waits, and being obstructed by stupid little things like this coming from every direction. It's a new 13.1, which ultimately will be on RAID, and right now with all packages I thought I needed already installed, it takes over a minute to start shutting down once instructed to shut down. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-01-31 03:10, Felix Miata wrote:
Carlos E. R. composed on 2015-01-31 02:02 (UTC+0100):
Must have been yesterday, out with the trash I emptied after midnight.
So, 13.1. And it is also in my signature.
Among the 36 thread posts remaining in my trash I found no clue who started the thread, and mistakely thought to what it applied would be among such a large number of posts.
You might have considerered a subject line with your OS version. Not everyone remembers which version(s) every regular here runs, and in successful archive searches it's commonly vital to know which OS version is being discussed to actually locate the information sought.
But I place that information on the signature. And I don't delete a thread in mail list in about a year, so I don't have problems with locating the starting post. The archives have it all, complete, so the information is there. No, it is your fault for deleting posts too early, or not looking it up in the archive. :-P :-)
But the update applies to all oS releases. I think even 14.1 got it.
14.1? No such on https://en.opensuse.org/openSUSE:Roadmap Do you mean Tumbleweed aka pre-beta 13.3?
Nope. I do mean 11.4, the very old 11.4 which is still partially supported by the Evergreen group. You surely know what Evergreen is?
I have version 440 on oS 13.1.
The following, in addition to what I wrote about software.opensuse.org, is what lead me to write:
# grep PRETTY /etc/os-release PRETTY_NAME="openSUSE 13.1 (Bottle) (i586)"
# rpm -qa | flash-player | grep -v pullin flash-player-11.2.202.310-2.1.6.i586
# zypper ref; zypper se -s flash-player | grep 586 | grep -v pullin i | flash-player | package | 11.2.202.310-2.1.6 | i586 | Non-OSS | flash-player-gnome | package | 11.2.202.310-2.1.6 | i586 | Non-OSS | flash-player-kde4 | package | 11.2.202.310-2.1.6 | i586 | Non-OSS
Only one available? That cannot be right.
Well, your system is wrong. :-) Version 310 is the never updated version, from the non-oss repo. Did you remove the non-oss-update repo? Telcontar:~ # zypper --no-refresh se --details flash-player Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+---------------------+------------+--------------------+--------+----------------------------- i | flash-player | package | 11.2.202.440-94.1 | x86_64 | openSUSE-13.1-Update-Non-Oss v | flash-player | package | 11.2.202.438-90.1 | x86_64 | openSUSE-13.1-Update-Non-Oss v ... v | flash-player | package | 11.2.202.440-94.1 | i586 | openSUSE-13.1-Update-Non-Oss v | flash-player | package | 11.2.202.438-90.1 | i586 | openSUSE-13.1-Update-Non-Oss ... v | flash-player | package | 11.2.202.310-2.1.6 | i586 | openSUSE-13.1-Non-Oss -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. composed on 2015-01-31 03:51 (UTC+0100):
On 2015-01-31 03:10, Felix Miata wrote:
Carlos E. R. composed on 2015-01-31 02:02 (UTC+0100):
Must have been yesterday, out with the trash I emptied after midnight.
So, 13.1. And it is also in my signature.
Among the 36 thread posts remaining in my trash I found no clue who started the thread, and mistakely thought to what it applied would be among such a large number of posts.
You might have considerered a subject line with your OS version. Not everyone remembers which version(s) every regular here runs, and in successful archive searches it's commonly vital to know which OS version is being discussed to actually locate the information sought.
But I place that information on the signature.
Signatures are supposed to be limited to a reasonable length, so that particular bit isn't in mine, which is just as well, as not every reader of email even gets to find out any .sig even exists. Some email apps hide it. I only look there in OPs. Your OP escaped here 23 hours ago.
And I don't delete a thread in mail list in about a year, so I don't have problems with locating the starting post. The archives have it all, complete, so the information is there.
Lucky you. I count on online archives, but in this case, like many openSUSE, I skipped even looking there, because in the high volume lists finding things there is annoying due to absence of date sorting in by-author pages. Finding any particular OP hurts my eyes. I thought the 36 in trash should have provided enough info. My mistake.
No, it is your fault for deleting posts too early,
I get hundreds of emails a day, so have to deal with most quickly to prevent backup. I wasn't interested in this thread yesterday, so none from it carried over.
or not looking it up in the archive. :-P :-)
Yup.
But the update applies to all oS releases. I think even 14.1 got it.
14.1? No such on https://en.opensuse.org/openSUSE:Roadmap Do you mean Tumbleweed aka pre-beta 13.3?
Nope. I do mean 11.4, the very old 11.4 which is still partially supported by the Evergreen group.
When you mean 11.4, don't write 14.1. It's confusing.
You surely know what Evergreen is?
It's what I'm in the middle of trying to escape from on this 24/7 box, something I've been trying to do since October. If you see little to nothing from me here in the coming hours (or day or two), that should be why.
# rpm -qa | flash-player | grep -v pullin flash-player-11.2.202.310-2.1.6.i586
# zypper ref; zypper se -s flash-player | grep 586 | grep -v pullin i | flash-player | package | 11.2.202.310-2.1.6 | i586 | Non-OSS | flash-player-gnome | package | 11.2.202.310-2.1.6 | i586 | Non-OSS | flash-player-kde4 | package | 11.2.202.310-2.1.6 | i586 | Non-OSS
Only one available? That cannot be right.
Well, your system is wrong. :-)
Ya think. :-D
Version 310 is the never updated version, from the non-oss repo. Did you remove the non-oss-update repo?
Funny story. Turns it it appears, until now, I may not have had that particular repo on any installation newer than 12.2. Flash is a usability nightmare, so it doesn't get installed on my testing installations, and is allowed to be found on no more than one Mozilla profile per local user, if that many. Apparently the only thing in that repo besides Flash that I've ever installed is Opera, which I stopped caring about too long ago to remember. Thus, when the leading "repo-"s got stripped from /etc/zypp/repos.d/, that one got removed rather than edited. Now that I have 440 I can go back to figuring out why a reboot takes a minute before anything shutdown related becomes apparent. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Fri, 30 Jan 2015 19:40:24 -0500 Felix Miata <mrmazda@earthlink.net> пишет:
This thread seems to have omitted info about which openSUSE release(s) the Flash security breach(es) apply to. On http://software.opensuse.org/package/flash-player only for TW is 440 shown. For 13.2 it's 411
flash-player-11.2.202.440-2.29.1.x86_64 and for 13.1 it's 310. What's the scoop? Why is latest
Flash older for older yet supported releases? Are they all the same player version and just the rpm version is different?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-01-30 21:23, Yamaban wrote:
On Fri, 30 Jan 2015 13:52, Carlos E. R. <robin.listas@...> 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? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Sat, 31 Jan 2015 01:53:11 +0100 Carlos E. R. wrote:
Isn't deleting the entire file too drastic, or is it recreated fully without destroying something important? Side effects?
This fix isn't dramatic at all and it goes back ages. It's completely harmless. It just forces FF to evaluate what plugins are installed and re-register them (recreating the file in the process.) regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2015-01-31 01:58, Carl Hartung wrote:
On Sat, 31 Jan 2015 01:53:11 +0100 Carlos E. R. wrote:
Isn't deleting the entire file too drastic, or is it recreated fully without destroying something important? Side effects?
This fix isn't dramatic at all and it goes back ages. It's completely harmless. It just forces FF to evaluate what plugins are installed and re-register them (recreating the file in the process.)
Good to know. But I'll forget :-( Wrote a note file in the FF directory... now I have to remember to look in it, next time ;-) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
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
On 2015-01-31 02:12, Yamaban wrote:
On Sat, 31 Jan 2015 01:53, Carlos E. R. wrote:
...
That is why this file can be removed without harm.
Thanks for the explanation, instructive :-) Yes, I understand the concept of that file. Makes sense.
For further info the MozillaZine Knowlegdebase is a good startpoint. http://kb.mozillazine.org/Flash
Ah! I forgot about that resource. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
participants (17)
-
Andrei Borzenkov
-
Billie Walsh
-
Carl Hartung
-
Carlos E. R.
-
Carlos E. R.
-
Daniel Bauer
-
David Haller
-
ellanios82
-
Felix Miata
-
I.Petrov
-
James Knott
-
jdd
-
Lew Wolfgang
-
Patrick Shanahan
-
Robert Rea
-
Ruediger Meier
-
Yamaban