Pipelight fail to start Wine when there is multiple wine installation on Linux

[Qian Hong]

I have multiple Wine installation on my system, one is build from source code and installed to /usr/local/bin/wine. When trying to start Windows plugin, pipelight reports the error like below:
===
Pipelight Error (npactivex)!
Something went wrong, check the terminal output
===

From the terminal output, I see:
===
wine client error:0: version mismatch 455/454.
Your wine binary was not upgraded correctly,
or you have an older one somewhere in your PATH.
Or maybe the wrong wineserver is still running?
===

After some investigation, I found the solusion from Wine faq works well:
http://wiki.winehq.org/FAQ#head-5d2fd5010318b5facd3ebf67930d1259e67c465f
$ export WINEVERPATH=$W
$ export PATH=$W/bin:$PATH
$ export WINESERVER=$W/bin/wineserver
$ export WINELOADER=$W/bin/wine
$ export WINEDLLPATH=$W/lib/wine/fakedlls
$ export LD_LIBRARY_PATH="$W/lib:$LD_LIBRARY_PATH"
$ google-chrome

I proposal to set the above enviroment value in basicplugin.c:startWineProcess(), so the user will not have to do it manually, could you consider have a look?

Thanks a lot for your great work!

[Erich E. Hoover (ehoover)]

This should only matter if you are running multiple versions of Wine at the same time, which your suggestion will likely fix - but I'm not certain how stable that would be. Have you tried closing other Wine instances before using pipelight?

[Ken Sharp (kennybobs)]

I run multiple versions of Wine simultaneously and they work fine. It sounds like there's something wrong with your $PATH.

Wine looks for the binaries in the directory it is installed in first by default. ...and works.

[Qian Hong (fracting)]

Hello,

We've discussed this on #pipelight-team, sorry for no update here:

I've set my LD_LIBRARY_PATH to /usr/local/lib, that was for using custom libxcb build to work around http://bugs.winehq.org/show_bug.cgi?id=31882, which is not necessary now.

After unset LD_LIBRARY_PATH, everything works fine.