Pepper flash plugin linux

How to install Pepper Flash on Ubuntu

Content on some websites like animations, videos, and games need flash player to be installed and running on your browser. Flash player enables your web browser to run multimedia content. For chrome users, Flash player is already installed but if you are a chromium user, you will need to manually install it. There are many flash players available, but for today’s article, we will use Pepper Flash that is maintained by Google and it is newer than the Adobe Flash player. Pepper Flash is available for both chrome and chromium browsers, but it does not work directly for Firefox. To use it for Firefox, it requires to install an additional package.

In this article, we will see how to install pepper flash for chromium and Firefox browsers. It is really easy to do so let’s get started.

We will use Ubuntu 18.04 LTS OS for describing the procedure mentioned in this article.

Installing Pepper Flash on Ubuntu

Follow the below steps to install Pepper Flash player on Ubuntu 18.04 LTS.

Step 1: Adding the Canonical Partner repository

Pepper Flash plugin is maintained by Canonical Partners repository. We will need to add its PPA to our system repository. For that, open the Terminal by using Ctrl+Alt+T key shortcut, then run the following command as sudo in Terminal:

When prompted for the password, enter sudo password.

Step 2: Update package manager

Now, we will need to update our apt package manager with the new Canonical Partners repository. Run the following command as sudo in Terminal to update apt repositories:

Step 3: Install Pepper Flash for Chromium browser

After adding and update the repositories, run the following command in Terminal as sudo to install the Pepper Flash:

To keep the Pepper Flash up to date, run the following command as sudo in terminal:

Advertisement

Step 4: Allow Flash in browser

When the installation is completed, you will need to make sure that the Flash payer is allowed in your chromium browser. Open the browser, and enter the following address in the address bar of your browser.

Then switch on the toggle Ask first (recommended).

Now restart your chromium browser for changes to take effect.

Installing Pepper Flash for Firefox browser

To use Pepper Flash on Firefox, we will need to install browser-plugin-freshplayer-pepperflash. For that run the following command as sudo in Terminal:

To view the version of Pepper Flash you are using, run the following command in terminal:

That is how easy it is to install Pepper Flash Player for chromium and Firefox on Ubuntu 18.04 LTS. Now you can enjoy the videos, games and interactive web content on your browser.

Karim Buzdar

About the Author: Karim Buzdar holds a degree in telecommunication engineering and holds several sysadmin certifications. As an IT engineer and technical author, he writes for various web sites. You can reach Karim on LinkedIn

Источник

Установка Flash Plugin на Opera (Pepper Flash Plugin)

Некоторое время назад Opera прекратила поддержку полюбившейся всем 12-й версии и создала очередной клон Chromium.
Это создало (помимо прочих) две проблемы:
1. В Chromium нет встроенного Flash Plugin (есть только в Chrome).
2. Поиск по запросу «Flash Plugin на Opera», как и справка Opera дают советы, относящиеся к той, старой Opera.

Я напишу, наверное, единственную в рунете инструкцию по установке Flash Plugin на новую Opera.
Компания Adobe не любит Linux и уже давно отказалась выпускать для него обновленные версии Flash Plugin.
На помощь нам пришла компания Google, выпускающая свою версию, названную PepperFlash Plugin.
Но в ноябре 2016 и Google прекратила поддержку Flash-плагина для Linux.
Теперь остаётся пользоваться «костылём», т. е. версией плагина без номера с сайта Adobe. Установку придётся делать вручную и будет ли это плагин обновляться — никто не гарантирует.
Порядок действий следующий:
1. Скачиваем плагин с сайта Adobe (выбираем «Download the Flash Player Plugin content debugger (64-bit) — PPAPI»).
2. Извлекаем из него файл библиотеки libpepflashplayer.so
3. Помещаем его в папку /usr/lib/pepperflashplugin-nonfree/
(Яндекс ещё советует попробовать папку /usr/lib/PepperFlash/, но мне не понадобилось).
4. Перезапускаем Opera.

Можно попробовать скачать другую библиотеку из репозитория Ubuntu. В этом архиве библиотека имеет другое имя — придётся переименовать, но есть надежда, что в этом репозитории библиотека будет обновляться. Работоспособность не проверял.

