*** Most common problems ***
- Keywords:
- graphic user agent xattr
- Last updated by:
- Michael Müller
There are some problems you may came across after installing Pipelight which are just caused by missing packages or a wrong configuration. This list should give you the ability to solve them quickly on your own:
-------
1. 32 bit graphic drivers / black screen / slow performance
-------
Some of the supported plugins make use of Direct3D / OpenGL to either render 3D content or to simply accelerate the rendering of videos. This requires that you have your graphic drivers are setup correctly otherwise you will either get an error message (Unity3D) or other plugins might just show a black rectangle or fall back silently to software rendering. Since all our plugins are 32 bit only, you are also required to have the 32 bit drivers installed. Many Linux distributions do not install them automatically and you most probably do not even notice that you are missing them as everything is compiled for 64 bit. To check whether you have such a problem, close all your browser windows and start your browser from a terminal. You should see then one of the following message when using the Plugin:
err:winediag:
err:winediag:
err:wgl:has_opengl Failed to load libGL: libGL.so.1: cannot open shared object file: No such file or directory
If you are using Silverlight, hardware acceleration will only be enabled for NVIDIA and Intel cards as AMD cards are causing problems at the moment. If you are using AMD graphic cards you will only see the following message:
[PIPELIGHT:
*** Solution ***
Actually the instructions to install the 32 bit libraries are very different depending on the distribution and the graphic card you are using. Anyway, it is not sufficient to have the 32 bit libGL installed from the mesa package, you will also need the corresponding 32 bit DRI libraries! So here are some instructions for selected distributions and graphic drivers. Feel free to edit this faq and add other distributions:
--- NVIDIA (Proprietary driver) ---
-> Manual installation:
Simply make sure that you answer "Install NVIDIA's 32-bit compatibility OpenGL libraries" with yes and that is all you need to do.
-> Ubuntu:
The Ubuntu package for the proprietary driver also installs the 32 bit libraries by default, simply make sure that you have enabled the driver in the "Additional drivers" dialog under settings.
-> Debian:
Make sure that you have the libgl1-
--- Open Source Drivers: Intel / Nouveau ---
-> Ubuntu / Debian:
Simply execute "apt-get install libgl1-
-> Arch Linux:
You need the following packages depending on the graphic card you are using:
For Intel: lib32-intel-dri
For Nouveau: lib32-nouveau-dri
For AMD: lib32-ati-dri
************
If the performance is still bad although you have installed all necessary packages and video acceleration is working, your problem may not be related to your video at all. Silverlight for example synchronizes the video playback to the audio output and things like asynchron / delayed sound is a good hint that the real problem is the audio output. If you are using pulseaudio (which should be the majority) try to execute "pulseaudio -k" to restart pulseaudio. This should fix the problem in most of the cases. For more information take a look at https:/
-------
2. User agent switcher / plugin freezes / error messages
-------
Some plugins, especially Silverlight, do not work on all sites if they detect a non windows user agent. This may result in weird error messages on Netflix or the Silverlight application will simply not finish loading at all. You should therefore always install a user agent switcher as described in https:/
-------
3. xattr / Silverlight DRM not working
-------
Silverlight uses ACL (the windows way of handling permission on files) to protect it's DRM files. To store these information we use extended attributes and it is required that they are enabled for your filesystem. You can check this by executing:
touch ~/.xattr_test && setfattr -n 'user.testAttr' -v 'attribute value' ~/.xattr_test &> /dev/null; getfattr ~/.xattr_test 2>&1 | grep -q user.testAttr && echo 'It works!' || echo 'No workie!'; rm ~/.xattr_test &> /dev/null
Make sure that you have getfattr / setfattr installed, otherwise the result is useless (Ubuntu / Debian package: attr).
*** Solution ***
You will need to enable xattr for your filesystem if you get "No workie!" although getfattr / setfattr is installed. This depends a bit on the used file system, but in most of the cases you will need to edit your /etc/fstab file and add "user_xattr" to the mount options. For more information take a look at: http://
-------
4. home directory on NFS volume
-------
Pipelight does not work if your home directory is on a NFS volume as it is lacking xattr, flock, ... support. You will need to either symlink ~/.wine-pipelight/ to a directory which uses a different filesystem or mount an image file into this directory. Another possibility is to copy the configuration files of the plugins from /usr/share/
winePrefix = $HOME/.
to some other directory which is not mounted via NFS.
-------
5. distribution specific issues
-------
--- Fedora ---
On Fedora the wine version provided with Pipelight replaces the system-wide version. If you already have installed wine before, you will need to update your wine version, otherwise DRM content will not work. To verify that you're using our version of wine, it is sufficient to run:
wine --patches
If you see a long list of patches, then everything is okay. If the command is not found or you get an error message, then you haven't upgraded yet.
--- Ubuntu 13.10 / Mint 16 ---
Some newer distributions like Mint 16 don't install recommendations automatically anymore - this means that specific packages might be missing, which reduce the functionality (like that it only works in non-embedded mode) or lead to other unexpected behaviour. To fix this issue, install wine-compholio like:
sudo apt-get install wine-compholio --install-
-------
6. plugin crashs on loading / browser extensions (noscript, ...)
-------
Some browser extensions like noscript or httpseverywhere cause the individualization of Silverlight to fail resulting in a crash or error message. Please take a lookt at https:/
