After a long time of silence (but ongoing development as shown in their git repository) the Pipelight developers released a new stable pipelight a few weeks ago. I created Slackware packages for this (Slackware 14.0 and newer) but before you upgrade, please read the words of caution at the end of this post, they will save you some frustration.
The new pipelight is a bugfix release: after Google deprecated NPAPI plugins, the focus for Pipelight team has been better support for Firefox. As stated in the release notes, most of the remaining bugs should now be in Wine, not in pipelight. That has also lead to more focus on what used to be called “wine-compholio”. the team’s patch-set for wine that implements the Windows browser plugin support. The name “wine-compholio” has changed to “Wine Staging” which is now even used as the default wine version on Fedora. I am not willing to go that far, so there is still a separate wine-pipelight package that you have to install on Slackware in order to use my pipelight package.
Remember that you can always get the latest Windows plugin releases (an important feature in case of security fixes) without having to wait for me creating a new package. Just run the command “pipelight-plugin –update” as root. After doing that, the next time your browser loads the pipelight plugin, it will automatically download the newest version of your installed Windows plugin(s).
I know that some people are grumbling whenever someone develops a program for Linux that enables the use of Windows software (emulated or otherwise), such as wine or pipelight. The fact is, if you want to watch Netflix on your Slackware computer, and you do not want to install Google Chrome, then Mozilla Firefox combined with pipelight and MS SilverLight is still the only way to achieve this. Chromium does not support NPAPI either and the Widevine CDM can not be made to work as it does in Chrome. Also, software using Silverlight is still widespread in school systems. I will welcome the future implementation of EME in Firefox that will allow separate download and use of Content Decryption Modules (CDM) like Widevine which is used by Chrome for streaming Netflix. Then, Google Chrome nor pipelight/silverlight will be necessary any longer. Accepting that DRM is here to stay and can still be made compatible to Open Source and Free Choice is the start and I am glad that Mozilla thought hard and long about the apparent clash and came up with a sane solution.
Anyway, enough of the ranting.
In my original post about pipelight, you will find full installation and configuration instructions, as well as a troubleshooting section. That blog article is also referred to on the pipelight.net support page. Let me remind you that you need to go multilib if you want to use pipelight on 64-bit Slackware.
Package location (uploads expected later today, I thought it was more important to have this blog page up first):
A note of caution when upgrading to my pipelight-0.2.8 package:
This only applies to 64-bit Slackware!!!
I have made one important change to the file locations of the 64-bit pipelight package. The file “libpipelight.so” is a 64-bit shared library, but the previous 64-bit pipelight packages would install this file into “/usr/lib/pipelight/libpipelight.so”. That is not the correct location for 64-bit libraries, so the new package installs this file as “/usr/lib64/pipelight/libpipelight.so”.
This has the side effect that your pipelight stops working. The error message(if you start firefox in a terminal) will be something like “pluginInitOkay(): incompatible version of pluginloader.exe“. Don’t worry, you can remedy this.
These are the steps you have to take in order to fix this (it’s a one-time action):
As root user: remove all old copies of the library created by earlier pipelight versions:
# rm -r /usr/lib/pipelight
As your own user account, list all plugins you have currently enabled (copy that command’s output because you have to re-enable them in a later step):
$ pipelight-plugin --list-enabled
That command basically checks your “~/.mozilla/plugins/” directory for symlinks named “libpipelight*.so”. If you look inside that directory, you will notice that all these symlinks are pointing to the no longer existing location “/usr/lib/pipelight”. So, you first remove those symlinks:
$ pipelight-plugin --disable-all
And re-create them properly (still as your own user account):
$ pipelight-plugin --enable <your previously enabled plugin(s)>
That’s all. Have fun! Eric
Thanks Eric – I cheated a bit because “pipelight-plugin –list-enabled” didn’t list anything. So I went into the plugin directory and manually changed the symlink from lib to lib64. Works fine.
Pingback: Links 23/12/2014: Updates on GNU/Linux in China and N. Korea | Techrights
The pipelight-plugin –update is NOT updating either Flash or Silverlight. Currently installed flash version is 126.96.36.199 and silverlight -5.1.40416. Running the command in sudo and the next time Firefox starts it should download the updates, but doesn’t. The updater script runs and reports the signature on the file is from Wed 06 Apr 2016. I know that both these plugins have been updated for security issues. Is the FDS team deprecating pipelight-plugins or do I have a different issue?
Brian, looking at https://bitbucket.org/mmueller2012/pipelight/commits/all there has not been a new commit to the updater since April 6.
I can not tell you the status of pipelight development. Best is to ask the developers directly on https://answers.launchpad.net/pipelight/ .
Will you be upgrading wine- pipelight with you latest version of wine 1.9? Or is there a slackbuild script which I can use to that?
Brian I have not looked at pipelight for a long time… I am using Chromium these days and quite happy with it.
I will check the pipelight status shortly and see what needs to be done about the wine-pipelight component.
Brian, I have updated the pipelight package with version 0.2.8.2.
This version of the package no longer requires a separate “wine-pipelight” package. You can safely “removepkg” it. The new pipelight uses a regular wine installation like the one you get with my “wine” package.
My own wine package has the “wine-staging” patches applied (a requirement to make wine work with pipelight), as well as the “wine-nine” patches (which leverages the improved d3d9 support in mesa through gallium-nine).
If you want to use someone else’s wine instead you need to make sure that it applies the “wine-staging” patch set. A vanilla wine will not work with pipelight.