Лирическое отступление
Это и правильно, с таким громоздким, полным ошибок проприетарным монстром ни сайт, ни браузер не возьмут в будущее. Но, к сожалению, есть сайты, ещё не успевшие уйти с Flash и даже такие, которые сделали сделали недавно полный апгрейд сайта и он на Flash! Пример: 101.ru — веб-дизайнеры и аудио-программисты как будто работают в разных эпохах. С одной стороны, прорывной адаптивный дизайн под любую ширину экрана, а с другой, аудио на Flash, т. е. привет из XX века.
Если проверить версию плагина через opera://plugins — получим 9999, т. е. натуральный «костыль», чтобы обойти проверку версии в браузерах. Теперь ни Adobe, ни Google не гарантирует безопасность плагина. Т. о., выбор разумного человека — обходиться без установки Flash.

Теперь можно не использовать инструкцию из официальной документации Ubuntu (вместо удаления текста сделаю его зачеркнутым):

sudo apt-get install pepperflashplugin-nonfree
sudo update-pepperflashplugin-nonfree —install

Появится нужная нам библиотека

Можно запускать Opera и проверять.
Если же видео по прежнему не воспроизводится, а в списке плагинов: opera://plugins нет Adobe Flash Player ищем в папке с установленной Opera обнаруживаем файл с названием, очень напоминающим наш плагин
/usr/lib/x86_64-linux-gnu/opera/resource s/pepper_flash_config.json

Открываем этот файл и ищем — есть ли в нём путь к установленной библиотеке
/usr/lib/pepflashplugin-installer/libpep flashplayer.so?
Если нет — вписываем, не забывая поставить запятую после пути.

Недавно обнаружилась ещё одна проблема: после обновления версии Opera начинает проверять установленную версию Flash Plugin и отказывается запускать устаревшие версии. Иногда помогает повторный запуск
sudo update-pepperflashplugin-nonfree —install
но не всегда.
Тогда придётся выкачивать файл со свежей версией плагина прямо из репозитория и устанавливать.

Источник

PepperFlash в Chromium

Как известно, разработчики Adobe прекратили развитие и обновление Flash-плагина под GNU/Linux. Однако, команда разработчиков Google Chrome взяла на себя продолжение разработки данного плагина, и получается это у них лучше, чем у Adobe, и распространяют его в составе готового пакета своего браузера.

Adobe возобновила выпуск Flash plugin для Linux в формате NPAPI последних версий:

Но и пользователям браузера Chromium можно использовать эту версию плагина, если использовать именно Chrome по какой-то причине не получается. Для этого нужно или установить пакет или самостоятельно вручную получить файл плагина.

Содержание

Установка с помощью пакета для Chromium [ править ]

При наличии сети установите пакет chromium-pepperflash :

При его установке входящая в него утилита /usr/sbin/update-pepperflash загрузит последнюю версию Google Chrome и распакует оттуда плагин. При удалении пакета скачанный RPM с Google Chrome и плагин будут удалены из системы.

Если что-то не срабатывает, установите пакет и запустите скрипт вручную:

Использование PepperFlash в Firefox [ править ]

Можно использовать PepperFlash и в браузерах, использующих NPAPI. Для этого необходимо (помимо собственно chromium-pepperflash ) установить пакет freshplayerplugin и, если используется Firefox, удалить пакет mozilla-plugin-adobe-flash :

После этого перезапустите браузер.

Установка вручную [ править ]

1. Cкачиваем официальный пакет браузера Chome. Там выбираем rpm-пакет, 32 бита или 64 — смотря у кого какая платформа.

2. Из скачанного пакета RPM вытаскиваем (предполагается, что все в курсе, что mc спокойно входит в rpm-пакет как в обычный архив) сам плагин libpepflashplayer.so , который прячется там по пути /opt/google/chrome/PepperFlash/ .

3. Вытащенный оттуда плагин кладем в /usr/lib/pepper-plugins/ (или в /usr/lib64/pepper-plugins/ , если система 64-битная).

4. Далее необходимо отредактировать файл /etc/chromium/default , находим там строку

и дописываем параметры запуска с Pepper Flash. В итоге, эта строка должна выглядеть так:

для 32-битных систем и

для 64-битных систем.

Нужно указать правильную версию Flash’а в команде. Для этого перейдите в директорию /opt/google/chrome/PepperFlash, откройте файл manifest.json и там посмотрите точную версию плеера.

5. Перезапускаем chromium и получаем Pepper Flash вместо Adobe Flash.

Использование PepperFlash решает проблему жуткой каши на месте многих флеш-вставок на сайтах, снижение нагрузки на процессор. Также зафиксировано улучшение качества картинки онлайн-видео на некоторых бортовых видеокартах.

Источник

nathanael-naeri / flash-readme.md

Date: 2017-04-23
Title: Flash and LSO cookies
Author: Nathanaël Naeri

