Flash plugin

flash-player-propertiesLatest Adobe Flash plugin package for supported Fedora and RHEL/CentOS distributions.

Package information

This package tries to comply as maximum to the Fedora Packaging Guidelines; this means the packages has debuginfo packages, default Fedora’s GCC compile time options (where possible) and standard locations for binaries, data and docs.


  • Separate Control Center integration package for the native architecture (64 bit/32 bit).
  • No copying of the plugin around the filesystem after the package is installed; installation in the original Adobe package is all done in %post section!
  • 32 bit plugin can also be installed along the 64 bit one in a 64 bit environment; this is useful for example with the 32 bit Steam client or 32 bit browsers.

Supported distributions:

  • Fedora 23 – i686/x86_64
  • Fedora 24 – i686/x86_64
  • RHEL/CentOS 6 – i686/x86_64
  • RHEL/CentOS 7 – x86_64


To install the repository on a supported Fedora 22+ distribution, run as root the following command:

# dnf config-manager --add-repo=http://negativo17.org/repos/fedora-flash-plugin.repo

For installation on CentOS and Redhat Enterprise Linux:

# yum-config-manager --add-repo=http://negativo17.org/repos/epel-flash-plugin.repo

Then, to install the plugin, perform the following commands:

# yum -y install flash-plugin
# setsebool -P unconfined_mozilla_plugin_transition=off

If you are on a 64 bit system and would like to have the 32 bit plugin as well, launch the following command:

# yum -y install flash-plugin.i686

For the control center, install the flash-plugin-properties package.


Just open an issue to the specific package on Github.

16 thoughts on “Flash plugin

  1. Hi

    Are you sure that you packaged http://www.adobe.com/software/flash/about/ says 11,2,202,491 installed

    I can find only one string “508” with ghex /usr/lib64/mozilla/plugins/libflashplayer.so. But a lot of strings “491”!

    Please recheck latest Adobe Flash plugin package.

    May be I have a problem with migration from yum to dnf.
    flash-plugin- found in DNFDB; skipping with “dnf-2 migrate”

    What is it? An error in packaging? Or in migration to dnf?


  2. dnf info flash-plugin
    Last metadata expiration check: 0:02:36 ago on Thu Mar 24 16:54:34 2016.
    Installierte Pakete
    Name : flash-plugin
    Arch : x86_64
    Epoch : 1
    Version :
    Release : 1.fc23
    Größe : 18 M
    Paketquelle : @System
    Aus Paketqu : fedora-flash-plugin

    Firefox about:addons and https://helpx.adobe.com/de/flash-player.html
    says it is only and blocks flash.

    What is wrong?


    1. My mistake, fixed build coming. I mismatched tarballs, as they always have the same name.
      New builds coming in minutes.

      1. You do it manually?

        Why not automate it with scripts? Bash, LUA, Ruby, Python, Perl …..

        As I unterstand it is a an ordinary process, always the same. Fetching the tarballs etc. ……

        Are you doing all yr packetizing work manually? Why not develop an enigne for this?

        Are Fedora package maintainers doing it all manually?

  3. No, I have it automated, but the tarballs for Flash Plugin always have the same name and there is no versioning in the files; so even if you automate it you need to make sure that the tarballs are deleted and new hashes for them are set.

    I’m reorganizing things up a bit (takes time, and I don’t have much) to have private instances of COPR and Pagure as I’m not allowed to use Fedora’s own COPR and Koji to build non-free packages.

    1. Nothing wrong with the automation. The package is not “generated” as soon as Adobe is releasing a new version, but rather when I’m updating the git part of it, like in Fedora or any other project:


      Feel free to create merge requests for the packages. I’m updating it today, btw.

Leave a Reply