Last error: 126 on Fedora 19

Asked by Richi

I'm trying to install (and eventually package) Pipelight for Fedora 19 (x86_64) and have gotten to a point where I don't know how to move forward. I've downloaded the v0.1-2 tar ball and built and installed it without issue. I've also patched wine-1.7.0-1.fc19.x86_64 with the 2 patch files inside the pipelight package, rebuilt the RPMs and installed them, again with no issue.

I wasn't sure how to install Silverlight on wine so I first tried "wine Silverlight.exe" which seemed to work but because of the issue described later on, I uninstalled it and re-installed it by running "wine FirefoxPortable.exe" (from http://portableapps.com/apps/internet/firefox_portable) and navigated to MS's Silverlight site and downloaded Silverlight.exe and ran it from FirefoxPortable. Again, the installation seemed to go through. Doing an "about:plugins" in FirefoxPortable gave a "State: Enabled" for "Path: C:\Program Files (x86)\Microsoft Silverlight\5.1.20513.0\npctrl.dll" but trying to access Silverlight sites just produced an empty window where I would expect the Silverlight app to appear. Right-clicking on the window and selecting "Silverlight" would give me the Silverlight control panel.

Moving on the Pipelight, I copied the pipelight config file to $HOME/.config/ and modified it for my system (still using $HOME/.wine/ for my wine prefix). I had to copy the libpipelight.so file to $HOME/.mozilla/plugins/ because it didn't seem to be picked up in the default "/usr/lib/mozilla/plugins/" dir on Fedora 19. On Firefox, "about:plugins" just gives me the generic:

Pipelight Error!

    File: libpipelight.so
    Path: /home/richip/.mozilla/plugins/libpipelight.so
    Version: 0.0
    State: Enabled
    Something went wrong, check the terminal output

and I don't know how to get console output from the firefox wrapper script used. So I switched to google-chrome which gave a similar error in "about:plugins" but in the console output, I got the following:

[PIPELIGHT] Attached to process
[PIPELIGHT] Trying to load config file from /home/richip/.config/pipelight
[PIPELIGHT] GPU driver check script not found - treating test as failure
[PIPELIGHT] Using wine prefix directory /home/richip/.wine/
[PIPELIGHT] Windowless mode is off
[PIPELIGHT] Embedded mode is on
[PIPELIGHT] Usermode Timer is off
[PIPELIGHT] Last error: 126
[PIPELIGHT] Could not load library
[PIPELIGHT] Failed to initialize DLL
[PIPELIGHT] Error during the initialization of the wine process - aborting

In "pipelight" config file, I have the following set (among other configs):

winePrefix = $HOME/.wine/
dllPath = c:\Program Files (x86)\Silverlight\5.1.20513.0\

Any help would be appreciated in getting Pipelight to work

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
Best Michael Müller (mqchael) said :
#1

Hi,

I would always recommend to do all the testing with Chrome! Firefox caches the errors and the plugin isn't loaded at all in some cases. When everything works you can just clear the plugin cache with the following commands, then it should work in Firefox, too.
------
Type "about:support" in your address line and hit enter. You should now see a button which opens your profile directory. Click on it and remove the "pluginreg.dat" file in this directory. Restart your browser and check if it works now.
------

I think I already know what your problem might be - when you're using the default Silverlight installer, the directory contains "Microsoft" in its name, which is missing in our default config. The silverlight-installer dependency we're using already installs everything to a different path. Probably this problem is already solved just by putting in the correct path into your config file.

If you want to get some more detailed debug output you can also go to: http://fds-team.de/pipelight/
When you visit this page it will run some diagnostic checks in order to find errors in config files / nonexistent files and so on.

If the problem persists please attach the output of the diagnostic page above.

By the way: Are the wine patches by Erich E. Hoover also included? If not you may probably experience other issues with streaming sites.

Michael

Revision history for this message
Richi (richip) said :
#2