Valid for: Ubuntu 14.04+
Valid for: NPAPI and PPAPI Flash Player (plugins) 25.0
Valid for: Fresh Player Plugin (wrapper) 0.3.6

Flash Player on Linux

There are two Flash Player plugins available for Linux: one that uses the legacy Netscape Plugin API (NPAPI) to interface with the browser [1], and another that uses the more modern Pepper API (PPAPI) instead [2,3].

Chromium and Chrome only support the Pepper API to interface with plugins, and can therefore only use the PPAPI Flash plugin. Firefox only supports the Netscape Plugin API, and only for the NPAPI Flash plugin since version 52: support for all other plugins has been dropped, as the web moves away from plugins [4]. Mozilla is exploring the possibility to use the Pepper API for Flash in the future [5], but they may just drop all Flash support instead.

To complicate the matter, a PPAPI-to-NPAPI wrapper (converter) exists that makes it possible for the PPAPI plugin to present to NPAPI-compatible browsers as a NPAPI plugin [6]. This piece of software was designed because Adobe stopped developing the NPAPI plugin for Linux from 2011 to 2016, focusing instead on the PPAPI plugin. With the NPAPI plugin stuck at version 11.2, it became desirable for Linux users of NPAPI-compatible browsers to be able to use the PPAPI plugin through the PPAPI-to-NPAPI wrapper. The reverse wrapper, NPAPI-to-PPAPI, does not exist.

The NPAPI and PPAPI plugins are not exactly the same, and certain features are not fully implemented in the NPAPI version, such as GPU acceleration of 3D graphics [7]. To enjoy these features, it is necessary to use the PPAPI plugin through the PPAPI-to-NPAPI wrapper. If doing so, note that the version number reported by the wrapper in about:plugins might be wrong [8,9,10]: check with www.adobe.com/software/flash/about instead.

Both the NPAPI plugin and the PPAPI plugin are binary files, named respectively libflashplayer.so and libpepflashplayer.so, that can be downloaded from Adobe [11,12] and placed manually in a browser-specific location for the browser to find them. The PPAPI-to-NPAPI wrapper is another binary file, named libfreshwrapper-flashplayer.so, whose sources can be downloaded from the developer’s page [6] and the compiled binary can be placed in the same browser-specific location. Several packages provide the plugin and the wrapper and automate their installation:

Recommended sources for the NPAPI and PPAPI plugins

When installing a new Ubuntu 14.04+ system, selecting the option about non-free software installs flashplugin-installer as a recommended dependency of ubuntu-restricted-addons [13,14,15].

The package downloads the adobe-flashplugin source package from Canonical’s partner repository [19], which is a tarball archive containing the NPAPI plugin, the PPAPI plugin, and the control panel (name: adobe-flashplugin_ .orig.tar.gz). The package then extracts the NPAPI plugin to /usr/lib/flashplugin-installer/libflashplayer.so, and creates a symlink to it in the Mozilla plugin directory: /usr/lib/mozilla/plugins/flashplugin-alternative.so -> /etc/alternatives/mozilla-flashplugin -> /usr/lib/flashplugin-installer/libflashplayer.so.

The PPAPI plugin and the control panel are not installed.

To get the PPAPI plugin instead of (or in addition to) the NPAPI plugin provided by flashplugin-installer, remove flashplugin-installer and install adobe-flashplugin from Canonical’s partner repository [16,17,18,19].

Then install the PPAPI/NPAPI wrapper too (see further), so that NPAPI-compatible browsers can detect the PPAPI plugin in addition to the NPAPI one. If both versions show up in about:addons (which shouldn’t be the case), don’t try and disable the NPAPI one: you can’t tell it from the PPAPI one by the version number, and disabling a version also disables the other.

The adobe-flash-properties- package is installed as a recommended dependency of adobe-flashplugin: I don’t know if it is the control panel for the NPAPI plugin, the PPAPI plugin, or both. There is nothing interesting in it anyway.

Previously recommended source for the PPAPI plugin

Debian users are not supposed to use Canonical’s partner repository, but instead use pepperflashplugin-nonfree as their source for the PPAPI plugin [20,21]. This Debian package made by Bart Martens is automatically imported into Ubuntu at each development cycle [22,23], but doesn’t have a specific Ubuntu maintainer, and has been requested for removal from Ubuntu 17.10+ [44].

