Hello everyone, in our mail have been asked several questions that make me see that there is some confusion in the nomenclature of packages and architecture (32 and 64 bits). I will try to explain in detail the installation and uninstallation of the plugin, in addition to offering free alternatives.
Tested on all versions of Ubuntu with support currently (12.04, 12.10, 13.04, 13.10 and 14.04 and others) and for both architectures (32 and 64 bits).
Table of Contents
In Ubuntu, the package to install Flash Player is ” flashplugin-installer “:
Sudo apt-get install flashplugin-installer
Restart the browser and confirm that you have it installed at:
Note : It is not necessary to click on the browser when you notify us that the plugin is missing, add a repository, or download a .deb from the page Official Adobe or other, or anything. Everything goes to the same plugin / version of Flash Player and the only thing that we will get is to make a mess or worse, to liar to the system.
Nomenclature of packages:
As I see that there is a small mess between the nomenclature of the packages, I will specify them:
|Metapaquetes that contain the installation of Flash, in addition to other installations with restricted licenses of copyright:|
|Ubuntu-restricted-extras||It contains the “flashplugin-installer”|
|Non-free-codecs||Obsolete package that was in the Medibuntu repositories and contained the “ubuntu-restricted-extras”, which in turn contained the “flashplugin-installer”|
|Packages related to the installation of Flash Player:|
|Flashplugin-nonfree||This is the old package that installed Flash. In Ubuntu, it is already deprecated and in some versions it is kept in the repositories by compatibility theme, but it is an empty package that redirects to flashplugin-installer|
|Flashplugin-installer||This is the package that currently install Flash Player on Ubuntu. It does not contain the plugin, but provides an installer that will detect the system architecture and download and install the plugin|
|Adobe-flashplugin||This is the package that will be downloaded to install Adobe Flash Player, from partner repositories (canonical partners)|
Note: It is not necessary to activate, nor add the partner repositories (canonical partners).
Since the installer “flashplugin-installer” always, whether or not the repositories are activated, redirects the download to the “adobe-flashplugin.orig.tar.gz” of that page:
As you can see in the page the latest version is 17.04.1 and the package that will install will be the last one in the list:
You can check it perfectly since The terminal (that thing so rare). Having deactivated partner repositories:
Kaos1304 @ kaos: ~ $ sudo apt-get install flashplugin-installer ... Selecting the previously uninstalled flashplugin-installer package. (Reading the database ... 322574 files or directories currently installed.) Unpacking flashplugin-installer (from ... / flashplugin-installer_20170616.1ubuntu0.13.04.1_amd64.deb ) ... Processing triggers for update-notifier-common ... Flashplugin-installer: downloading http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20170616.1.orig.tar.gz Installing from local file /tmp/tmpiRlygJ.gz Flash Plugin installed. Configuring flashplugin-installer (20170616.1ubuntu0.13.04.1) ... Kaos1210 @ kaos: ~ $
We can also download that package to extract it (right click> extract here) and check that it brings the plugin for 32bit (i386) and 64bit (amd64):
Kaos1304 @ kaos: ~ $ ls adobe-flashplugin-20170616.1 Amd64 i386 Kaos1304 @ kaos: ~ $ ls adobe-flashplugin-20170616.1 / amd64 Libflashplayer.so readme.txt usr Kaos1304 @ kaos: ~ $ ls adobe-flashplugin-20170616.1 / amd64 / usr Bin lib lib64 share Kaos1304 @ kaos: ~ $
One of the most common problems is to mix / repeat installations and when problems occur, it is best to uninstall everything related to Flash, including other applications:
Sudo apt-get purge flashplugin-nonfree flashplugin-installer adobe-flashplugin gnash gnash-common mozilla-plugin-gnash swfdec-mozilla
Sudo rm -f /usr/lib/firefox-addons/plugins/libflashplayer.so
Sudo rm -f /usr/lib/mozilla/plugins/libflashplayer.so
Sudo rm -f /usr/lib/mozilla/plugins/flashplugin-alternative.so
Sudo rm -f / usr / lib / mozilla / plugins / npwrapper * flash * so
Rm -f ~ / .mozilla / plugins / * flash * so
Reinstall it with a simple:
Sudo apt-get install flashplugin-installer
And restart the browser
Adobe and its Flash Player
The support that gives Adobe to GNU / Linux, is very bad, compared to the one that gives the dark side and that has to be assumed. It is what there is and no matter how much we pataleemos we will not have more or better, since Adobe, in its day, brake dry and will not release new versions for GNU / Linux, although that yes, we will continue to have security updates (would be missing more ).
Alternatives to Adobe Flash Player:
If Adobe and / or your Flash Player touches the “balls”, there are enough free alternatives, depending on which cases:
Gnash : is based on GameSWF, and supports most of the features of SWF v7 and some SWF v8 and v9. However it does not support SWF v10, so the more complicated Flash web pages can not open them. Installation:
Sudo apt-get install gnash mozilla-plugin-gnash
LightSpark : It is written in C ++ / C and runs under GNU / Linux. Its goal is to support the new Adobe Flash formats and the AVM2 virtual machine. It’s the same as Gnash.
HTML5 : It is the future of the Web and little by little is being implemented. Many of the largest audio-visual content pages are giving you the opportunity to use HTML5 instead of Flash. An example is Youtube.
To view YouTube videos in HTML5, open the following page:
Not all videos will be able to be seen in HTML5, due to the codecs that have been used to create them and / or upload them to the Web, but this is another topic and very long.
Install Gnash and Flash Player together to select one or the other as needed:
Added: For those who are interested in working in Firefox, Chromium and SWare Iron browsers with Gnash by default and using Flash Player on the occasions when Gnash can not play the Flash content, you can follow the instructions that I leave in one of the comments Of this topic.