I tried "about:support" in google-chrome-stable-29.0.1547.62-219432.x86_64 and got a "This webpage is not available". Clicking on "More" gave me: "The webpage at chrome://support/ might be temporarily down or it may have moved permanently to a new web address." This is google-chrome running on Fedora Linux. Did you mean for me to try Google Chrome running on Wine?

I tried the http://fds-team.de/pipelight/ site and got:

------
Pipelight diagnostic:

User agent (Javascript)
Checking for Windows user agent ...failed
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.62 Safari/537.36

Silverlight (as seen by a website)
Checking for Silverlight ...failed

Pipelight
Checking for Pipelight ...okay
------

Am I supposed to change the User agent setting? The Silverlight entry seems to indicate it can't find Silverlight, but as you can see in my pipelight config entries above, I'm directing pipelight to the correct Silverlight installation directing on Wine.

As for patches, I only have the following patches applied from the pipelight-0.1-2 package:

0008-winex11-Add-minimal-XEmbed-client-support.patch
0009-d3d9-Partial-implementation-of-IDirect3DSwapChain9Ex.patch

I'll try to find the Erich Hoover patches and apply them and do a rebuild/reinstall of wine.

Revision history for this message
Richi (richip) said :
#3

Sorry ... didn't see the prompt on Chrome to allow Pipelight to execute. After clicking on always allow, I get the following:

------
Pipelight diagnostic:

User agent (Javascript)
Checking for Windows user agent ...failed
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.62 Safari/537.36

Silverlight (as seen by a website)
Checking for Silverlight ...failed

Pipelight
Checking for Pipelight ...okay

Configuration of Pipelight
Checking if config exists ...okay
/home/richip/.config/pipelight
Checking if pluginLoaderPath is set and exists ...okay
/usr/share/pipelight/pluginloader.exe
Checking if winePath is set and exists ...okay
/usr/
Checking if winePath/bin/wine exists ...okay
/usr//bin/wine
Checking if winePath/bin/winepath exists ...okay
/usr//bin/winepath
Checking if winePrefix is set and exists ...okay
/home/richip/.wine/
Checking if dllPath/dllname is set and exists ...failed
/home/richip/.wine/dosdevices/c:/Program Files (x86)/Silverlight/5.1.20513.0//npctrl.dll
(dllPath = c:\Program Files (x86)\Silverlight\5.1.20513.0\)
(dllName = npctrl.dll)
Checking if dependencyInstaller is set and exists ...failed
/usr/share/wine-browser-installer/install-dependency
You either have to install the dependencyInstaller script or setup your wine prefix manually.
Depending on the distribution you probably will have to execute some post-installation script to do that.

Distribution
Loading file /etc/issue ...okay
Fedora release 19 (Schrödinger’s Cat)
Kernel \r on an \m (\l)

Content of file: /home/richip/.config/pipelight
Loading file /home/richip/.config/pipelight ...okay
#
# Enables a diagnostic mode which might be helpful to find an
# error in the configuration or installation.
# To get the error messages go to: http://fds-team.de/pipelight
#
# Information for advanced users: The diagnostic page embeds the plugin
# of type "application/x-pipelight-error" to trigger the output of some
# debug information. The plugin cannot be triggered if everything is
# working, so this only affects users with a broken installation.
# The debug output will include paths on the local filesystem and the
# linux distribution used. If you don't want to leak this information
# accidentially in case of a broken installation please either uninstall
# Pipelight or disable the diagnosticMode. [default: false]
#
diagnosticMode = true

#
# Path to the wine directory
# * the wine executable itself should be at: winePath/bin/wine
# * the winepath executable should be at: winePath/bin/winepath
#
# Please note: In older versions this was a path to the wine
# executable instead (deprecated, but should still work).
#
#winePath = /opt/wine-compholio/
winePath = /usr/

#
# Path to the wine prefix containing Silverlight
#
winePrefix = $HOME/.wine/

#
# The wine architecture for the wine prefix containing Silverlight
#
#wineArch = win32
wineArch = win64

