Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Neuntausend
GoonWaffe Goonswarm Federation
31
|
Posted - 2013.05.26 07:40:00 -
[1] - Quote
I may hae found something that reliably gets rid of the -7 error, at least it does for me. Sadly, I do not know what exactly it is.
As far as I know, the Launcher is based on chrome, and chrome based apps have always had several problems, especially with secure connections. A few releases ago, a fix for the worst problems got integrated into wine, but other quirks remained. Now there are a few other popular games that use chrome and thus have some issues running under wine: Guildwars 2 for example. Today I saw a "wine-1.5.28-Guildwars2" build in PlayOnLinux's list of available wine builds and tried that for Eve, and who would have thougt? The Launcher works now.
If you have playonlinux, please go ahead, try it and report back with your results.
|
Torgeir Hekard
Brutor Tribe Minmatar Republic
1
|
Posted - 2013.05.26 08:40:00 -
[2] - Quote
Looks like confirming.
That is, I haven't tried playonlinux version (their wine is built withoiut OSS support, and I use OSSv4), but researching the subject a little led me to this patch:
https://gist.github.com/selman/4597314/raw/0ec8cef131133d9900a66b018029390332c1817c/awesomium-partial.diff
Apparently it changes something in handling SSL certs.
After patching git wine with it, I got launcher showing the login frame properly 5 times in a row, and as a bonus, now https works in IGB (actually the latter is more important for me since I use custom launcher script that lets me avoid typing my passwords on my broken keyboard till the new laptop arrives). |
Kyle Valentine
Aliastra Gallente Federation
13
|
Posted - 2013.05.26 19:08:00 -
[3] - Quote
1.5.28 Guildwars 2 works for me with POL. No more -7 error. |
Anun Hen
Justified Chaos
10
|
Posted - 2013.05.26 19:14:00 -
[4] - Quote
Assuming I have downloaded the latest wine source tarball from winehq, would somebody be kind enough to provide some step-by-step instruction on how to patch them to include this fix? |
Woo Mi
Federal Navy Academy Gallente Federation
1
|
Posted - 2013.05.26 19:31:00 -
[5] - Quote
Yup, it's a git patch, so some translation magic will be required to use it as a regular patch. I still need to figure this out. On a positive note, a freshly compiled tar of the just released 1.5.31 wine does work if you run the client directly. |
Mr M
Agony Unleashed
238
|
Posted - 2013.05.27 03:00:00 -
[6] - Quote
Super!
|
Torgeir Hekard
Brutor Tribe Minmatar Republic
2
|
Posted - 2013.05.27 04:37:00 -
[7] - Quote
Anun Hen wrote:Assuming I have downloaded the latest wine source tarball from winehq, would somebody be kind enough to provide some step-by-step instruction on how to patch them to include this fix?
Extract the tarball somewhere.
Place your patch file there
Run patch -p -i patchfile.patch
Install the packages necessary to build wine (in debian-based distros like ubuntu this would be sudo apt-get builld-dep wine)
cd into the build directory and run ./configure. I also highly recommend you to use --prefix=/home/username/wine-git or something like that. You will understand why later.
If the configure script didn't exit with an error, run make depend and then make. Also, by default, make uses a single thread to compile stuff, so if you have a multicore CPU (would be surprise if you don't), you'd want to use make -jN where N is the number of desired threads to run (you can use something like number of cores for that) to speed up the process.
Then you run (or don't run) [sudo] make install. Here the --prefix part of ./configure comes handy. If you didn't specify the prefix, it's set to / by default, meaning the wine in question would install system-wide screwing up your existing wine installation. Also it's not a good way to install software in a distro with a package manager (you'd want to make a .deb package out of it. Or what your system uses instead). So if you don't want to do something irreversible, use --prefix, and that's where the wine would install when you run make install. If you didn't specify the prefix and don't want to litter your system, you can omit the make install part and run wine directly from the build directory. It's messy but works.
then you can run eve as usual, only specifying a full path to wine.
i.e. instead of wine ExeFile.exe you run /home/username/wine-1.5.30/bin/wine ExeFile.exe.
Or
export WINE=/home/username/wine-1.5.30/bin/wine
Also you should probably run things like regedit and winecfg for your new wineprefix from that directory too (note that you don't need your EVE directory to be under wine
$WINE ExeFile.exe
Also you might want to specify a clean wineprefix, since the new wine does not require any additional stuff to run eve (that is, no installing VC runtimes, no usual overrides). The only override you will need is set d3d11 to disable.
You should probably also run regedit and winecfg from the new wine directory for the new wineprefix. Mind that you don't need to move your EVE installation directory (that is, if you specify unix path to the game as a wine argument. If you use wine "c:\Program Files\blablabl" you'd want to make a link to the eve directory inside your new wineprefix. But you DO want to copy your client settings to the new wineprefix.
PS: on something hanging somewhere.
I believe it's not a wine bug. WinXP and Win2k3 users report the launcher remaining in process tree indefinitely after they close it. When I was using the new launcher, I've got the same problem. That is, I've noticed the launcher remaining in the process tree eating CPU. Even if you don't launch client from it and just try to close it normally without disabling WINEDEBUG, you'd notice that it litters the outpt with errors about race conditions between different threads that continue for about a minute or so after closing the launcher. So I think it's not a wine problem, but rather a horrible coding on CCP part. |
Tetractys
Phoenix. Tactical Narcotics Team
0
|
Posted - 2013.05.27 08:05:00 -
[8] - Quote
Torgeir Hekard wrote:Anun Hen wrote:Assuming I have downloaded the latest wine source tarball from winehq, would somebody be kind enough to provide some step-by-step instruction on how to patch them to include this fix? Extract the tarball somewhere. Place your patch file there Run patch -p -i patchfile.patchInstall the packages necessary to build wine (in debian-based distros like ubuntu this would be sudo apt-get builld-dep wine) cd into the build directory and run ./configure. I also highly recommend you to use --prefix=/home/username/wine-git or something like that. You will understand why later. If the configure script didn't exit with an error, run make depend and then make. Also, by default, make uses a single thread to compile stuff, so if you have a multicore CPU (would be surprise if you don't), you'd want to use make -jN where N is the number of desired threads to run (you can use something like number of cores for that) to speed up the process. Then you run (or don't run) [sudo] make install. Here the --prefix part of ./configure comes handy. If you didn't specify the prefix, it's set to / by default, meaning the wine in question would install system-wide screwing up your existing wine installation. Also it's not a good way to install software in a distro with a package manager (you'd want to make a .deb package out of it. Or what your system uses instead). So if you don't want to do something irreversible, use --prefix, and that's where the wine would install when you run make install. If you didn't specify the prefix and don't want to litter your system, you can omit the make install part and run wine directly from the build directory. It's messy but works. then you can run eve as usual, only specifying a full path to wine. i.e. instead of wine ExeFile.exe you run /home/username/wine-1.5.30/bin/wine ExeFile.exe. Or export WINE=/home/username/wine-1.5.30/bin/wine$WINE ExeFile.exeAlso you might want to specify a clean wineprefix, since the new wine does not require any additional stuff to run eve (that is, no installing VC runtimes, no usual overrides). The only override you will need is set d3d11 to disable. You should probably also run regedit and winecfg from the new wine directory for the new wineprefix. Mind that you don't need to move your EVE installation directory (that is, if you specify unix path to the game as a wine argument. If you use wine "c:\Program Files\blablabl" you'd want to make a link to the eve directory inside your new wineprefix. But you DO want to copy your client settings to the new wineprefix. PS: on something hanging somewhere. I believe it's not a wine bug. WinXP and Win2k3 users report the launcher remaining in process tree indefinitely after they close it. When I was using the new launcher, I've got the same problem. That is, I've noticed the launcher remaining in the process tree eating CPU. Even if you don't launch client from it and just try to close it normally without disabling WINEDEBUG, you'd notice that it litters the outpt with errors about race conditions between different threads that continue for about a minute or so after closing the launcher. So I think it's not a wine problem, but rather a horrible coding on CCP part.
Great explaination. Can you please integrate it with an help if you have to perform this procedure on a x86_64 system? (xubuntu 13.04 -x86_64).
Thank you in advance! Kind Regards. |
Torgeir Hekard
Brutor Tribe Minmatar Republic
3
|
Posted - 2013.05.27 08:40:00 -
[9] - Quote
Tetractys wrote:Great explaination. Can you please integrate it with an help if you have to perform this procedure on a x86_64 system? (xubuntu 13.04 -x86_64).
Thank you in advance! Kind Regards. Unfortunately I run x86 system myself, so I'm not much of a help here.
There is, however, an article on WineHQ on how to build a 32-bit wine on an amd64 system
http://wiki.winehq.org/WineOn64bit#head-b62ae8f996e97e1df7258bb8eaec2e83e54ca799
NOTE: Pay attention to ubuntu versions. That is, if you decide to use the chroot method, you should change precise to whatever version you use (I'm not well versed in the arcane art of ubuntu release naming conventions) when doing debootstrap, lest you end up with a release that is mismatched to your apt sources list and your main system. |
Anun Hen
Justified Chaos
11
|
Posted - 2013.05.27 11:05:00 -
[10] - Quote
Tetractys wrote:explanation
thanks, I was more looking for instructions on how to apply this specific file (which is on github) to the wine source. Or can I just save the patch as "xxxx.patch" and run patch -p -i xxxx.patch?
should I be at the root of the sources directory? |
|
Torgeir Hekard
Brutor Tribe Minmatar Republic
3
|
Posted - 2013.05.27 11:20:00 -
[11] - Quote
Anun Hen wrote:Tetractys wrote:explanation Or can I just save the patch as "xxxx.patch" and run patch -p -i xxxx.patch? should I be at the root of the sources directory?
Yes.
Yes. |
Anun Hen
Justified Chaos
11
|
Posted - 2013.05.27 13:29:00 -
[12] - Quote
Torgeir Hekard wrote:Anun Hen wrote:Tetractys wrote:explanation Or can I just save the patch as "xxxx.patch" and run patch -p -i xxxx.patch? should I be at the root of the sources directory? Yes. Yes.
thank you, will try soon and report |
Doublewhopper
The Revelation Crew DarkStorm Enterprises
16
|
Posted - 2013.05.28 01:24:00 -
[13] - Quote
Launcher with patched wine confirmed as working in terms of "technically working".
Now usability and user experience is a whole different story...sadly... |
Torgeir Hekard
Brutor Tribe Minmatar Republic
6
|
Posted - 2013.05.28 16:18:00 -
[14] - Quote
**** this gay forum, it ate my post. Will rewrite it tomorrow. In an external editor. And make backups. And put it on pastebin. And link it here. Because the forum is gay and those who made it should feel gay.
Basically built new wine on lubuntu 13.04 amd64, the official guide is a bit outdated, but works with little modifications.
PS: sorry if I offended actual gauys by comparing them to the forum developers. Probably I went to far there. No, dear homosexuals, you aren't this forum developers. I'm very sorry. |
Torgeir Hekard
Brutor Tribe Minmatar Republic
6
|
Posted - 2013.05.29 08:34:00 -
[15] - Quote
Ookay. So, building wine on amd64 ubuntu.
I've got myself a new laptop, and it refuses to embrace my ODD-HDD adapter, so I can't plug my old SSD instead of the DVD drive. On the positive side, it enabled me to do a fresh install of lubuntu 13.04 amd64, and now I know kungfu^W how to cross-compile wine on ubuntu. On a less pleasant note I also know how to stop doomsday clock ticking on WD drives, how to use bumblebee and that Intel RapidStart is a ***** and will corrupt your Windows 8 filesystem if you even think about dualbooting. But that's another story.
We'll be using the aforementioned official guide Except when it doesn't work. We'll also use the chroot method because it's neat and tidy and doesn't leave us with a pack of wild symlinks creeping everywhere.
1. Install schroot and debootstrap sudo apt-get install schroot debootstrap
2. Make a schroot config for our victim sudo vim /etc/schroot/chroot.d/raring_i386.conf
Quote:[raring_i386] description=Ubuntu Raring personality=linux32 directory=/srv/chroot/raring_i386 root-users=your_username type=directory users=your_username 3. Reboot because you don't know how to exit vim.
4. Debootstrap the new system sudo mkdir -p /srv/chroot/raring_i386 sudo debootstrap --variant=buildd --arch=i386 raring /srv/chroot/raring_i386 http://archive.ubuntu.com/ubuntu/
5. Feed it cookies^W apt sources sudo cp /etc/apt/sources.list /srv/chroot/raring_i386/etc/apt/
6. NOW ENTERNG CHROOT schroot -c raring_i386 -u root
#HERE BE INSIDE CHROOT AS THE DEMIURG AND MASTER OF CELESTIAL SPHERES 7. Install minimal system and useful stuff (note GÇö this is where the official guide is outdated: add-apt-repository was in another castle. You can find it by doing apt-file search filename. Only you need to install apt-file first. The below one works for 13.04) apt-get install ubuntu-minimal apt-get install software-properties-common
8. Add wine ppa, though it's useless because later add-apt-repository ppa:ubuntu-wine/ppa
9. Grab build deps apt-get update apt-get build-dep wine
This will fail. Because wine=wine1.5, and build deps aren't specified for wine1.5. So instead you use crunches and fetch build deps for the earlier wine version. Apparently it's sufficient.
apt-get build-dep wine1.4
10. Now install git apt-get install git
11. Now, a little schroot magic. Schroot is kind enough to link your home directory into the chrooted environment, so when you enter schroot, you work in your own home. On the positive side, we can build wine directly into our home directory. On the negative side, we are root now. I find it kinda sad to wander my home diectory as an omnipotent being that creates indestructible walls for ***** and giggles and leaves dealing with them to mere mortals. So get out of chroot, stalker, and enter as a proper user.
exit mkdir ~/wine-git schroot -c raring_i386 -u username
12. Pull wine from git git clone git://source.winehq.org/git/wine ~/wine-git
13. patch wine cd ~/wine-git cp ~/Downloads/awesomium-partial.diff ./ patch -p1 -i awesomium-partial.diff
14. configure wine ./configure GÇöprefix=/home/username/wine-bleeding-edge
15. brew wine make -j[Number-of-cores] Go drink tea, eat cake, feed turtle, procrastinate, play your Gibson Les Paul Sunburst.
16. Several aeons have passed. You probably even tried to tackle one. The wine has finally brewn. Now install it make install
Note that it will install it into the prefix directory, which is in your home (if you specified it properly), so it does not need root priveleges to install, and it will appear in your home outside chroot
17. Now exit chroot and fail to start wine. It needs it's dependencies resolved outside the chrooted environment. The easiest way is to install wine from repos (either native or ppa). It won't screw up your custom-built wine. exit sudo apt-get install wine
18. Run your pimped state-of-the-art fine tuned wine as /home/username/wine-bleeding-edge/bin/wine
19. ?????
20. PROFIT |
Frazier
Interstellar Geographic Society
4
|
Posted - 2013.05.29 13:16:00 -
[16] - Quote
On Debian you can use this guide: http://verahill.blogspot.com.au/2013/05/416-wine-1530-in-chroot.html
It will get you a nice .deb package of wine for later use or installs on other machines. Don't forget the SSL patch mentioned above since it is missing in the guide obviously. Using this method (namely checkinstall to create the .deb file) you can, and should, specify a different install directory for wine. Using "configure --prefix=/your chosen path" will also affect the .deb file setup path. Additionally you should alter the package name at checkinstall when the package properties are shown to you. (point 2) Use something like "wine_eve" or so. If you don't do this the package manager will remove the already installed "wine" package.
Oh, and to install the package on your amd64 host system, you need to specify the --force-architecture flag of dpkg. |
Dryvin Marstolt
Locknova Excavation Service
1
|
Posted - 2013.05.30 07:34:00 -
[17] - Quote
Just wanted to chime in that the PlayOnLinux wine-1.5.28-Guildwars2 apperas to be working properly. I just used PlayOnLinux to download the Wine version, then used it to run EVE. Didn't actually install the game in PlayOnLinux.
Since I use Arch x86_64, this was the most convenient way to do this, since installing patched versions of Wine is a pain due to needing 32 bit libraries for everything, or a chroot jail.
Just used: env WINEPREFIX=/opt/EVE_Online WINEARCH=win32 ~/.Playonlinux/wine/linux-x86/1.5.28-GuildWars2/bin/wine /opt/EVE_Online/drive_c/Program\ Files/CCP/EVE/eve.exe
Works beautifully. Will be curious to see if using the slightly older version of Wine corrects the crashes I've been seeing for the past week or two. |
Kismeteer
GoonWaffe Goonswarm Federation
276
|
Posted - 2013.05.30 14:51:00 -
[18] - Quote
Forget the launcher, just go straight to the exefile.exe instead. You just need the launcher to occasionally update. Check details at the end of the Ubuntu Howto thread. https://forums.eveonline.com/default.aspx?g=posts&m=3072510#post3072510 |
Dryvin Marstolt
Locknova Excavation Service
1
|
Posted - 2013.05.30 18:59:00 -
[19] - Quote
While this is true at the moment, they will eventually be removing the ability to login that way. The devs have confirmed that this is the case. So a more long term solution is still going to be necessary. |
Marsan
Caldari Provisions
108
|
Posted - 2013.05.31 02:47:00 -
[20] - Quote
Has anyone noticed that the launcher work once after every patch? It seem like to me everytime I patch the game I try the launcher to see if things have improved, and it works. Then I log out and try again only to be met with failure. Former forum cheerleader CCP, now just a hopeful small portion of the community. |
|
Shaman Mystic
Viziam Amarr Empire
0
|
Posted - 2013.05.31 05:32:00 -
[21] - Quote
Hoping this hasn't been said already. The new launcher works for me as long as I clear the launcher cache on each start up to load the User name and password bars.
Ubuntu 12.10 Wine 1.5.31 |
Woo Mi
Federal Navy Academy Gallente Federation
3
|
Posted - 2013.05.31 08:24:00 -
[22] - Quote
After the latest launcher version the launcher now successfully exits without hanging for me. It also starts up successfully every time, without a need to kill its cache. I am using wine 1.5.31 + the ssl certificate patch from the other thread. |
Goompas Teron
Hedion University Amarr Empire
0
|
Posted - 2013.06.07 16:51:00 -
[23] - Quote
Dryvin Marstolt wrote:Just wanted to chime in that the PlayOnLinux wine-1.5.28-Guildwars2 appears to be working properly. I just used PlayOnLinux to download the Wine version, then used it to run EVE. Didn't actually install the game in PlayOnLinux.
Since I use Arch x86_64, this was the most convenient way to do this, since installing patched versions of Wine is a pain due to needing 32 bit libraries for everything, or a chroot jail.
Just used: env WINEPREFIX=/opt/EVE_Online WINEARCH=win32 ~/.Playonlinux/wine/linux-x86/1.5.28-GuildWars2/bin/wine /opt/EVE_Online/drive_c/Program\ Files/CCP/EVE/eve.exe
Works beautifully. Will be curious to see if using the slightly older version of Wine corrects the crashes I've been seeing for the past week or two. Im using arch64 too. Do you have working ingame browser? Or maybe anyone else have working ingame browser and can share installation details(system, wine version) |
Woo Mi
Federal Navy Academy Gallente Federation
3
|
Posted - 2013.07.18 22:11:00 -
[24] - Quote
I am still running 1.5.31 successfully. Can anyone confirm/deny that the awesomium patch is still needed for wine 1.6? |
Cipher Jones
The Thomas Edwards Taco Tuesday All Stars
741
|
Posted - 2013.08.06 20:01:00 -
[25] - Quote
Shaman Mystic wrote:Hoping this hasn't been said already. The new launcher works for me as long as I clear the launcher cache on each start up to load the User name and password bars.
Ubuntu 12.10 Wine 1.5.31
What files? just the logs?
Eve is Real |
Cipher Jones
The Thomas Edwards Taco Tuesday All Stars
741
|
Posted - 2013.08.06 20:13:00 -
[26] - Quote
Woo Mi wrote:I am still running 1.5.31 successfully. Can anyone confirm/deny that the awesomium patch is still needed for wine 1.6?
To run the client I did not need it, needed only vcrun2005, 08, 10, and corefonts. Slackware 14.
Eve is Real |
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |