Flash 11.2.202.228 solutions

[QIII]

If worse comes to worst while the community works on a solution to such a blatant "nose-thumbing" from Adobe, I may have to dig out an XP disk and run it in VBox for Flash content. Sigh.

[lovinglinux]

If worse comes to worst while the community works on a solution to such a blatant "nose-thumbing" from Adobe, I may have to dig out an XP disk and run it in VBox for Flash content. Sigh.

Well, I can't say I haven't thought about that too. But either doing that or using Chrome will brake my work-flow. At least using Chrome we can use the "Open With" feature of Opera or the Firefox extension.

[Trapper]

Because Adobe is no longer supporting Flash on Linux. They gave this task to Google, which will release a new kind o plugin, using Chrome Pepper API. Neither Mozilla or Opera will adopt Pepper.

Okay. Another squeeze to eliminate competition and to get everyone to "buy" into specific new technologies and hardwares. Firefox is pretty much dead without flash support unless flash is going to be replaced. What's the roadmap here?

[gradinaruvasile]

If worse comes to worst while the community works on a solution to such a blatant "nose-thumbing" from Adobe, I may have to dig out an XP disk and run it in VBox for Flash content. Sigh.

Nah, its not THAT bad. If you have a decent enough CPU, unticking that hardware option (first image) will remove the smurf effects and you can play 1080p with no issues.

About the future of Flash:

Pepper might be an open API, but the flash plugin itself (thats a proprietary piece of work) will be bundled with Chrome.

So, you are a developer of an open (or not so open) source browser on Linux. You implement the Pepper API. But you will lack the reason d'etre of it: the flash plugin itself. Adobe+Google surely signed some agreement over the IP that goes into the Flash Plugin so it will not be possible to publish it freely ONLY if Google or Adobe or both decides to do so.
So, until then you can have all the pepper API implementation and you would still require the installation of Chrome or at least the libpepflashplayer.so file from the installer.

PS: I have Google Chrome dev version installed. Once i verified th eplugins and saw that there is a /opt/google/chrome/PepperFlash/libpepflashplayer.so file instead of libgcflashplayer.so in the plugin list.
I disabled the locally installed flash plugin and this pepper thing worked (with smurfs and all).
Then i linked the pepper plugin to ~/.mozilla/plugins/, fired up Chromium, but the plugin, although it appeared in the plugin list, had nothing besides its name and it did not work. I use the latest buildbot builds of Chromium that is updated quite a few times every day so there is something fishy with the pepper flash support - it seems to be implemented only in Chrome.
The next day i wanted to do some more testing, but as Chrome was updated, the pepper plugin vanished and the old NPAPI one came back.

[paulie-m]

I installed flash 11.2.202.228 today and all my browseres stopped playing flash.I looked through various forums for advice but only one worked. Reinstall flash 11.1.102.63 (available from adobe archives). All was well after that. P.S. I have nVidia card, but had exactly the same trouble on my other PC which has Intel graphics chipset and same solution worked on this.

[gradinaruvasile]

I installed flash 11.2.202.228 today and all my browseres stopped playing flash.I looked through various forums for advice but only one worked. Reinstall flash 11.1.102.63 (available from adobe archives). All was well after that. P.S. I have nVidia card, but had exactly the same trouble on my other PC which has Intel graphics chipset and same solution worked on this.

That might be some other issue.

Flash player is in fact a single .so file (dll equivalent): libflashplayer.so or whatever the packagers rename it (flash-mozilla.so). The installed .debs put the .so file in /usr/lib/mozilla/plugins/ folder and create some symlinks.
But as user you can copy/link the plugin's .so file in the ~/.mozilla/plugins/ folder, it will be picked up by the browsers aswell.
You can have more than 1 instance of the flash player, typically this is the issue. You can check in any browser the "about:plugins" page to see how many instances you have. You can have more than one and have no issues if you disable all but one.

[paulie-m]

