FDS-TEAM
Linux, Windows, Programming and more...
Pipelight - Installation
15 Oct 2013 00:08 CEST  - 60 comment(s)

# 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, multi-plugin)

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.

You just have to type in the following commands in your terminal to add the necessary repositories to your system:

sudo apt-add-repository ppa:ehoover/compholio
sudo apt-get update


If you want to use only Silverlight, you can now proceed with the following command which will automatically enable Silverlight and is mostly provided for backwards compatibility with old installations:

sudo apt-get install pipelight


Otherwise you should use our new multi-plugin system, which allows you to select the plugins you want to use. The next commands illustrates how to install the pipelight-multi package and how to enable Silverlight 5.1. If you don't want to use this plugin, simply skip the second line. More information on enabling plugins or using different Silverlight versions is available at the end of the page.

sudo apt-get install pipelight-multi
sudo pipelight-plugin --enable silverlight


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.

When you decided to use the multiplugin version you can optionally enable additional plugins, 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, multi-plugin)

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


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, multi-plugin)

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:

wget http://download.opensuse.org/repositories/home:/DarkPlayer:/Pipelight/Debian_7.0/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

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


to your /etc/apt-sources.list file. Update your package cache by executing:

apt-get update


For Debian jessie and Sid (see below for liboups0 problem) you need to manually install some packages as there is more than one installation candidate for a virtual package which we depend on and Debian does not know which one to choose:

# Debian jessie (Is this still necessary? You may want to try without it first)
apt-get install libjack0:i386

# Debian Sid (see below)
apt-get install libasound2-plugins:i386 libavcodec54:i386


The installation is now the same as on Ubuntu. If you want to use only Silverlight, you can use

apt-get install pipelight


otherwise use the following command which also enables Silverlight (simply skip the second line if you don't want this) is highly recommended:

apt-get install pipelight-multi
pipelight-plugin --enable silverlight


The installation on Sid (may also affect Jessie) is a bit more complicated since one of the dependencies is not multi-arch ready and you manually need to rebuild libopus0 with multi arch support to get around this issue before installing Pipelight. You can find the needed patch in the corresponding bug in the debian bugtracker. I also precompiled the packages with the patch applied, so that you can get around this issue by installing the amd64 and i386 version of the packae with dpkg -i.

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, multi-plugin)

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


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 (Easy, multi-plugin)

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 packages, just replace Fedora_19 with Fedora_18)

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


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


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, multi-plugin)

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. […]

Info:

We haven't automated the build process for this distribution yet, which means that the packages for this distribution could lag behind the other ones a bit. We're going to automate this, when the request is high enough such that it makes sense to do this effort. The current packages are for pipelight version 0.2.2.

# Note: As this seems to be a bit problematic on AVLinux the GPU acceleration is disabled by
# default. You can still force it if you want to give it a try, just run your browser with
# the environment variable PIPELIGHT_GPUACCELERATION set to 1

wget "https://dl.dropboxusercontent.com/u/21447213/AVLinux/pipelight-multi_0.2.2~avlinux.deb"
wget "https://dl.dropboxusercontent.com/u/21447213/AVLinux/wine-compholio_1.7.6~avlinux.deb"


As a next step you should always check

sha256sum *.deb


to be sure nothing has been modified:

d8a1f7cd24d5b5d331b04db899ce5217e22c2132cad89842d1d02f34c4b75d93  pipelight-multi_0.2.2~avlinux.deb


and install them with dpkg -i (as root user, the order is also important):

dpkg -i "wine-compholio_1.7.6~avlinux.deb"
dpkg -i "pipelight-multi_0.2.2~avlinux.deb"
pipelight-plugin --enable silverlight


If you get some error message about missing dependencies (which should not be the case, when you haven't uninstalled packages which are there by default) install them or ask us when unsure. Moreover 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, multi-plugin)

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.

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:

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.2, 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.2) Tarball wget https://bitbucket.org/mmueller2012/pipelight/get/v0.2.2.tar.gz Precompiled Windows binaries wget https://launchpad.net/pipelight/trunk/0.2/+download/pluginloader-prebuilt-v0.2.2.tar.xz (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/pluginloader.exe
/usr/local/share/pipelight/pipelight-* 			(configs)
/usr/local/share/pipelight/install-dependency
/usr/local/share/pipelight/hw-accel-default
/usr/local/bin/pipelight-plugin
/usr/local/lib/pipelight/libpipelight.so


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)


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 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 --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 Point

Some games have problems with focus or mouse input which 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 Bots

# 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 has still to be seen in beta stage. Nevertheless everything has already been tested before and almost everything (except some specific configurations or minor issues) should work. 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.

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.

10 Dec 2013 19:57 CET

Hi Lee Elson,

I assume you encounter this problem which mainly occurs with the broken default graphic drivers provided by Ubuntu 13.10.

As this bug report suggests (for example answer #2) you can try to disable GPU acceleration or alternatively update your graphic card drivers (see for example answer #21).

For a quick test its sufficient to start your browser with:

PIPELIGHT_GPUACCELERATION=0 firefox


(you can also use a different browser for testing, just ensure that you've closed all other browser windows before)

By the way: I saw your message in IRC, but unfortunately you had already left when I was back.

Sebastian

10 Dec 2013 16:33 CET

Hi Sebastian:

Thanks for your input. I was able to install user-agent-overrider and it works. Now, when I try Netflix, it fails with a pop up message:
pluginloader.exe has encountered a serious problem

I'll check the pipelight channel for answers too.

10 Dec 2013 05:06 CET

Hi Lee Elson,

the problem is that you've set your user agent switcher to Internet Explorer - since IE uses a completely different plugin system it doesn't work when you set it to that. We recommend to use a FireFox user-agent string instead.

I would recommend to do the following steps to get it working with the User-Agent Overrider plugin:

After you've installed it you should see a new icon right beside your address bar. When you click on it you see Preferences and some preconfigured user agent settings like "Firefox 22/Windows". You have to select there the user agent string you want (for example Firefox 22/Windows).
Afterwards refresh the page, and verify with the diagnostic page that the string really has changed.

Unfortunately this UA switcher doesn't contain Firefox 15 (which is required for some other sites). If you notice that some pages still do not work as expected, click again on the UA Overrider icon, select Preferences, and then copy&paste the following line in the textbox (insert below all other entries for example):

Firefox 15/Windows: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120427 Firefox/15.0a1


This adds a new option "Firefox 15/Windows" which works with almost every page.

If you need additional help with the configuration feel free to join our channel #pipelight on IRC freenode.

Sebastian

10 Dec 2013 04:57 CET

I'm having trouble ("Active x disabled") getting a user agent to work in Firefox 25.0.1 (Ubuntu 13.10). UAcontrol doesn't seem to change the agent (as determined by your test page) and I can't figure out how to use user-agent-overrider. Any suggestions?

06 Dec 2013 06:03 CET

Hi jason,

yes to both of your questions.

Pipelight is also compatible with the Opera browser and should work out of the box when for example Silverlight is enabled system-wide. Besides Firefox, Chrom(ium) and Opera we also support Midori, Uzbl, … and some other browsers which allow to configure NPAPI plugins.

For Linux Mint you've to pay attentation that there are some versions which are based on Ubuntu, some other versions are based on Debian. After you've checked which version you're using exactly just following the corresponding installation instructions.

Feel free to ask us if you encounter any error.

Sebastian