Comment 2 for bug 1235918

Hi hoeg85,

it might be possible that you're the first person that is stumpled upon a page, that requires a better DRM protection level.

A bit background information: The error 6030 is nothing completely new, it also occured on a lot of other pages in earlier versions of pipelight, but it should be fixed for most of them - EXCEPT pages that really require Microsoft signed driver certificates - see https://bugs.launchpad.net/pipelight/+bug/1222293 .

Nevertheless it might be possible that there is still something configured wrong, so to ensure that this is not the case, please check the following things, and report back, what the settings are / if these things work for you.

* I'm not sure if this could be related to the problem, but please check, if there is an update for "wine-compholio" available. The following line suggests that you're still using an older version, as this message doesn't occur that often in new versions:
[PIPELIGHT:LIN] pluginfunctions.c:561:NPP_Destroy(): plugin did not deinitialize properly, killing it!

sudo apt-get update && sudo apt-get upgrade

You should also install all other updates related to pipelight, wine-*-installer and things like that.

* The debug output above shows that you've already changed the silverlightVersion in your config file, but doesn't show all the other settings. Can you please attach your config file to take a look at it, and to verify that all changes are correct:

/home/user/.config/pipelight

* I assume you didn't have the possibility yet to test with other DRM protected pages yet, is this correct? The following DRM test page should work with Silverlight 5.0: http://web.sldrm.video.msn.com/d1/sldrm.html (BUT NOT WITH 5.1!).
If this one also doesn't work, please check with the following command if you have XATTR enabled.

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

If this prints "No workie!" you should check if you have XATTR disabled in /etc/fstab or if you're using a filesystem without any XATTR support (ext3,4 should be supported).

.

I hope that one of these ideas helps to solve the problem, as its currently not possible yet to work around this issue, when the webpage REALLY wants Microsoft signed driver certificates - but so far we didn't find any example for this yet.

Sebastian