I did have to copy the .so file into /usr/lib..etc after downloading from adobe archives. Previously I had tried the same with with a .so file from version 11.2.202.228 and that did not worked.Before downgrading I installed gnash and used galternatives to select that as my default flash player.What a load of rubbish!! It's a terrible flash player. That's when I downloaded older 11.1.102.63 version,copied over the .so file and all my browsers are happy again (and me too).

[bdlandry]

FYI: If you are using Vuze, this problem also causes it to crash when you do a search, then click on a search result and open the search page to download.

The fix of downgrading libflashplayer.so fixes this problem as well.

in 11.10 I replaced the libflashplayer.so in /usr/lib/flashplugin-installer with the older version from:

http://fpdownload.macromedia.com/get...63_archive.zip

[lovinglinux]

NPS: I have Google Chrome dev version installed. Once i verified th eplugins and saw that there is a /opt/google/chrome/PepperFlash/libpepflashplayer.so file instead of libgcflashplayer.so in the plugin list.
I disabled the locally installed flash plugin and this pepper thing worked (with smurfs and all).
Then i linked the pepper plugin to ~/.mozilla/plugins/, fired up Chromium, but the plugin, although it appeared in the plugin list, had nothing besides its name and it did not work. I use the latest buildbot builds of Chromium that is updated quite a few times every day so there is something fishy with the pepper flash support - it seems to be implemented only in Chrome.
The next day i wanted to do some more testing, but as Chrome was updated, the pepper plugin vanished and the old NPAPI one came back.

I have noticed a PepperFlash folder inside stable Chrome's profile directory as well. But it is empty. I guess they experimenting.

Okay. Another squeeze to eliminate competition and to get everyone to "buy" into specific new technologies and hardwares. Firefox is pretty much dead without flash support unless flash is going to be replaced. What's the roadmap here?

Firefox is not dead because this only affects the Linux version, but I agree it looks like this was a moove by Google to force Pepper adoption.

That might be some other issue.

Flash player is in fact a single .so file (dll equivalent): libflashplayer.so or whatever the packagers rename it (flash-mozilla.so). The installed .debs put the .so file in /usr/lib/mozilla/plugins/ folder and create some symlinks.
But as user you can copy/link the plugin's .so file in the ~/.mozilla/plugins/ folder, it will be picked up by the browsers aswell.
You can have more than 1 instance of the flash player, typically this is the issue. You can check in any browser the "aboutlugins" page to see how many instances you have. You can have more than one and have no issues if you disable all but one.

I have Intel chipset and I am using 11.2.202.228 without issues. But a have seen reports from non-nVidia users that lost flash after the update to 11.2.202.228, even with AMD.

FYI: If you are using Vuze, this problem also causes it to crash when you do a search, then click on a search result and open the search page to download.

The fix of downgrading libflashplayer.so fixes this problem as well.

in 11.10 I replaced the libflashplayer.so in /usr/lib/flashplugin-installer with the older version from:

Please read the first post. Instead of downloading the 170Mb you suggested,I have provided the Linux packages you find inside that file and also instructions where to put the file. If you are installing for yourself, the best location is ~/.mozilla/plugins.

[EgoGratis]

I used and recommend Flash-Aid since i can remember and the addon exist. Thanks.

But i must say i am against recommending downgrading Flash to previous versions of Flash and against mentioning this option. I do understand this solves some issues for some users BUT at the same time it opens known security holes for them?

This is just not an option and for users that have problems with Flash and won't use Chrome only two options exist:

1.) Adobe fixes Flash problems.
2.) There is no Flash anymore for Linux users that don't want to use Chrome and have problems with latest Flash.

I don't see other options right now for users that have problems with latest Flash and none of the "workarounds" work for them with latest Flash version.

Running software that has "web access" and known security holes is just not an option and therefore downgrading Flash should not be mentioned at all as it's not the solution for the problem as it only creates way larger security problems!