Ubuntu users may use it as their source for the PPAPI plugin, but it is not recommended over adobe-flashplugin. Available in multiverse, the package downloads the PPAPI plugin from Adobe, installs it as /usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so, and writes the path to it in a config file in /etc/chromium-browser/customizations (16.04+) or /etc/chromium/default (14.04) so that Chromium-based browsers can find it. After the PPAPI/NPAPI wrapper is installed (see further), NPAPI-compatible browsers are able to detect it too.

In the early days of the PPAPI plugin, the plugin was only available to Google, and the only way of getting it on Linux was to rip it from a download of Google Chrome (which comes as a .deb package). This is what pepperflashplugin-nonfree used to do. Now Adobe has made the Linux PPAPI plugin available to Canonical and on their own download site, and Google has unbundled it from Chrome since Chrome version 54, released in late 2016-10 [24]. Versions of pepperflashplugin-nonfree that have taken this change into account are in in for 17.04+ and in -updates for previous releases.

The advantage of pepperflashplugin-nonfree is that it doesn’t install the NPAPI plugin and the control panel, so no bloat if you’re only after the PPAPI plugin. Also, it is in multiverse which is enabled by default, if for some reason you don’t want to enable partner. The drawback is that its version is not bumped when a new Flash Player plugin is released [21], so Flash Player updates cannot be done via APT and must be done manually. A standalone script is provided for that task, which redownloads the plugin [25]:

Jonathon Fernyhough’s PPA features a version of this package that also downloads the PPAPI plugin from Adobe, is compiled for 14.04 and 16.04, and automates the Flash Player updates via a daily cronjob [26]. I’d recommend it over the multiverse version for these releases.

The PPAPI-to-NPAPI wrapper

The PPAPI/NPAPI wrapper is named Fresh Player Plugin, because even though it is not the (PPAPI) Flash plugin itself, it is a (NPAPI) plugin to the browser, installed as a binary file in the Mozilla plugin directory (libfreshwrapper-flashplayer.so). It is developped by Rinat Ibragimov [6,27] and packaged for Debian and Ubuntu as browser-plugin-freshplayer-pepperflash (src:freshplayerplugin) by several different maintainers.

Vincent Danjean is the maintainer of the Debian package [28]. This package is imported in Ubuntu’s multiverse repository [29,30], starting with 16.04, as part of the regular Debian package import at the beginning of the development cycle of each Ubuntu release. The resulting Ubuntu package doesn’t have a specific Ubuntu maintainer.

The Debian package recommends pepperflashplugin-nonfree, Debian’s sole source for the PPAPI Flash plugin. Its Ubuntu version was modified [31] to recommend adobe-flashplugin instead, Ubuntu’s recommended source for the PPAPI Flash plugin.

The package adds an alternative to the mozilla-flashplugin group, changing the symlink chain pointing to adobe-flashplugin’s NPAPI plugin (/usr/lib/mozilla/plugins/flashplugin-alternative.so -> /etc/alternatives/mozilla-flashplugin -> /usr/lib/adobe-flashplugin/libflashplayer.so) to a symlink chain pointing to the PPAPI/NPAPI wrapper (/usr/lib/mozilla/plugins/flashplugin-alternative.so -> /etc/alternatives/mozilla-flashplugin -> /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so). This is how Mozilla-based browsers are able to find the wrapper. As for the wrapper itself, it finds the PPAPI plugin it is supposed to wrap by looking for it in several locations where the plugin is usually installed [36].

Like all packages imported from Debian, new versions of browser-plugin-freshplayer-pepperflash only land in Ubuntu’s development release (and not even automatically, since there is a Debian/Ubuntu delta). For the package to be updated in Ubuntu’s published releases, a MOTU needs to take specific action, which rarely happens (the packages in the repository of a published release are updated as little as possible, for stability reasons). Hence why browser-plugin-freshplayer-pepperflash is outdated in the published releases.

Andrei Alin is the maintainer of the package available in the WebUpd8 PPA [32,33]. In contrast to the package available in multiverse, Andrei Alin’s package is updated for all published releases, whenever new upstream releases are available.

The package recommends adobe-flashplugin and adds the same alternative as the package available in multiverse.

Jonathon Fernyhough’s PPA provides versions of browser-plugin-freshplayer-pepperflash for 14.04 and 16.04 that are backports of the 17.04 multiverse version [26]. Mere copies, no changes.

This may be useful for users of 14.04, since browser-plugin-freshplayer-pepperflash is not present in multiverse for that release (no backport has ever been requested). Users of 16.04 will also get a small version bump from using this PPA. In both cases however, Andrei Alin’s package is more recent.