#
# DLLs to overwrite in Wine
# (prevents Wine from asking for Gecko or Mono)
#
wineDLLOverrides = mscoree,mshtml=

#
# Path to the plugin loader executable
# (Should be set correctly by the make script)
#
pluginLoaderPath = /usr/share/pipelight/pluginloader.exe

#
# Path to the runtime DLLs (libgcc_s_sjlj-1.dll, libspp-0.dll,
# libstdc++-6.dll). Only necessary when these DLLs are not in the same
# directory as the pluginloader executable.
#
#gccRuntimeDlls = /usr/lib/gcc/i686-w64-mingw32/4.6/
gccRuntimeDlls = /usr/i686-w64-mingw32/sys-root/mingw/bin/

#
# Path to the Silverlight directory
# Must be changed if a different version should be used.
# The standard installation Path is:
# c:\Program Files\Microsoft Silverlight\5.1.20513.0\
#
dllPath = c:\Program Files (x86)\Silverlight\5.1.20513.0\

#
# Name of the Silverlight library to load
# (relative to the path specified above)
#
dllName = npctrl.dll

#
# fakeVersion allows to fake the version string of Silverlight
# Allows to get around some version checks done by some websites
# when using an old version of Silverlight.
#
# fakeVersion = 5.1.20513.0

#
# overwriteArg allows to overwrite/add initialization arguments
# passed by websites to Silverlight applications. You can
# use this option as often as you want to overwrite multiple
# parameters. The GPU acceleration state of Silverlight can be controlled
# by setting:
#
# enableGPUAcceleration=false # disable GPU acceleration
# comment out # let the application decide (default)
# enableGPUAcceleration=true # force GPU acceleration
#
# You may need to overwrite the minimum runtime version if
# you use an old Silverlight version as some websites set
# an artificial limit for the version number although it
# would work with older versions.
#
# overwriteArg = minRuntimeVersion=5.0.61118.0
# overwriteArg = enableGPUAcceleration=false
# overwriteArg = enableGPUAcceleration=true
#

#
# windowlessmode refers to a term of the Netscape Plugin API and
# defines a different mode of drawing and handling events.
# On some desktop enviroments you may have problems using the
# keyboard in windowless mode, on the other hand the drawing is
# more efficient when this mode is enabled. Just choose what works
# best for you. [default: false]
#
windowlessMode = false

#
# embed defines whether the Silverlight plugin should be shown
# inside the browser (true) or an external window (false).
# [default: true]
#
embed = true

#
# Path to the dependency installer script provided by the compholio
# package. (optional)
#
dependencyInstaller = /usr/share/wine-browser-installer/install-dependency

#
# Silverlight version to install using the dependencyInstaller
# (optional)
#
# Valid values are:
# silverlight5.1
# silverlight5.0
# silverlight4
#
# If you changes this value, you also need to adjust dllPath
#
silverlightVersion = silverlight5.1

#
# In order to support browsers without NPAPI timer support
# (like Midori) we've implemented a fallback to
# NPN_PluginThreadAsyncCall. In the default configuration
# a timer based approach is preferred over async calls and the
# plugin decides by itself which method to use depending on the
# browser capabilities. Setting the following option to true
# forces the plugin to use async calls. This might be mainly
# useful for testing the difference between both event handling
# approaches. [default: false]
#
# eventAsyncCall = true

#
# The opera browser claims to provide timer functions, but they
# don't seem to work properly. When the opera detection is
# enabled Pipelight will switch to eventAsyncCall automatically
# based on the user agent string. [default: true]
#
operaDetection = true

#
# Minimal JavaScript user agent switcher. If your page doesn't check
# the user agent before loading a Silverlight instance, you can use
# this trick to overwrite the useragent or execute any other Java-
# Script you want. You can use this command multiple times.
# Uncomment the following 4 lines for FF15 spoofing.
#
# executejavascript = var __originalNavigator = navigator;
# executejavascript = navigator = new Object();
# executejavascript = navigator.__proto__ = __originalNavigator;
# executejavascript = navigator.__defineGetter__('userAgent', function () { return 'Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120427 Firefox/15.0a1'; });

