Need Advice on Pipelight Install
Greetings
I am part way through a Pipelight install, mainly for the purpose of satisfying Netflix browser and Silverlight requirements. I didn't install a useragentchanger but instead just used Firefox's "about:config" and created the proper key. This seems to be working fine. Pipelight almost completes the diagnostic page. I get 2 errors Code:
Code:
Checking if dllPath/dllname is set and exists ...failed Code:
/usr/libexec/wine-pipelight/bin/regedit Thanks in advance for any help in this matter. |
What is the output of "pipelight-plugin --list-enabled" when you run it as your own user account?
Eric |
Hello, and thank you for responding
Code:
bash-4.2$ pipelight-plugin --list-enabled |
That looks OK at least.
Try this: Stop the browser. Delete your ~/.wine-pipelight/ directory (it only contains stuff related to pipelight, your existing default wine configuration will be untouched). Open the pipelight test URL http://fds-team.de/pipelight/ right after you start your browser again. You should see the Windows plugin downloads (performed by wine-pipelight) and that should cause no errors. It will take a little while to complete and during that time your browser will seem frozen. Does this make a difference? Did you install a "cabextract" package? Eric |
Thanks Alien Bob but zero change. Exactly the same 2 errors. I'm not sure about the "as webpages will see it" part but I think I must resolve the "dllPath/dllname" issue to proceed.
and yes I have had cabextract for some time. I'm using "cabextract-1.3-i486-1_SBo". Is this recent enough? |
Update
Ok I think I see a problem but I'm not sure how it is to be fixed. The error refers to a dllPath/dllname like this
Code:
Checking if dllPath/dllname is set and exists ...failed It was my understanding that the diagnostic page installs the plugin. Did I jump the gun somewhere and do something out of order? I followed the sequence outlined on http://alien.slackbook.org/blog/pipe...inux-browsers/. The only deviation was using about:config to set "general.useragent.override". Originally I incorrectly chose a WinX64 string because many sites identify my CPU as opposed to my OpSys, but I have since changed that to Code:
Mozilla/5.0 (Windows NT 6.2; rv:22.0) Gecko/20130405 Firefox/22.0 EDIT-Update Further- OK I am apparently still getting lots of crosstalk to my existing wine install because even though I launched "Silverlight.exe" specifically from "/usr/libexec/wine-pipelight/bin/wine" Silverlight was installed to my existing Wine as "Program Files/Microsoft Silverlight". On a whim I copied it to the pipelight version of Program Files and renamed it to just "Silverlight" as that was what the error stated it sought. Now everything is green-lighted (so the error listed at the top of this post is no longer a fail) except for Code:
Silverlight (as seen by a website) |
Wine creates a base directory in your homedirectory where it installs all the Windows related stuff you want to use. By default this is ${HOME}/.wine aka ~/.wine
If you want to have multiple independant setups of wine (in your case, the 'normal' wine and the 'wine-pipelight', but you could also think about a specific Wine configuration for a single game that has other requirements than your other Windows related stuff) then you instruct Wine to use a different base directory than ~/.wine . You do that by defining the variable WINEPREFIX. Pipelight sets the variable WINEPREFIX="$HOME/.wine-pipelight" which is how all the pipelight stuff gets installed in ~/.wine-pipelight . Try setting this before running that SilverLight installe: Code:
export WINEPREFIX="$HOME/.wine-pipelight" |
About the installation of Silverlight and other programs through wine-pipelight: This is done when the pipelight plugin is activated for the first time. That can be triggered by several means: you can open "about:plugins" or visit the Pipelight test page http://fds-team.de/pipelight/ or open another page that requires the plugin (such as the Netflix page).
Eric |
Thanks again, Alien Bob, for your attention to this matter. I know your time is precious and I'm absolutely positive it is safe to speak for the entire Slackware Community that this is something very special about Slackware, that a Slackware Developer like yourself, would take the time to help what could be just one member. It gives us all confidence and pride, I think. I hope it also gives you the same.
OK back to Pipelight. I tried exporting WINEPREFIX exactly as you posted and then cd'd to "~enorbet/.wine-pipelight/drive_c/users/enorbet/Temp" in console (where I stored the "Silverlight.exe" that came from Netflix), and ran Code:
wine ./Silverlight.exe So now when I go to the Pipelight test page I am still at the same spot, where everything is green-lighted except Code:
Silverlight (as seen by a website) If I run "about:plugins" I see the error message Code:
Pipelight Error (silverlight5.1)! Thanks again for your help so far. |
Let's try a different approach. Did you install my binary packages, or did you compile your own versions and installed those? I am beginning to wonder if your wine-pipelight is 64-bit.
What does this return? Code:
file /usr/libexec/wine-pipelight/bin/wine Code:
/usr/libexec/wine-pipelight/bin/wine: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), stripped Code:
[PIPELIGHT:LIN:unknown] attached to process. Code:
Silverlight Plug-In Eric |
Ok both of my wine installs were almost entirely from your slackbuilds. Only a few componenets of my main wine install were compiled from source and they all work perfectly. As far as wine-pipelight goes, I had installed cabextract much earlier as mentioned above, but these I installed just a few days ago, together
1) pipelight-0.2.4.2-i486-1alien.tgz 2) webcore-fonts-installer-3.0-noarch-2alien.tgz 3) wine-pipelight-1.7.11-i486-1alien.tgz and my return is indeed as expected Code:
bash-4.2$ file /usr/libexec/wine-pipelight/bin/wine Code:
[PIPELIGHT:LIN:unknown] attached to process. |
I guess there you have your culprit.
Code:
zenity: error while loading shared libraries: libnotify.so.1: cannot open shared object file: No such file or directory Pipelight prefers to use zenity if it finds the program installed. Unfortunately for you, zenety is broken on your computer and therefore the Wine installations which want to paint a dialog box on your screen fail. Remove zenity, remove the directory ~/.wine-pipelight and restart your browser. See what happens. Eric |
Bingo Baby! :D
Naturally that did it and the payoff is perfect. Netflix streams like it was on cable tv, except I have a much better sound system on my PC, LOL. Nothin' quite like a recording quality sound card through a 600 watt 12' Subwoofer, w/ 300 watts on satellites w/ 8.5" Midrange and Ribbon Tweets! WooHOO! Plus, my main Wine still works perfectly as well. I'm a very happy man.... all thanks to Alien Bob, and what some M$ FUD Flunky recently referred to on TechRadar as "the miserable world of Linux terminal commands". Oh yes! I am SO miserable :D I hope you're smiling as big as me, Alien Bob. Dankuwel! PS I must've installed zenity a long time ago as some dependency since I have no recollection why I had it. Just to be complete, I suppose I should install the latest to keep it all shiny. |
All times are GMT -5. The time now is 05:13 PM. |