FDS-TEAM
Linux, Windows, Programming and more...
Pipelight - Installation
15 Oct 2013 00:08 CEST  written by FDS-Team - 169 comment(s)
[article-image]

This page contains information about how to install Pipelight on different distributions and how to compile it on your own. The instructions were moved to this separate page so that they can be updated and linked to a bit easier. If you write a blog post / news entry about Pipelight, please keep in mind that Pipelight is still in beta stage and we sometimes need to alter things in a way which might break compatibility with previous installation instructions (like for example multi-plugin support), so please consider linking to this page instead of copying the instructions, thanks.

1. Package Installation

The installation of Pipelight is split into the following steps:

  • Installation of Pipelight itself
  • Optional: Enable/disable specific browser plugins
  • Install a user agent switcher

Even though we introduced multiplugin support recently (not yet supported for all distributions), the Pipelight package itself will enable Silverlight by default. If you don't want to use Silverlight, you can either disable it (might be necessary to repeat this step after every upgrade) or choose a package which doesn't enable plugins automatically.

NOTE: The download and installation of plugins starts the first time when you open about:plugins or visit a page that requires the specific plugin. This can take up to a couple of minutes - please be patient and wait until the installation has finished.

1.1. Ubuntu (Easy)

We have prepared a PPA archive for Ubuntu which provides you with prebuilt binarys and automatic updates. To make the installation as easy as possible, especially for users of the netflix-desktop app, we decided to share the same Wine version with Erich E. Hoovers package, so you don't need to install and update another Wine package. Simply use apt-get to install pipelight and the package system will install all required dependencies.

warning

Warning:

Please note, these instructions have been changed with the release 0.2.3 in order to combine all necessary stuff in one repository. The previous PPAs ppa:mqchael/pipelight and ppa:ehoover/compholio will still work during the next time, but we recommend everyone to switch over to the new one, since we will discontinue this probably in the future. You can remove the older PPAs with the following commands:

sudo add-apt-repository --remove ppa:mqchael/pipelight
sudo add-apt-repository --remove ppa:ehoover/compholio

Additionally with release 0.2.4 the previous package pipelight is also deprecated and no longer mentioned in these installation instructions. Don't worry, it will work nevertheless in the future, but new users should preferably use the pipelight-multi package, since it might become impossible to stay completely backwards compatible in the future.

You just have to type in the following commands in your terminal to add the necessary repository to your system and to install pipelight-multi:

sudo add-apt-repository ppa:pipelight/stable
sudo apt-get update
sudo apt-get install --install-recommends pipelight-multi
sudo pipelight-plugin --update

The installation of pipelight/pipelight-multi will also install the Microsoft core fonts as they are required by Silverlight. If you don't have them yet, you will be asked to accept a license agreement during the installation (Just press TAB and ENTER to accept it). The core fonts package is only available in the multiverse repository, which is enabled by default on newer Ubuntu versions, but if this is not the case for your installation / distribution take a look at this question on how to enable it.

After the installation of pipelight-multi you have to select which plugins you want to use. The next commands illustrates how to enable Silverlight 5.1. If you don't want to use this plugin, simply skip it. More information on how to enable other plugins or how to use a different Silverlight versions is available at the end of the page. After typing the command to enable Silverlight you have to accept the corresponding Silverlight licenses. This was added in Pipelight release 0.2.4 to make it more transparent which licenses a user has to accept to use a specific browser plugin. To accept the license just type Y, if you don't want to accept the license or want to look up the details first type N and redo the command later when you change your decision.

sudo pipelight-plugin --enable silverlight
# Type in 'Y' to accept the license of Silverlight and all required modules

You can optionally enable additional plugins if you want to, just take a look at the post installation steps for more information. The installation of Silverlight (or any other plugin you have selected) takes place when you start your browser for the next time. Please note that you will need to install a user agent switcher for most plugins/pages to get them working.

1.2. Arch Linux (Easy)

There are two ways to install Pipelight on Arch Linux. Please note that we recommend not to mix them. The prebuilt packages depend on each other, so you cannot easily use them individually. Moreover the path where Wine is installed is different between both versions.

1.2.1. Using a repository with prebuilt binaries

We now provide prebuilt packages for Arch Linux in our own repository so that it is no longer required to build Wine on your own. The big advantage of this method is that Wine is installed to a separate location (/opt/wine-compholio) which allows you to keep your regular Wine version installed.

To install the package just add the following entry to your /etc/pacman.conf:

[pipelight]
Server = http://repos.fds-team.de/stable/arch/$arch

As next step you should add our key to your pacman key database to allow verifying the packages. All packages and the repository itself is signed using a 4096 bit RSA key, so that you can set the SigLevel to Required if you like. You can import the key and set the trust level to trusted by using:

sudo pacman-key -r E49CC0415DC2D5CA
sudo pacman-key --lsign-key E49CC0415DC2D5CA

Now you can install Pipelight like any other package using pacman:

sudo pacman -S pipelight

There are currently no plugins enabled by default, so that you can decide on your own which ones you want to use. Take a look at the post installation steps on how to do this. The installation of Silverlight (or any other plugin you have selected) takes place when you start your browser the next time. Please note that you will need to install a user agent switcher for most plugins/pages to get them working.

1.2.2. Using AUR and building from source

Thanks to Anish Bhatt who created the easy to install AUR pipelight, you can now also install Pipelight on Arch Linux without much manual intervention or configuration. If you need more information you can also take a look at the corresponding archlinux pipelight wiki.