#
# We are currently implementing hardware acceleration support, which
# can cause problems on some systems as especially specific open source
# drivers render only garbage when hardware acceleration is enabled.
# To prevent breaking any working solutions, we are currently
# implementing a whitelist system, which will enable hardware
# acceleration by default if the specified shell scripts returns 0.
# Otherwise we will disable it. You can still use
#
# overwriteArg = enableGPUAcceleration=false/true
#
# to overwrite the check results. If you really want to skip this test
# you can use: graphicDriverCheck = /bin/true
#
graphicDriverCheck = /usr/share/wine-browser-installer/hw-accel-default

#------------------------- EXPERIMENTAL -------------------------
# Watch out: The following section contains highly experimental
# stuff! These functions are likely not working properly yet and
# might be removed at any time.

#
# Silverlight uses a lot of timer stuff do to the window redrawing
# . In order to speed this up a bit the following switch enables
# some API hooks to do most of timer stuff in user mode (without
# having to call wine-server each time). It is still unclear
# if this option has any significant effent on the performance.
# [default: false]
#
# experimental-userModeTimer = true
------

Revision history for this message
Richi (richip) said :
#4

Sorry ... I missed a couple of things. I've added "Microsoft " in my config's dllPath setting. I've also installed User-Agent Switcher for Chrome and selected Windows Firefox 15. http://fds-team.de/pipelight/ now gives me:
------
Pipelight diagnostic:

User agent (Javascript)
Checking for Windows user agent ...okay
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120427 Firefox/15.0a1
Please note: not every user agent works on every site, try multiple ones if something doesn't work!

Silverlight (as seen by a website)
Checking for Silverlight ...okay
Version: 5.1.20513.0

Result
Result from all tests ...okay
You are ready to use Silverlight
------

I'll verify that it works now. I still have yet to apply the Hoover patch. Will update Question when I have more info.

Revision history for this message
Sebastian Lackner (slackner) said :
#5

Hi Richi,

the instructions with about:support are only required for Firefox, not for Chrome/Chromium. You can skip over this if you want to continue testing with Chrome, but will have to do that later in Firefox to reload everything.

Concerning the patches: There are a few more patches requires, you can find them here (patches 1-7):
http://bazaar.launchpad.net/~ehoover/netflix-desktop/wine-compholio/files/head:/patches/
But this is not directly related to your current problem, this only affects some streaming sites.

As Michael already wrote, the problem is that your dllPath is incorrect.
Your config contains: dllPath = c:\Program Files (x86)\Silverlight\5.1.20513.0\
But in your first message you wrote: C:\Program Files (x86)\Microsoft Silverlight\5.1.20513.0\
(which contains an additional "Microsoft" in the path)

Moreover you'll have to change back "wineArch" to win32, as it only works well with the 32bit version (you've also installed the 32bit version, as you can see in the path name).

Sebastian

Revision history for this message
Richi (richip) said :
#6

Thanks.

I've recreated my wine prefix and am now using WINEARCH=win32. Reinstalling Silverlight caused it to move the path to the expected "C:\Program Files\Microsoft Silverlight\5.1.20513.0\". I'm still getting a blank window when I try a silverlight site like http://bubblemark.com/silverlight2.html (which doesn't seem to be a video streaming site), but then, I haven't applied the patches yet.

Am attempting to apply the Erich Hoover patches now, but they're not applying cleanly or at all on wine-1.7.0 from Fedora 19. I'll continue to work on this.

Thanks for all the help so far!

Revision history for this message
Richi (richip) said :
#7

My mistake. I tried to use both patches:

0009-d3d9-Add-headers-for-IDirect3DSwapChain9Ex-interface.patch
0009-d3d9-Partial-implementation-of-IDirect3DSwapChain9Ex.patch