Giovanni Santini’s PPA provides daily builds of the Fresh Player Plugin for all published releases and the development release [34]. It is useful when you need an upstream bugfix, can’t wait for the next packaged release, and don’t feel like installing from source. Note that the PPA is currently lagging behind upstream because of a Github-to-Launchpad importation error [35].

Note that Giovanni Santini follows the Debian packaging rather than the Ubuntu packaging: it recommends pepperflashplugin-nonfree instead of adobe-flashplugin, and creates a new alternative group to symlink to the wrapper instead of using the one already put in place by adobe-flashplugin.

Installation and configuration

The command for adding a PPA to the system is sudo add-apt-repository ppa: /

The wrapper must know the location of the PPAPI plugin it is supposed to wrap. By default, it looks for a file named libpepflashplayer.so in a dozen different directories, where Chrome and the previously listed packages providing the PPAPI plugin would have put it. Among those are [36,37]:

If the plugin has been installed manually in a different place, or given a different name, its path must be given explicitly in the configuration file /etc/freshwrapper.conf (site-specific) or

See the example configuration file /usr/share/doc/browser-plugin-freshplayer-pepperflash/freshwrapper.conf.example [38] for more configuration options. It shows the default values.

Local shared objects aka Flash cookies

Storage locations: NPAPI

The NPAPI plugin stores the LSO cookies in the following locations [39]:

The default Flash cookie is stored as:

Storage locations: PPAPI

The PPAPI plugin stores the LSO cookies in

/.config/google-chrome/Default/Pepper Data/Shockwave Flash/WritableRoot/#SharedObjects/ when it is used through Google Chrome [39], and in the following location when it is wrapped by Fresh Player Plugin:

The default Flash cookie is stored as:

Clear cookies when Firefox closes

The «Keep until I close Firefox» cookie setting apparently only applies to text cookies, not LSO cookies. If ticked:

The «Clear history when Firefox closes» preference and «Clear recent history» command have a cookie tickbox that apparently applies to both text and LSO cookies, and doesn’t care about exceptions. If ticked:

The LSO cookies in the PPAPI location (

/.config/freshwrapper-data/. ) are left untouched, along with the corresponding default Flash cookie, since Firefox doesn’t know about PPAPI plugins. To delete these LSO cookies, use BetterPrivacy [40].

Install BetterPrivacy Firefox addon to automatically delete PPAPI LSO cookies

By default, BetterPrivacy looks for LSO cookies under

/.macromedia (NPAPI location). Configure it to look under

/.config/freshwrapper-data (PPAPI location). By default, the default Flash cookie is neither cleared nor deleted, but there is an option to delete it as well.

The NPAPI storage location may be deleted manually once and for all (rm -r

/.macromedia), since once the wrapper is installed, the PPAPI plugin will be used, not the NPAPI plugin, so there won’t be any new files created in the NPAPI location.

Exception: if the wrapper is from Giovanni Santini’s PPA, Firefox detects two Flash plugins: PPAPI through the wrapper, and NPAPI, because the package installs a new alternative group to symlink to the wrapper (flash-mozilla.so), instead of using the one that adobe-flashplugin has already put in place to symlink to the NPAPI plugin (mozilla-flashplugin). Because of that, an empty .macromedia/Flash_Player/macromedia.com/support/flashplayer/sys/settings.sol is created when Firefox tries to clear the default Flash cookie. Oh well.

In case of Flash-related trouble, check the Issues page of the wrapper on GitHub [41]. Answers will probably be there.

Hardware accelerated video decoding

Current defaults are for hardware accelerated rendering to be enabled (enable_3d = 1) and hardware accelerated decoding to be disabled (enable_hwdec = 0), said hardware being the GPU of course [38,42].

Version >=54.39.0 of libavcodec is required for compiling the wrapper with hardware accelerated decoding support. But Ubuntu 14.04 only has version 54.35.1, so the WebUpd8 packager (Andrei Alin) compiled the wrapper without hardware accelerated decoding support, because even if he updates his libavcodec, the users of the package can’t be expected to have done so [42]. Consequently, switching on hardware accelerated decoding in the configuration file is useless on 14.04, it is not available.

Later releases of Ubuntu have version 56+ of libavcodec, so the wrapper for these releases has most likely been compiled with hardware accelerated decoding support. To turn it on, switch enable_hwdec to 1 in the wrapper’s configuration file, and check that enable_vaapi and enable_vdpau are also set to 1 so that hardware accelerated decoding uses VA-API/VDPAU.

The WebUpd8 team maintains other interesting PPAs [43]:

Источник