Simply use your favorite AUR helper (in this example yaourt) to compile and install Pipelight and all it's dependencies:

yaourt -S pipelight
sudo pipelight-plugin --update

This package is using a different approach than Ubuntu to stay compatible with older versions and enables Silverlight by default. If you don't want to use Silverlight, please execute the following command after the installation to disable it again:

sudo pipelight-plugin --disable silverlight

Similar to Ubuntu you can now enable additional plugins you want to use or disable again. Take a look at the post installation steps on how to do this. The installation of Silverlight (or any other plugin you have selected) takes place when you start your browser the next time. Please note that you will need to install a user agent switcher for most plugins/pages to get them working.

1.3. Debian Wheezy / Jessie / Sid (Easy)

We also provide a repository for current versions of Debian. The installation is a bit more complicated than on Ubuntu, but still easy. As a first step you need to enable the installation of i386 packages, if you are using a 64 bit version of Debian, since the provided Wine version is 32 bit only. Execute the following commands via sudo (if installed) or as root:

sudo dpkg --add-architecture i386

Now you need to import the key of the repository:

Wheezy:

wget http://download.opensuse.org/repositories/home:/DarkPlayer:/Pipelight/Debian_7.0/Release.key
sudo apt-key add Release.key

Jessie/Sid:

wget http://repos.fds-team.de/Release.key
sudo apt-key add Release.key

We are now almost ready to add the repository, but we need the Microsoft fonts packages for some Silverlight applications which are only available in the contrib repository. So you need to open /etc/apt/sources.list and append contrib at the end of each line that begins with deb or deb-src which is a default debian repository. For example example:

# Original line: deb http://ftp.de.debian.org/debian/ wheezy main
deb http://ftp.de.debian.org/debian/ wheezy main contrib

After this step you can include our repository by adding the following repository to your /etc/apt-sources.list file.

Wheezy:

deb http://download.opensuse.org/repositories/home:/DarkPlayer:/Pipelight/Debian_7.0/ ./

Jessie:

deb http://repos.fds-team.de/stable/debian/ jessie main

Sid:

deb http://repos.fds-team.de/stable/debian/ sid main

Update your package cache by executing:

apt-get update