I've picked one (0009-d3d9-Partial-implementation-of-IDirect3DSwapChain9Ex.patch) and am NOT applying 0010 to 0015 from the pipelight wine-patches directory. It's rebuilding right now. Will send a follow-up post when completed, reinstalled and tested

Revision history for this message
Sebastian Lackner (slackner) said :
#8

Hi,

you've to watch out that you don't accidentially mix up different patches.

You should always use Erich E. Hoovers patches 0001 - 0007 and then ADDITIONALLY our patches.

For v0.1-2 you can use these 2 patches:
https://bitbucket.org/mmueller2012/pipelight/src/4de635ad1bcb0f52f91fd5224022afa2f9d82a5c/wine-patches?at=v0.1-2

Alternatively you can also use our newer versions of the patches - these are a lot more files as we're currently working on some improvements to get them upstream:
https://bitbucket.org/mmueller2012/pipelight/src/02e9e11880391bb10fb7aa7378ed9457987c2067/wine-patches/?at=master

After this you should either have patches 0001 - 0009 or 0001 - 0015, depending on which version you use.

One thing you've to pay attention to: The xembed patch has been updated since the initial release version v0.1-1. The latest version has the md5sum 61fffa33f9280cd398cee756007a7bbf. When using the older version of the patch there are still some problems with KDE.

When you want to test without all patches applied you can change your configuration file and set "embed" to "false" manually. Then you'll get the Silverlight content in a separate window instead.

Sebastian

Revision history for this message
Richi (richip) said :
#9

Thanks for all the help. At this point, it's starting to look as if my issue isn't a pipelight issue. I've applied patches 0001 to 0009 to wine-1.7.0 from Fedora 19, reinstalled it, removed my wine prefix ($HOME/.wine) and reinstalled MS Silverlight. I am still getting the same result (blank window where the Silverlight app is supposed to be). Based on your previous comments that your patches are only supposed to enable embedded mode, I even tried pipelight in non-embedded mode and the new window resulted in the same blank window. Even running PortableFirefox with wine resulted in the same issue.

Who can I turn to for help with my issue? This is the output I get from Chrome whenever I try to start the Bubble test app:

NP_GetMIMEDescription: returned mime description
NP_GetValue(var=1)
NP_GetValue(var=2)
NP_Initialize (gwt-hosted-mode/c++), pid=3770
NPP_New(instance=0x7ff307a7f4c0,mode=1,argc=4,args=[id=pluginEmbed,type=application/x-gwt-hosted-mode,width=10,height=10],saved=(nil)): version=27
NPP_SetWindow(instance=0x7ff307a7f4c0,window=0x7ff307a45960)
[PIPELIGHT] Attached to process
[PIPELIGHT] Trying to load config file from /home/richip/.config/pipelight
[PIPELIGHT] GPU driver check script not found - treating test as failure
[PIPELIGHT] Using wine prefix directory /home/richip/.wine/
[PIPELIGHT] Windowless mode is off
[PIPELIGHT] Embedded mode is off
[PIPELIGHT] Usermode Timer is off
fixme:advapi:RegisterTraceGuidsW (0x2b1f87, 0x350118, {aa087e0e-0b35-4e28-8f3a-440c3f51eef1}, 1, 0x63f6e8, (null), (null), 0x350118,): stub
[PIPELIGHT] Init sucessfull!
[PIPELIGHT] Using timer based event handling
fixme:advapi:CreateProcessAsUserW 0xf4 L"C:\\Program Files\\Microsoft Silverlight\\5.1.20513.0\\agcp.exe" L"agcp.exe 8 236" (nil) (nil) 1 0x00004000 (nil) (null) 0x63f1e8 0x63f1d8 - semi- stub
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:file:K32GetMappedFileNameW (0xffffffff, 0x4015f4, 0x50e234, 520): stub
fixme:module:GetModuleHandleExW should pin refcount for 0x240000

