Netflix DRM error N8152 fedora 18
Hi!
I am trying to watch netflix on my fedora 18 box.
I got the bunny video http://
Netflix was failing with all kinds of errors.
Discovered the XATTR requirement and install libattr-devel, reconfigured and recompiled wine-1.7.3 with all the patches.
Also enabled the user_xattr attribute on my ext4 filesystem. (disabled tmpfs to be sure as wine seems to put files in /tmp)
Removed my ~/.wine-pipelight and manually installed corefonts and silverlight.
Now netflix player loads up to 98% and then failes with drm error N8152.
Did i miss anything? or is it currently not working?
(used patches from http://
to compile wine i used: tools/make_
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Pipelight Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Michael Müller
- Solved:
- Last query:
- Last reply:
Revision history for this message
|
#1 |
Hiho!
The N8152 error can be caused by two things:
* you should check that you have a user agent switcher installed that modifies the JS user agent string. I would also recommend to set it to Firefox 15, which is known to work for most pages, see: https:/
To verify if the user agent switcher works correctly you can use our diagnostic page: http://
* it can be caused by missing XATTR support.
Concerning the second problem: Unfortunately wine uses some kind of weird auto-magic to detect if XATTR is available, and fails in some cases. I have experienced that although I didn't do anything different, in some cases XATTR wasn't detected by configure and not compiled in.
You can check if this is the issue with the following command (execute in the wine build directory):
cat config.log | grep XATTR
If this returns an empty output, then XATTR was not detected. You can try the following trick to force it - just define the environment variable CFLAGS before running configure.
CFLAGS=
and then compile it again. This helped in my case.
( You can also join our IRC channel #pipelight on IRC freenode if you have additional questions, most of the pipelight devs are on there and in some cases a chat is easier to figure out problems than an issue tracker ;-) )
Sebastian
Revision history for this message
|
#2 |
Hi!
My user agent string : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120427 Firefox/15.0a1
cat config.log | grep XATTR provides lots of output.
I can also see attributes being set on the Playready directory
# file: home/menne/
user.wine.
So i am guessing wine is applying the ACL's...
Revision history for this message
|
#3 |
Hi,
I have just rechecked the previous answered questions and bug reports, and noticed, that noone else had exactly this error code yet (with similar error codes it was always caused by one of the reasons above). Moreover I know from some other people, that they managed to run it on Fedora, so I assume that there has to be something special with exactly your setup.
* Do you use the pipelight-sandbox (default is disabled, but can be enabled via config file)? It is still in beta stage, and doesn't work well with DRM protected content. If this is the case please disable it again.
* Are you using SELinux or something similar? It might be possible that some of the DRM functions don't work properly if this is the case (Silverlight for example spawns separate processes for DRM stuff, which is denied for browser plugins in the default configuration.)
* Are you using a very old kernel? It could be possible that a specific kernel feature like for example the RTMGRP_IPV4_IFADDR flag is not yet available.
* Which SIlverlight version do you use and how did you install everything? I would recommend to use 5.1 - the easiest way is to get it is to use the install-dependency script provided in the misc/ folder of the pipelight repo. A manual installation would also work, of course. Additionally it might be necessary to change the config paths. The mpg2splt-dependency is not needed for netflix, but for some other streaming services.
If none of these ideas helps, please include the full terminal output (close your browsers first, then start your browser from a terminal, and redirect stdout&stderr):
chromium-browser &> ~/pipelight.log
Sebastian
Revision history for this message
|
#4 |
Hi! thx for the quick responses.
I dont use pipelight-sandbox, i use the default config with a changed wine path... (mine is in /usr/local)
SELinux status: disabled
Kernel version: 3.10.12-
Removed ~/.wine-pipelight and reinstalled with install-dependency script
Still the same error.
Here is the log:
[7164:7164:
[7164:7164:
[7164:7164:
[7164:7164:
[PIPELIGHT:LIN] attached to process.
[PIPELIGHT:LIN] trying to load config file from '/home/
[PIPELIGHT:LIN] basicplugin.
[PIPELIGHT:LIN] using wine prefix directory /home/menne/
[PIPELIGHT:LIN] checking Silverlight installation - this might take some time.
wine: cannot find L"C:\\windows\
err:wineboot:
[PIPELIGHT:WIN] windowless mode is off.
[PIPELIGHT:WIN] embedded mode is on.
[PIPELIGHT:WIN] usermode Timer is off.
fixme:advapi:
[PIPELIGHT:WIN] init successful!
fixme:advapi:
[PIPELIGHT:LIN] attached to process.
[PIPELIGHT:LIN] trying to load config file from '/home/
[PIPELIGHT:LIN] basicplugin.
[PIPELIGHT:LIN] using wine prefix directory /home/menne/
[PIPELIGHT:LIN] checking Silverlight installation - this might take some time.
wine: cannot find L"C:\\windows\
err:wineboot:
[PIPELIGHT:WIN] windowless mode is off.
[PIPELIGHT:WIN] embedded mode is on.
[PIPELIGHT:WIN] usermode Timer is off.
fixme:advapi:
[PIPELIGHT:WIN] init successful!
fixme:advapi:
[PIPELIGHT:LIN] attached to process.
[PIPELIGHT:LIN] trying to load config file from '/home/
[PIPELIGHT:LIN] basicplugin.
[PIPELIGHT:LIN] using wine prefix directory /home/menne/
[PIPELIGHT:LIN] checking Silverlight installation - this might take some time.
[PIPELIGHT:WIN] windowless mode is off.
[PIPELIGHT:WIN] embedded mode is on.
[PIPELIGHT:WIN] usermode Timer is off.
fixme:advapi:
[PIPELIGHT:WIN] init successful!
[PIPELIGHT:LIN] using timer based event handling.
fixme:advapi:
fixme:heap:
fixme:file:
fixme:module:
fixme:urlmon:
fixme:process:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:process:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
fixme:thread:
0
fixme:thread:
fixme:thread:
fixme:module:
fixme:advapi:
fixme:ntdll:
fixme:mountmgr:
fixme:advapi:
fixme:mountmgr:
fixme:advapi:
fixme:thread:
^Cfixme:
fixme:advapi:
Revision history for this message
|
#5 |
Hi,
Sorry for the late reply, but I was running out of ideas myself. Did you manage to get rid of this error yourself, or does it still persist?
I don't think that we've changed that much, but you could try to start again with the latest versions of pipelight and wine-compholio. We also have some a bit more detailed explanations how to compile everything.
(Please uninstall all previous versions of pipelight first, and verify that it doesn't appear anymore in the browser plugin list and in /usr/lib/
Wine 1.7.4: http://
Pipelight 0.2.0: http://
Please note that it shouldn't be necessary to modify pipelight config files manually anymore - just take a look at the command line arguments of ./configure:
Usage: ./configure [--prefix=PREFIX] [--wine-path=PATH]
The default paths are (you should see the paths after running configure):
prefix = '/usr/local'
winepath = '/opt/wine-
mozpluginpath = '/usr/lib/
gccruntimedlls = '/usr/lib/
Moreover: Which file system do you use exactly? For most people this error disappeared after wiping the wine prefix ~/.wine-pipelight, when it still persists after doing this it could probably be related to some file system issues.
Sebastian
Revision history for this message
|
#6 |
I recompiled the latest as soon as it arrived.
Still the same error, just now I remembered that I mount my filesystem with the noatime option, could that be the problem? I'll also delete my localized config.
I'll post back with results once I tested.
Revision history for this message
|
#7 |
Hi Analytical,
I just created some packages for Fedora and was able to play a DRM protected video with them. You should try to use them since they are known to work. Simply remove all files you may still have from older tries (mostly /usr/{local,
-------
# Install Microsoft core fonts
sudo yum install cabextract
sudo rpm -i http://
# Add repository
sudo wget http://
# Install Pipelight and enable Silverlight
sudo yum install pipelight
sudo pipelight-plugins --enable silverlight
-------
Just replace Fedora_19 with Fedora_18 in the repository url to get the Fedora 18 packages. After installing a user agent switcher I was able to play DRM protected videos, although there were some SELinux warnings because of mmap. I hope this works for you. Nevertheless I have to warn you that this was literally the second time I ever booted Fedora and don't have much experience in RPM based distributions so I can't guarantee that there might not be any problem with the packages (missing dependencies or similar). Any feedback is welcome.
Michael
Revision history for this message
|
#8 |
Hi, fixed it, turned out to be the untangle intrusion detection.
Turning that off fixed the error.