The installation is now the same as on Ubuntu. First install pipelight-multi and afterwards enable the plugins you want to use (in the example below Silverlight, just skip this line if you don't want to use this plugin):

apt-get install pipelight-multi
pipelight-plugin --update

# Afterwards enable some plugins, in this example Silverlight
pipelight-plugin --enable silverlight
# Type in 'Y' to accept the license of Silverlight and all required modules

Similar to Ubuntu you can now enable/disable additional plugins you want to use. Take a look at the post installation steps on how to do this. Silverlight (or any other plugin) should now be installed on the next browser start. Moreover you will need to install a user agent switcher for most of the plugins/pages to get them working.

1.4. openSUSE (Easy)

Thanks to Richard Bos who created packages for openSUSE, you can now install Pipelight without having to configure everything on your own.

To install Pipelight and all its dependencies you have to execute (as root user, for example with sudo):

zypper ar --refresh http://download.opensuse.org/repositories/home:/rbos:/pipelight/<openSUSE version>/home:rbos:pipelight.repo
zypper ref
zypper install pipelight
pipelight-plugin --update

Please put in your specific openSUSE version, packages are currently available for openSUSE_12.2, openSUSE_12.3 and openSUSE_Tumbleweed.

This package is using a different approach than Ubuntu to stay compatible with older versions and enables Silverlight by default. If you don't want to use Silverlight, please execute the following command after the installation to disable it again:

sudo pipelight-plugin --disable silverlight

Similar to Ubuntu you can now enable additional plugins you want to use or disable again. Take a look at the post installation steps on how to do this. The installation of Silverlight (or any other plugin you have selected) takes place when you start your browser the next time. Please note that you will need to install a user agent switcher for most plugins/pages to get them working.

1.5. Fedora 18/19/20 (Easy)

First of all you need to install the Microsoft core fonts which are not part of the normal repositories. They are required to get Silverlight working otherwise the plugin may simply fail to start without any error output. Just execute the following two commands to install them:

sudo yum install cabextract
sudo rpm -i http://sourceforge.net/projects/mscorefonts2/files/rpms/msttcore-fonts-installer-2.6-1.noarch.rpm

Now you only need to add the repository and install Pipelight which can achieved by executing (there are also Fedora 18 and Fedora 20 packages, just replace Fedora_19 with Fedora_18 or Fedora_20)

sudo wget http://download.opensuse.org/repositories/home:/DarkPlayer:/Pipelight/Fedora_19/home:DarkPlayer:Pipelight.repo -O /etc/yum.repos.d/pipelight.repo
sudo yum install pipelight
sudo pipelight-plugin --update

After the installation all plugins are disabled and you must manually enable those you want to use. To enable a plugin you can use the pipelight-plugin script as shown in the following line with Silverlight:

sudo pipelight-plugin --enable silverlight
# Type in 'Y' to accept the license of Silverlight and all required modules

If you already have Wine installed, you need to upgrade your packages, so that you will get our Wine version with all needed patches.

Take a look at the post installation steps for more information about enabling and disabling plugins. The installation of Silverlight (or any other plugin you have selected) takes place when you start your browser the next time. Please note that you will need to install a user agent switcher for most plugins/pages to get them working.

One problem you may come across is that Fedora uses SELinux and browsers are often not allowed to execute external programs which is required for Pipelight to work. For Firefox you can solve this issue by disabling the unconfined_mozilla_plugin_transition check via

sudo setsebool -P unconfined_mozilla_plugin_transition 0

Other Browser might require additional exceptions and you will need to take a look at the SELinux log if Pipelight does not work as expected.

1.6. AVLinux (based on Debian squeeze, Easy)

Quote by AVLinux

AV Linux is a free custom shop modded and rodded 32bit computer Operating System designed to turn a regular old (or fairly new) PC or Intel Mac into an Audio/Graphics/Video workstation appliance. […]

We provide a repository for AVLinux, so that you will get updates automatically without any further interaction. You simply need to import our repository key and add the repository to your sources. All the following commands must be executed as root:

To add the key simply execute:

wget http://repos.fds-team.de/Release.key
apt-key add Release.key

Now you can add the repository by creating a file /etc/apt/sources.list.d/pipelight.list with the following content:

deb http://repos.fds-team.de/stable/debian/ avlinux main

Now everything is set up and you only need to update your package cache so that you can finally install Pipelight.

apt-get update

Simply install the pipelight-multi package and afterwards enable the plugins you want to use (in the example below Silverlight, just skip this line if you don't want to use this plugin):

apt-get install pipelight-multi
pipelight-plugin --update

# Afterwards enable some plugins, in this example Silverlight
pipelight-plugin --enable silverlight
# Type in 'Y' to accept the license of Silverlight and all required modules

Some old versions of AVLinux and/or filesystems might not have enabled XATTR by default, which is required to see DRM protected content. You'll have to look up how to enable it, if streaming pages do not work properly. For all other non-DRM pages this is not necessary.

If you want to enable/disable additional plugins, take a look at the following section. Similar to all other distributions, the installation of Silverlight (or any other selected plugin) takes place when you start the browser the next time. Please note that you will need to install a user agent switcher for most plugins/pages to get them working.

1.7. Slackware (Easy)

It took some time, but now there are also packages available for Slackware users. They were created by Eric Hameleers, who also wrote an excellent article about how to install them and typical pitfalls you may run into on Slackware. Instead of copying the instructions, I decided to simply link to them, so that they can be updated independently and you may also find some of the user comments useful. Simply follow the these instructions.

After you installed the packages you can enable/disable additional plugins like on all other distributions, just take a look at the following section. Please note that you will need to install a user agent switcher for most plugins/pages to get them working.

Moreover please do me a favor and report problems and questions, which are not directly related to Slackware (for example that plugins are installed, but don't work as expected), to our launchpad page or ask them in our IRC channel #pipelight on Freenode. Especially Silverlight is very picky and Eric will most probably not be able to answer all of your questions.

1.8. SteamOS (Easy)

We created a repository providing packages for SteamOS that can be used with a default SteamOS installation. The repository contains some additional dependencies beside Pipelight and Wine which are available in Debian but not in SteamOS so that you do not need to add the original Debian repositories (and maybe get into conflicts). To add the repository and install the required packages, you need to switch to desktop mode and set a password on the desktop user as explained in the SteamOS FAQ.

After switching to desktop mode execute the following commands in a terminal to add the repository:

sudo dpkg --add-architecture i386
wget http://download.opensuse.org/repositories/home:/DarkPlayer:/Pipelight/SteamOS/Release.key
sudo apt-key add Release.key
echo "deb http://download.opensuse.org/repositories/home:/DarkPlayer:/Pipelight/SteamOS/ ./" | sudo tee /etc/apt/sources.list.d/pipelight.list

The next step is to update your apt cache so that you can finally install the Pipelight package and it's dependencies. Use the following command to do this:

sudo apt-get update

The package can now finally installed with the following command:

sudo apt-get -o Dpkg::Options::="--force-overwrite" install pipelight-multi
sudo pipelight-plugin --update

The Dpkg::Options::="--force-overwrite" option is required since the libssl package inside the SteamOS repository is not completely Multiarch ready and the 32 bit version tries to overwrite the changelog of the 64 bit version. Since both versions of the changelog contain the same content and are only provided for informational purposes, they can be safely overwritten.

As usual you can now start enabling plugins like for example Silverlight with the pipelight-plugin script:

sudo pipelight-plugin --enable silverlight
# Type in 'Y' to accept the license of Silverlight and all required modules

The Steam internal browser doesn't seem to use or support NPAPI plugins (yet) and Pipelight can therefore only be used with normal desktop browsers like the preinstalled Iceweasel browser. Pipelight will automatically work with this browser but don't forget to install a user agent switcher otherwise most streaming websites won't work. Just follow the instructions for Firefox since Icewaesel is more or less a re-branded version of Firefox.

If you followed all the steps, your result should look similar to the following screenshot of the german version of LOVEFilm on SteamOS:

LOVEFilm on SteamOSLOVEFilm on SteamOS

Please Note: I do not own any Steambox since they were only shipped into the U.S. :-/ and therefore was not able to test the performance on their hardware. Moreover I didn't have time yet to install it on a real machine and it may be possible that there are still problems with hardware acceleration. The installation therefore still needs to be considered as a bit experimental.

1.9. Mageia 4 (Easy)

You can use our repository to install Pipelight on Mageia 4. Simply add the repository using the following command(s):

sudo urpmi.addmedia "Pipelight 32-bit" http://repos.fds-team.de/stable/mageia/4/i586/

It is necessary to add the 32 bit version on both 32 and 64 bit systems, as most of the plugins are 32 bit only. If you are using a 64 bit system, you also need to add this repository:

sudo urpmi.addmedia "Pipelight 64-bit" http://repos.fds-team.de/stable/mageia/4/x86_64/

As next step you need to install the key we used to sign our packages with the following command:

wget http://repos.fds-team.de/Release.key
rpm --import Release.key

Now you can install the Pipelight package as usual using urpmi. We also recommend to update the plugin database after an installation.

sudo urpmi.update -a
sudo urpmi pipelight
sudo pipelight-plugin --update

Pipelight is now ready to use and you can enable the plugins that you are interested in. The following command shows how to enable silverlight for example (you can skip over it, if you don't want to use Silverlight):

pipelight-plugin --enable silverlight

For more information about various supported plugins take a look at the post installation steps. The installation of Silverlight (or any other plugin you have selected) takes place when you start your browser the next time. Please note that you will need to install a user agent switcher for most plugins/pages to get them working.

1.10. CentOS 6 (Easy)

info

Info:

There are currently only Pipelight packages available for 64 bit as the 32 bit repositories don't include the mingw packages (while they are available for 64 bit?!)

We also provide a repository with CentOS 6 packages, so that you do not need to care about Pipelight or Wine updates. Just add the repository with the following command:

sudo wget http://download.opensuse.org/repositories/home:/DarkPlayer:/Pipelight/CentOS_CentOS-6/home:DarkPlayer:Pipelight.repo -O /etc/yum.repos.d/pipelight.repo

Now you should be able to install Pipelight as any other package. We also recommend to update the plugin database of Pipelight after the installation.

sudo yum install pipelight
sudo pipelight-plugin --update

To enable a plugin you can use the pipelight-plugin script as shown in the following line with Silverlight:

sudo pipelight-plugin --enable silverlight
# Type in 'Y' to accept the license of Silverlight and all required modules

If you already have Wine installed, you need to upgrade your packages, so that you will get our Wine version with all needed patches.

Take a look at the post installation steps for more information about enabling and disabling plugins. The installation of Silverlight (or any other plugin you have selected) takes place when you start your browser the next time. Please note that you will need to install a user agent switcher for most plugins/pages to get them working.

1.11. Compile Pipelight on your own (Advanced)

If you do not use Ubuntu / Arch Linux / Debian / openSUSE / Fedora or just want to do everything on your own, you can easily compile/build Pipelight by yourself. Please keep in mind that you will still need a patched version of Wine with XATTR support (required for DRM protected content). A short description on how to compile Wine and which patches you need to apply is available here.

info

Info:

If you want to create a package for your favorite distribution, you may want to use a tagged version instead of the development branches. The latest release is v0.2.5, you can use the URL below to download the tarball. If you prefer you can also use the corresponding precompiled Windows binaries, so that you don't have to install/compile mingw. You should also consider joining our #pipelight channel on IRC freenode, so that we may provide you with help and additional informations on updates to make it easier for you to create packages.

Before building you need to install/checkout git/bazaar/tar and choose one of the following mirrors:

Latest release (tag: v0.2.5)
Tarball wget https://bitbucket.org/mmueller2012/pipelight/get/v0.2.5.tar.gz
Precompiled
Windows binaries
wget http://repos.fds-team.de/pluginloader/v0.2.5/pluginloader.tar.gz
(license)
Latest upstream source files (Mirrors synced periodically)
Git via HTTP git clone https://bitbucket.org/mmueller2012/pipelight.git
Tarball wget https://bitbucket.org/mmueller2012/pipelight/get/master.tar.gz
Git (Mirror) git clone git://fds-team.de/pipelight.git
Brazaar (Mirror) bzr branch lp:pipelight

You also need to check that the following dependencies are fulfilled:

libc6-dev, libx11-dev, mingw-w64, g++-mingw-w64, make, g++, sed

Change to the directory containing the Pipelight repository and compile/install it using:

./configure --wine-path="/path/to/wine/executable" --gcc-runtime-dlls="/path/to/gcc/runtime/dlls/"
make
sudo make install

# Run this again after you've changed something, could also be done as a post-installation step
sudo pipelight-plugin --create-mozilla-plugins

The last step is necessary as the NPAPI only supports one plugin per library and we need to copy the library for each supported plugin (I know it's dumb), to get multi plugin support working as browsers detect symlinks or hardlinks and will load the plugin only one time in this case.

You need to alter --wine-path depending on the prefix you passed to wine during the compilation (for example /usr/bin/wine) and the --gcc-runtime-dlls options must match the path to the gcc runtime dlls (libgcc_s_sjlj-1.dll, libspp-0.dll, libstdc++-6.dll) installed by the mingw cross compiler package. Most distributions do not ship these dlls in extra packages, but require you to download the whole cross compiler (I therefore opened a bug report for Ubuntu, maybe you may want to do the same for your distribution if this is the case and you want to create packages). These paths are not hard coded into the executables, but the make script will change the configuration files accordingly for you during the installation to make life easier ;-).

If you want to install the Pipelight files to a different directory, you may also want to pass a prefix to configure. The default installation (with prefix /usr/local) will place the files in the following locations:

/usr/local/share/pipelight/signature.gpg
/usr/local/share/pipelight/pluginloader.exe
/usr/local/share/pipelight/install-dependency
/usr/local/share/pipelight/hw-accel-default
/usr/local/share/pipelight/configs/pipelight-*
/usr/local/share/pipelight/scripts/configure-*
/usr/local/share/pipelight/licenses/*
/usr/local/bin/pipelight-plugin
/usr/local/lib/pipelight/libpipelight.so
/usr/local/share/man/man1/pipelight-plugin.1*

The Pipelight project also uses some scripts and external programs which you need to install to get everything working:

bash, glxinfo, wget, zenity or kdialog (optional, but recommended), microsoft core fonts (required for Silverlight), cabextract, gnupg

After everything is installed you should be able to continue with the instructions on how to enable plugins in the next section. If you don't want to enables the plugins in your normal browser, you can use a trick to enable them only in a separate instance of your browser. Just set the environment variable MOZ_PLUGIN_PATH to tell Chrome/Firefox where to search for additional browser plugins. The following commands illustrate how to use a separate chrome instance for testing:

# Create directory to place the symlinks into
mkdir $HOME/myplugins

# Enable the plugins you want to use and tell the script to place the symlinks in a different folder
MOZ_PLUGIN_PATH=$HOME/myplugins pipelight-plugin --enable silverlight --enable flash

# Start your browser with the MOZ_PLUGIN_PATH environmental variable pointing to this directory
MOZ_PLUGIN_PATH=$HOME/myplugins google-chrome --user-data-dir=$HOME/.config/chrome-pipelight

You will most probably need to define a separate profile like in the above example as most browser would simply create a new window in the context of the current browser instance otherwise. This method has also the advantage that you don't need to install a user agent switcher as Chrome allows you to pass one via the command line (--user-agent="Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120427 Firefox/15.0a1"). Moreover it may not be a bad idea to enable a different skin for this instance so that you can distinguish between them more easily ;-)

2. Optional: Enable/disable specific browser plugins

2.1. Enable/Disable plugins

After the installation of a multi-plugin supported Pipelight version (>= 0.2.0), you can now choose which plugins you want to enable. You can either enable plugins only for your current user or for all users. The pipelight-plugin script will automatically choose between both methods depending on whether the script is executed with root rights (i.e. sudo) or not. The following extract should visualize how to use the script:

# Get a list with all supported plugins and usage information
pipelight-plugin --help

# -- SYSTEM-WIDE --

# Shows a list of all system-wide enabled plugins
sudo pipelight-plugin --list-enabled

# Enable a plugin system-wide
sudo pipelight-plugin --enable pluginname

# Disable all plugins system-wide
sudo pipelight-plugin --disable-all

# -- CURRENT USER --

# Enable a plugin for the current user
pipelight-plugin --enable pluginname

# Disable it again
pipelight-plugin --disable pluginname

If you enable a plugin for the first time then Pipelight should kick off the installation of all required plugin files when it is loaded for the first time (for example when you open about:plugins in your browser). This can takes some minutes and we recommend you to close all browser windows before enabling a plugin as for example Chrome tries to load the plugin in all open instances which may cause them to freeze temporarily. In some very rare cases it may possible that an installation may fail and Firefox will not reload the required plugin information again on it's own. You can resolve this issue by following the steps at this FAQ.

Please keep in mind that the system-wide and user configurations are independent and that you can produce situations which may not make much sense (like enable a plugin for a user and system-wide at the same time). The only thing you can not do with this script is to disable system-wide plugins for a user, which is not a limitation we implemented but is caused by file system access restrictions. Nevertheless this shouldn't be a big problem as most browsers will allow you do to disable plugins in your browser configuration.

2.2. Silverlight

To enable Silverlight system-wide, which was the default setting in older pipelight releases (and is the default behavior of some packages that try to be as compatible as possible), simply execute

# Will enable the latest available Silverlight version, currently 5.1
sudo pipelight-plugin --enable silverlight

or use the following command line to get Silverlight 5.0 (required for some services like SkyGo):

sudo pipelight-plugin --enable silverlight5.0

Don't enable both at the same time as your Browser will always try to use the newest installed version.

If you are upgrading from an older Silverlight installation on Ubuntu and need to use Silverlight 5.0 instead, you will need to execute the following command as the pipelight package will always enable the newest Silverlight version to stay compatible with the old behavior:

sudo pipelight-plugin --disable silverlight --enable silverlight5.0

You should now try to open this test applet and verify if you can see the animation. If you want to watch Netflix or some other VOD service (even some non-VOD services like Magister might require this), please install a user agent switcher as described below.
Some Silverlight applications use NTLM authentication via HTTP to enforce access restrictions, like for example RavenDB, which does not work out of the box. Wine supports this method, but it needs the ntlm_auth program of the samba package to do a three way handshake with the webserver. It is therefore required to manually install this program to use such services. Most ditributions put this program in a package called winbind. You can check if your Silverlight application uses NTLM authentication by starting the browser from a terminal and looking for the following message:

ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path

If this is the case simply install the winbind package and your problem should be solved.

2.3. Flash

The Flash plugin is a bit special since there is a Linux version of it, which lacks of some features like DRM support (at least the PPAPI version) or is not updated any more (NPAPI version), but the first installation step is similar to Silverlight:

sudo pipelight-plugin --enable flash

Pipelight should now install the windows version of Flash the first time you start your browser and the plugin gets loaded. The only problem is that you may have several versions of Flash installed and your browser may choose the linux version when opening a Flash application. You can check this by visiting our Pipelight diagnostic site, which will show you whether you have multiple versions of flash enabled.

For Chrome you can solve the problem of multiple version pretty straight forward, simply go to chrome://plugins/ and click on Details (1) and disable all Flash plugins which do not contain "pipelight" under Location (2) as shown on the following screenshot:

Disable other Flash plugins to use PipelightDisable other Flash plugins to use Pipelight

Don't be confused by the fact that the text shows "Enable" at 2, this is only because the plugins are already disabled on the screenshot.

For Firefox this is a bit more complicated since you can not individually disable specific versions of a plugin, you can only disable the whole plugin with all it's versions. The only solution I know so far is to remove your current Linux version of Flash, which is done on some distributions by simply removing a symlink. For Ubuntu / Debian I would suggest the following workaround:

Instead of using pipelight-plugin to enable the plugin system-wide, you can tell updates-alternatives that the flash plugin is now served by Pipelight by executing the following commands:

sudo update-alternatives --install "/usr/lib/mozilla/plugins/flashplugin-alternative.so" "mozilla-flashplugin" /usr/lib/pipelight/libpipelight-flash.so 1
sudo update-alternatives --set mozilla-flashplugin /usr/lib/pipelight/libpipelight-flash.so

This will remove the symlink of the NPAPI Linux plugin and replace it with a symlink to Pipelight. You can switch back by using the following command (be aware that you need to do this manually on a removal of Pipelight):

sudo update-alternatives --remove mozilla-flashplugin /usr/lib/pipelight/libpipelight-flash.so

and your original version of Flash should become active again.

In most cases you shouldn't need to install a user agent switcher for Flash, but some websites which use the DRM functionality will still require you to fake a windows browser. You can use the same settings and user agent switchers which are described in our faq entry for Silverlight.

2.4. Shockwave Player

The Shockwave Player (not to be confused with Flash) is relatively easy to install since there are no existing plugins which could cause conflicts and moreover most websites using it don't require a user agent switcher. Enabling it via the pipelight-plugin should be sufficient to get the player working with most websites and games:

sudo pipelight-plugin --unlock shockwave
sudo pipelight-plugin --enable shockwave

Some people experienced problems when you have Flash enabled at the same time - if the browser freezes on the plugin start, try to disable all versions of flash and check if this solves the issue.

You should now try out the Rally Point game on the Adobe website which should work out of the box. The game loads after some seconds and you should be able to play it. If this is not the case, right click on the black screen and check whether OpenGL is selected as renderer. Pipelight sets the renderer to OpenGL by default on the plugin installation, but it sometimes happens that Shockwave resets the settings on the first start. If everything works well it should look like:

Shockwave game - Rally PointShockwave game - Rally Point

Some games have problems with focus / mouse input or don't load at all. In most cases this can be solved by right clicking on the plugin area and disabling the backwards compatibility under settings. During all our tests we couldn't find any game which didn't work because this feature was disabled and we also got messages from users who told us that this problem also exists on windows. It is therefore a good idea to disable it on your first start of the plugin, so that you do not need to care about it any longer. Our initial idea was to set this setting automatically after the installation but Shockwave resets the value on the first start of the plugin.

2.5. Unity Webplayer

The Unity3D player was added recently to Pipelight and is in experimental state, so it is possible that you stumble upon some smaller issues or that a game does not work. The reason for this is that Wine is missing some functionality which is required by Unity and we currently use some hack fixes to workaround them. Nevertheless, we tested the plugin with over 20 different games and only one (Contract Wars) of them didn't work at all. A few ones had somehow problems with the keyboard input and thought you were always pressing the left arrow key? All other games worked without any noticeable problems.

To enable the Unity3D plugin simply use the following command:

sudo pipelight-plugin --enable unity3d

You can test the plugin by opening the Tropical Paradise demo on the unity website. You will need to use an user agent switcher to get around the unsupported platform check and somehow only the Safari user agent string worked in our test. Maybe they are also testing for navigator.platform which is not set by the most user agent switchers. You should be able to use all the demos on this site except the first one which does not use the web player but must be downloaded. The Angry Bots demo (a small game, second image) sometimes shows an error when downloading the data file which is a bit annoying but not a big problem, reloading the page will continue the download at the position where it stopped. If you were able to download all files, you will be able to play the following 3rd person shooter:

Unity - Angry BotsUnity - Angry Bots

2.6. Widevine

The Widevine plugin was introduced with Pipelight 0.2.4 and allows to play DRM protected media. Unlike other plugins the Widevine plugin itself does not work standalone as it's only some kind of an add-on for the flash player. You will therefore need to have a flash player plugin installed to make use of it, but it does not need to be the windows version of flash, you can also combine Widevine with either the linux based NPAPI or the Pepper version of flash. This makes it possible to do all the video rendering with a native linux executable while only the DRM decryption part is done in Wine, resulting in a very good playback performance.

To enable the Widevine plugin simply use the following command:

sudo pipelight-plugin --enable widevine

After enabling the plugin you can test it here by clicking on one of the two available Videos at the top (Sintel, Starz). Depending on the Website you want to use, it may be required to also install a user agent switcher as described in our faq entry for Silverlight.

2.7. npactivex

The npactivex plugin is a wrapper to use ActiveX plugins in browsers supporting the NPAPI. The main focus of npactivex are Chinese banking websites which require an ActiveX plugin to authenticate the user. Besides the plugin itself you will also need a browser extension which detects the ActiveX controls on the websites and tells the browser to load the wrapper. The extension allows you to do define which ActiveX plugins should be loaded but it also uses some site specific workarounds and is only guaranteed to work with a small amount of plugins and not as a general wrapper. Moreover the required browser extension is currently only available for Chrome.

To enable the npactivex plugin simply use the following commands:

sudo pipelight-plugin --unlock npactivex
sudo pipelight-plugin --enable npactivex

As next step you need to manually install the ActiveX plugin you want to use. The best way to get the required download link is to switch the user agent to Windows and to visit the website of your bank. Make sure to grab a 32 bit version of the plugin as our pluginloader.exe is 32 bit only (as many plugins are only available as 32 bit version). Some websites will automatically direct you to the 64 bit version if you user agent contains WOW64, x64 or Win64, so make sure to select one which doesn't contain any of these keywords. You can see current user agent on our diagnostic page.

After you got the correct executable you need to install the plugin into the wineprefix of Pipelight. This can be done via the following commands:

If it's a .exe file:

WINEPREFIX=~/.wine-pipelight /path/to/wine activexplugin.exe

If it's a .msi file:

WINEPREFIX=~/.wine-pipelight /path/to/wine msiexec /i activexplugin.msi

You will need to insert the correct path of the wine version used by Pipelight, which is distribution specific (on Ubuntu/Debian its located at /opt/wine-compholio/bin/wine. You can get the correct path by extracting it from one of the config files with the following command:

sed -n 's/[[:space:]]*winePath[[:space:]]*=[[:space:]]\([^ ]*\)[[:space:]]*$/\1/p'  /usr/share/pipelight/configs/pipelight-silverlight5.1

As last step you need to install the chrome extension from the chrome web store and enable your banking website in the options of the extensions. This extension will also try to set your user agent and therefore conflict with any user agent switcher, so that we recommend to disable them.

2.8. Other plugins

With release 0.2.3 we've decided how to handle additional plugin requests for less commonly used browser plugins. Before that the usual method was that all possible browser plugin libraries were created, even if they were not really used. The main decision behind this was that we wanted to give non-root users the possibility to decide on their own which plugins they want to use (which is only possible when the libraries are all created in advance).

As we can imagine the majority wouldn't really like it, if we would do the same, even for plugins that are probably just used a couple of times. To solve that we splitted up the plugins into two categories: default plugins (which work out of the box) and additional plugins, which can be considered very experimental or only rarely used. Such additional plugins have to be unlocked before you can enable them (which internally creates the necessary libraries).

To see the list of all plugins just type:

pipelight-plugin --help

The following example commands should show how to unlock and enable a plugin:

# Unlock the plugin (create libraries)
sudo pipelight-plugin --unlock pluginname

# Enable it
sudo pipelight-plugin --enable pluginname

# Disable it again
sudo pipelight-plugin --disable pluginname

# Lock the plugin again (delete libraries)
sudo pipelight-plugin --lock pluginname

The following additional plugins (i.e. they were not mentioned yet) are supported as of version 0.2.5 and must be unlocked:

  • adobereader - popular(?) pdf viewer on windows
  • foxitpdf - alternative to adobereader
  • grandstream - plugin to connect to IP cameras
  • hikvision - another plugin to connect to IP cameras
  • roblox - a web plugin to launch games created with roblox

3. User agent switcher

Some browser plugins like Silverlight (and even some Flash based pages) check the browser user agent, to determine that the user is running a Windows machine (even if it would work out of the box on Linux, when the plugin is loaded via Pipelight). To work around this issue you will have to install a user agent switcher (or change the user-agent string via the command line, if this is possible with your specific browser).

NOTE: Even if it seems to be totally unrelated, a wrong user agent string causes errors like plugins getting stuck at 99% loading, various error messages popping up or different kind of other weird errors. Changing the user agent is always the first thing you should try if something doesn't work as expected.

To install a user agent switcher please take a look at our faq entry.

Please use only the ones provided in the list, there are many other ones which are known not to work. You can check whether your user agent is working (in theory - try multiple ones if something doesn't work as expected!) by visiting our Pipelight diagnostic site.

4. Help, its not working / I found a bug!

Pipelight supports almost all NPAPI commands and they are tested very well so that is unlikely that you will hit a bug in Pipelight itself. Nevertheless, we rely on the fact that Wine does all the Windows to POSIX API translation for the plugins and Wine is far away from being bug free or feature complete. Most of the problems you may come across (like Webcam is not working with Flash) are therefore not related to Pipelight itself but due to missing features or bugs in Wine. You can submit bug reports in our bug tracker for all kind of bugs but if it is really Wine related and not just a wrong configuration on your system, we may not always have the time to solve it. Debugging Wine is really a time consuming task and we try to focus on features which are required by a majority of the users.

Not all problems are directly caused by bugs and are more some kind of configuration issue. We can not create our packages in a way that they will boot just with a Kernel installed, but instead we expect that your system is setup correctly, like that you have working 32 bit graphic drivers installed. So please check if there is an FAQ entry for your issue in the FAQ list at Launchpad or if someone else has already reported exactly the same problem in the bug tracker before opening a new bug. Please do not report bugs to the WineHQ bug tracker as we are using a patched version of Wine which is not allowed when reporting bugs - if you're able to reproduce the same problem with the vanilla Wine version then you're welcome to do this of course.

If your problem started after some time, it may be possible that something is messed up with your wine prefix and you should be able to wipe it and Pipelight will reinstall everything on the next start of the browser. Simply close your browser and execute rm -rf ~/.wine-pipelight/. Please keep in mind that some services limit how many PCs can be used in a specific period of time with the same account and this step most probably will cause your System to appear as a new device.

If you get the DRM error 6030 when trying to watch a video, you should definitely try to use Silverlight 5.0. The error code 6030 means that your graphic driver signature couldn't be verified which we can not implement since we don't have a Windows graphic driver in Wine. Moreover this graphic driver must be signed by Microsoft. Switching to Silverlight 5.0 often helps since the restrictions have increased with version 5.1.

If you are sure your bug is related to Pipelight, take the time to file a bug report. Please also provide the required information (described when clicking on "Report a bug") to make it easier for us to track down the possible errors. These information are really required in most cases (there are distribution specific differences, some things have changed in newer pipelight versions, …) and we would need to ask you for that if you don't provide them on your own, which will only slow down the whole process.

27 Feb 2014 18:36 CET comment by Sebastian

Hello all,

we decided to disable the comment system on all Pipelight related articles.

During the last time the comments were often used as a replacement for our bug tracker / question system, although our website doesn't offer all the required features to handle them appropriately there: There is no way to check if the same problem was already reported or to search the comments for specific keywords, there is often no hint if the problem was resolved by any of our suggestions, and moreover a lot of different requests are mixed into a single stream. We also don't have the time to add all the missing functions immediately.

To make things easier for both sides, we now only accept support requests on Launchpad at the following locations:

For bugs: https://bugs.launchpad.net/pipelight
For questions/comments: https://answers.launchpad.net/pipelight

Sebastian

27 Feb 2014 17:54 CET comment by Sebastian

Hi,

@Patrick:
The percentage alone isn't that useful to figure out which error it could be, but the crash sounds like there is a problem with GPU acceleration. I would suggest to disable GPU acceleration by running:

/usr/share/pipelight/scripts/configure-silverlight

then type "disable", "abort", and try again. If its too laggy without GPU acceleration and you need help to fix that, please open a question at Launchpad.

@Richard:
Based on your error distribution it seems like either you don't have Debian Wheezy, or you have already partitially upgraded some packages of your operating system, which causes this incompatibility. Please check your package sources file (/etc/apt/sources.list) for any unusual or third party repositories, that could probably come with a newer/incompatible version. You could also try to use our Jessie/Sid repository instead if large parts of your operating system are already newer than on a regular Debian Wheezy.

@Deepak:
The Hikvision ocx installer (required for Internet Explorer) never worked (most probably because of Wine bugs). You can just click "Ignore" during the installation, all stuff which is required for Firefox will be installed nevertheless. If I remember correctly there was some weird bug, which could lead to plugin crashes in Chrome - but it worked well in Firefox, so I would recommend to use this one for testing.

If you have aborted the installation at the point where the ocx installer failed, it might be possible that Firefox (which caches the plugin status) doesn't load it anymore, or some files are corrupted in the wine prefix. You can try to wipe it (it will be automatically recreated) and to clear the plugin cache:

rm -rf ~/.wine-pipelight
sudo pipelight-plugin --create-mozilla-plugins

If this doesn't help I would suggest to create a log and post it on the launchpad question tracker.

# Make sure all firefox windows are closed!
sudo pipelight-plugin --create-mozilla-plugins
firefox &> pipelight.log

Upload the log pipelight.log for example to pastebin.com and attach the link to your question.

Sebastian

27 Feb 2014 06:35 CET comment by Deepak Shravasti (impactitl.com)

Please help me !!!

I am using Ubuntu 12.04 LTS (64-bit).
I want to enable HIKVISION Plugin. I followed this process. But still I am not able to see video of my DVR in my browser i.e. Firefox 26.0 / Chrome 33.0.

At the time of sudo pipelight-plugin –enable hikvision command I got an error by wine, that some kind of ocx file is missing.

Can any one guide me for this. This works fine on Windows 7 machine, in my environment.

26 Feb 2014 22:56 CET comment by Richard

When following the instructions for installing on Debian Wheezy..

Reading package lists… Done
Building dependency tree
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
pipelight-multi : Depends: wine-compholio (>= 1.7.4-2~)
E: Unable to correct problems, you have held broken packages.

Trying to install wine-compholio yields…

Reading package lists… Done
Building dependency tree
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
wine-compholio:i386 : Depends: libasound2-plugins:i386 but it is not going to be installed
Recommends: gettext:i386
Recommends: libgif4:i386 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

I tried a direct download of wine-compholio to install with GDebi, but the error I receive with that is the libasound2-plugins:i386

Running Debian Wheezy amd64

25 Feb 2014 09:19 CET comment by Patrick

Hey all,

I just installed Pipelight and have only had marginal luck using it with Netflix. A video will load to 22% then the plugin crashes entirely.

I'm using the latest stable Chrome, Xubuntu 14.04, and the latest updates from Pipelight. Any help would be greatly appreciated!

Thanks!

DP-CMS 0.1 RSSRSS - Feed