Revision history for this message
Michael Müller (mqchael) said :
#10

Hi,

someone else also experienced the same issue on OpenSUSE (blank window even when embed = false). When I tried to reproduce it I didn't encounter any problems and I think it is related to the fact that OpenSUSE applies a lot of patches to Wine. Do you also apply some Fedora specific patches? I just used the Wine 1.7.1 tarball from the Wine website and applied our patches.

I created a short and experimental guide on how to install Pipelight on OpenSUSE ( http://pastebin.com/uZiHKDqe ), maybe it also helps you to find your problem..

Michael

Revision history for this message
Richi (richip) said :
#11

Thanks for the reply. You actually answered a question I was about to ask (which version of Wine is known to work? 1.7.1 from your message above).

Currently, Fedora applies the following patches (just the filenames) to wine-1.7.0:

wine-1.5.17-osmesa-check.patch
wine-cjk.patch
wine-pulse-1.7.0.patch
wine-pulse-winmm-Load-winealsa-if-winepulse-is-found.patch

I'll try a couple of things: 1) try to rebuild wine without any of the Fedora patches, 2) try to apply the hoover/pipelight patches to a version of 1.7.1 (probably from rawhide), 3) if 1 fails to compile, I'll just do a manual build (not use rpmbuild) and install to a private directory like /opt/wine-compholio. My goal is to eventually package pipelight for Fedora 19 and submit my package for consideration to/by RPMFusion.

Btw ... pipelight and firefox had a couple of SELinux issues on Fedora 19. I had to do a couple of manual fixes before it came up to par with google-chrome. Now both load the pipelight plugin but both still have that "blank window" issue.

Revision history for this message
Richi (richip) said :
#12

Thanks Michael Müller, that solved my question.

Revision history for this message
Sebastian Lackner (slackner) said :
#13

Hi Richi,

wine-1.7.0 should also work - this version is still used in the Ubuntu repository.

As you've already suggested: I would also recommend to do the next tests without any Fedora specific patches, and if it works you can include them again step by step.

If you have further problems and want to get a faster answer than here you can also join #pipelight on IRC freenode, me and Michael (=DarkPlayer) and also some other package maintainers are there almost all the time ;-) When you're ready with your package we can also add it to our homepage if you want.

Sebastian

Revision history for this message
Daniel Hansen (dhansen) said :
#14

I'm currently running into the same issues as Richi. I did not, however, start with the fedora version of wine, I simply downloaded the wine-1.7.0.tar.bz2 package directly from winehq.org and applied the patches. I'm starting to think it is an issue with Xorg or the graphics stack in Fedora 19, but I don't know of a way to debug it further. I see that you have a newer set of patches now (0001 - 0015). I will try these patches and see if things come out differently. Otherwise, I suspect that this may be more involved to debug.

Revision history for this message
Sebastian Lackner (slackner) said :
#15

Hi Daniel,

Did you do your testing with the bubble balls demo? If not try this page, some other pages only work with user agent switcher and other configurations.

Did you also try to switch to non-embedded mode and enable/disable GPU acceleration? If not yet:

* Create a copy of the default config in your home directory (if you haven't one yet)
cp /usr/share/pipelight/pipelight ~/.config/pipelight

* Open ~/.config/pipelight and try to modify the following settings...
(1) overwriteArg = enableGPUAcceleration=false
(2) embed = false

if this doesn't work try again with enableGPUAcceleration=true.

Moreover you can also try out:
* Does resizing the window in nonembedded mode trigger a redraw event?
* Does it change anything when you're using a different window manager (which one are you using currently)?

If all this doesn't help - do you experience the same problem with other wine programs ?

Sebastian

Revision history for this message
Daniel Hansen (dhansen) said :
#16

I've tried pretty much all of those things at one point or another, but none of them helped in the past. However, I'm recompiling everything from scratch and I'll give it another go, with a bit more of a methodical approach. I'll let you know what I find.

Revision history for this message
Daniel Hansen (dhansen) said :
#17

Sebastian:

I tried disabling embed and running with/without GPU Acceleration enabled, but still no luck. All I see is a white box where the silverlight content should be. If I right click on the plugin area, the silverlight context menu comes up and I can even open up the settings window and browse the tabs, toggling elements there.

As to the question about running other wine programs: I just ran Google Sketch-up with my custom-compiled version of Wine (Vanilla 1.7.1 + patches 0001 - 0016) and it ran just fine.

Revision history for this message
Daniel Hansen (dhansen) said :
#18

To elaborate, the above testing was done on the Bubblemark page (bubblemark.com/silverlight2.html)

Revision history for this message
Sebastian Lackner (slackner) said :
#19

Hi Daniel,

Michael (=DarkPlayer) is currently investigating this issue by setting up a virtual machine and trying to reproduce it.

I assume that this is either some kind of weird bug only appearing with fedora, or that something is wrong of the compiled version, like for example that its a 64-bit instead of 32-bit wine installation.

If you want to you can join #pipelight on IRC freenode (for example with this webchat: http://webchat.freenode.net/?channels=%23pipelight ), maybe we find the issue while discussing about this problem.

Sebastian

Revision history for this message
Daniel Hansen (dhansen) said :
#20

I think I've discovered the source of the issue. I just installed MS core TT fonts from http://corefonts.sourceforge.net and the bubblemark page now loads. However, I've also discovered that XATTR does not appear to be enabled for ext3/ext4 on Fedora by default. Is there any way around this, other than having to recompile the kernel to get DRM working?

Revision history for this message
Michael Müller (mqchael) said :
#21

You most probably don't need to recompile your kernel. Extended attributes are disable in some distributions by default on filesystem level but not on kernel level. Try to change your fstab file like described in this wiki entry:

http://wiki.gentoo.org/wiki/Netflix/Pipelight#Adding_support

and execute mount / -o remount . You can now test if it works by executing

xattr_test=$(HOME); 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!'

which is a slightly improved version of the same wiki entry.

Revision history for this message
Daniel Hansen (dhansen) said :
#22

Looks like I am mistaken, ext4 is the fs I'm using, which looks to support xattr by default. When I grep my wine config.log for xattr (i.e. grep -i xattr config.log), I don't get any output, which seems like it might be the issue. Any idea why wine wouldn't be compiling xattr support?

Revision history for this message
Sebastian Lackner (slackner) said :
#23

Hi Daniel,

I also don't know why xattr support is sometimes missing, even if the file system supports it, but I'm using the following workaround:

CFLAGS=-DHAVE_ATTR_XATTR_H=1 ./configure ...

It doesn't appear in config.log, but its definitely compiled in.

Sebastian

Revision history for this message
Daniel Hansen (dhansen) said :
#24

I just saw your comment about the test, the test works, but it still appears that wine isn't compiling in XATTR support

Revision history for this message
Daniel Hansen (dhansen) said :
#25

AHA! It looks like I needed to install libattr-devel.

Revision history for this message
Daniel Hansen (dhansen) said :
#26

I now have netflix running in Google Chrome on Fedora 19. Here are my take-aways:

(1) Not having the MS TT core fonts installed appears to have lead to the "white box" issue that I was seeing (you can follow instructions at this website to get them installed on Fedora: http://corefonts.sourceforge.net/)
(2) libattrs-devel needs to be installed before configuring and compiling wine

Revision history for this message
Michael Müller (mqchael) said :
#27

Hi,

does one of you two know if there is still a plan to create a fedora package for pipelight?

Michael

Revision history for this message
Daniel Hansen (dhansen) said :
#28

I don't have much packaging experience, but I'd like to put my efforts to benefit more fedora users, so that they can use and test pipelight as well. I'm gonna give it a try.

Revision history for this message
DominikL (dominikluebben) said :
#29

Can anyone provide RPM packages of the patched Wine and a Pipelight package for Fedora 19? Would be great. :)