You are not logged in.
Pages: 1
First off, I am not using 64bit.
Lately, running Wine and Eve-Online is fine.
However, when I Quit from the game menu...it freezes.
I actually have to x-it-out (the wine window), and a window pops up with
"A simulated logout was in the process and is not responding".. or some such thing
and then I can terminate it and get my desktop back.
I've seen several posts about this, but no resolve.
Last edited by Kilzool (2014-07-13 09:58:09)
Offline
Use WINEDEBUG to provide more information. Do you run EVE in an emulated virtual desktop?
I actually have to x-it-out
[...]
I've seen several posts about this, but no resolve.
You mean the close button? Link them, might be helpful.
wine --versionOffline
I will try to use the WINEDEBUG to post more info.
Yes I use this command to run it:
wine explorer /desktop=eveA,1400x1050 "C:\\Program Files\CCP\EVE\eve.exe" >/dev/null 2>&1And my wine version is:
wine-1.7.19When I QUIT the eve game, it freezes.. (as in, it doesn't exit). I have to X out the window for the popup to
appear to terminate the game.
Offline
When I QUIT the eve game, it freezes.. (as in, it doesn't exit).
I understood that.
I have to X out the window for the popup to
appear to terminate the game.
If you have to close the wine window, just write so. Another way to kill wine is:
env WINEPREFIX="your-prefix" wineserver -kX out the window
is gibberish to me, and made me think you have to get out of Xorg or use xkill.
What is the architecture of your system and wine you are using? Have you tried older versions/different architecture (x32) of wine? You could use PlayOnLinux to check these out more comfortably. Please provide links to other posts you mentioned.
Offline
For what it's worth I had this exact problem with EVE when using wine from the repos. I switched to aur/wine-d3dstream-git and the problem is gone.
This is sadly the only version it throws at me:
$ wine --version
cs-0.8EDIT: I just realised that I didn't use to have this problem with Wine a couple of weeks ago, sadly I can not quite remember which version I used back then. But looking in my pkg cache, it seems like it might have been 1.7.16. You could try to revert to an earlier version, and see if the problem persists.
Last edited by Sekre (2014-05-19 20:05:48)
Offline
I have the same issue on my desktop which has an nvidia video card, but not on my laptop, which has an Intel HD5000.
Which video card do you have? (I'm just wondering if it might be relevant, since it's the only noticable difference between my two PCs).
Offline
Nvidia 9400 GT -- so I wonder if the solution, or quick fix, is to downgrade WINE versions to......
some version earlier than 1.7.16 ???
Offline
PoL uses wine version 1.5.26. Or at least used to. Use the version that works best for you.
Last edited by emeres (2014-06-03 14:53:38)
Offline
Nvidia 9400 GT -- so I wonder if the solution, or quick fix, is to downgrade WINE versions to......
some version earlier than 1.7.16 ???
I'm not sure that wine is the issue, since it's not reproducible with Intel video cards. Maybe it's an nvidia issue.
Offline
Kilzool wrote:Nvidia 9400 GT -- so I wonder if the solution, or quick fix, is to downgrade WINE versions to......
some version earlier than 1.7.16 ???I'm not sure that wine is the issue, since it's not reproducible with Intel video cards. Maybe it's an nvidia issue.
Yep, it's an nVidia thing. I just switched from open-source radeon drivers to a new binary-fuelled nVidia card and sure enough, EVE started locking up on shutdown immediately. Also using Wine 1.7.19. When I get home tonight I'll roll it back a few versions and see if I can't find a fix.
Last edited by andrewd18 (2014-06-04 13:30:43)
Offline
Rolled back to 1.7.16, 1.7.15, and then down to 1.6.2. All crash. The EVE-O forums are implying it's an Arch specific bug.
I don't even need to log in to get it to crash; just start the game from ExeFile, hit ESC, then quit. Hang.
Last edited by andrewd18 (2014-06-04 23:16:20)
Offline
Rolled back to 1.7.16, 1.7.15, and then down to 1.6.2. All crash. The EVE-O forums are implying it's an Arch specific bug.
I don't even need to log in to get it to crash; just start the game from ExeFile, hit ESC, then quit. Hang.
Since you seem to have more time for this than me: can you try rolling back the nvidia driver? Seeing as how it's only reproducible on nvidia, I'm betting the issue is on that end.
Also, as a workaround, I've always had this script (which also works when eve crashes horribly at any other time):
#!/bin/sh
export WINEPREFIX=$HOME/wine/prefixes/eve
wineserver -kNasty, but efficient.
Last edited by hobarrera (2014-06-05 17:08:44)
Offline
Since you seem to have more time for this than me: can you try rolling back the nvidia driver? Seeing as how it's only reproducible on nvidia, I'm betting the issue is on that end.
Unfortunately I cannot. I do not have older versions of the nvidia package on my machine, and I cannot use one of the older 304, etc. packages because I'm running a 660, which will not work with those driver versions.
Offline
hobarrera wrote:Since you seem to have more time for this than me: can you try rolling back the nvidia driver? Seeing as how it's only reproducible on nvidia, I'm betting the issue is on that end.
Unfortunately I cannot. I do not have older versions of the nvidia package on my machine, and I cannot use one of the older 304, etc. packages because I'm running a 660, which will not work with those driver versions.
Did you try the aur package, I suggested earlier?
aur/wine-d3dstream-git
I compiled this again two-three days ago, and am seeing good effect in EVE in particular, with an nVidia 660, both with and without bumblebee.
Offline
Did you try the aur package, I suggested earlier?
aur/wine-d3dstream-gitI compiled this again two-three days ago, and am seeing good effect in EVE in particular, with an nVidia 660, both with and without bumblebee.
I use PlayOnLinux to manage my WINE prefixes. It turns out the 1.7.18-CS-0.8-f1cf438 build is a build of the HEAD of that repository. So I switched to that WINE version, and yes, the problem is solved.
I also created a CSMT-enabling registry key. To do so, launch regedit, browse to HKEY_CURRENT_USER/Software/Wine/Direct3D, right click and select New > String Value “CSMT”. Then, double click and set the string to “enabled”.
Thank you!
Offline
Sekre wrote:Did you try the aur package, I suggested earlier?
aur/wine-d3dstream-gitI compiled this again two-three days ago, and am seeing good effect in EVE in particular, with an nVidia 660, both with and without bumblebee.
I use PlayOnLinux to manage my WINE prefixes. It turns out the 1.7.18-CS-0.8-f1cf438 build is a build of the HEAD of that repository. So I switched to that WINE version, and yes, the problem is solved.
I also created a CSMT-enabling registry key. To do so, launch regedit, browse to HKEY_CURRENT_USER/Software/Wine/Direct3D, right click and select New > String Value “CSMT”. Then, double click and set the string to “enabled”.
Thank you!
Neat!
Then the million isk question is, "Why does the CSMT build not display this issue?"
I just might have to put on my scuba gear and go diving into this some more when the schedule permits.
Offline
Sekre wrote:Did you try the aur package, I suggested earlier?
aur/wine-d3dstream-gitI compiled this again two-three days ago, and am seeing good effect in EVE in particular, with an nVidia 660, both with and without bumblebee.
I use PlayOnLinux to manage my WINE prefixes. It turns out the 1.7.18-CS-0.8-f1cf438 build is a build of the HEAD of that repository. So I switched to that WINE version, and yes, the problem is solved.
I also created a CSMT-enabling registry key. To do so, launch regedit, browse to HKEY_CURRENT_USER/Software/Wine/Direct3D, right click and select New > String Value “CSMT”. Then, double click and set the string to “enabled”.
Thank you!
If it worked on an older release but not a new one, would you mind reporting the regression on the wine bug tracker? ![]()
Offline
Thanks for the information. I originally posted this on the EVE forums, but didn't have much time to follow up on it. Glad to see some useful information has cropped up.
I installed the aur/wine-3d3stream-git which alone did not resolve the problem.
I had to enable CSMT as andrewd18 listed. I didn't have a key for Direct3D so I just created the key and then set the string value.
The application now closes but if you run it from cli you can see that it still errors out with "Terminating process by request - returning 0". This hangs until you CTRL+C or close the terminal. This isn't a big deal, but suggests that while it's a perfectly reasonable workaround, it's not a complete resolution. Definitely saves me a lot of headache, however, and I thank everyone that shared information here.
Offline
Did you try the aur package, I suggested earlier?
aur/wine-d3dstream-git
I tried this... but the same thing is happening.
When I QUIT the game (EVE ONLINE), it doesn't quit. So I waited like 2 minutes to
see if it will "time out" and close.. but doesn't.
So that 1.5 hrs to compile wine-d3dstream-git didn't help.
Nvlock could be the problem. Not sure though.
I do have an NVIDIA card...and its not the proprietary driver, its the
driver from the pacman. I do not play any other game on wine.
Offline
I use PlayOnLinux to manage my WINE prefixes. It turns out the 1.7.18-CS-0.8-f1cf438 build is a build of the HEAD of that repository. So I switched to that WINE version, and yes, the problem is solved.
I also created a CSMT-enabling registry key. To do so, launch regedit, browse to HKEY_CURRENT_USER/Software/Wine/Direct3D, right click and select New > String Value “CSMT”. Then, double click and set the string to “enabled”.
Thank you!
What is this CSMT string mean in regedit, for Direct3D?
What is that suppose to do?
Offline
What is this CSMT string mean in regedit, for Direct3D?
What is that suppose to do?
If you don't enable CSMT in the WINE Registry, it won't activate the CSMT threading. Therefore, it will act like default WINE. You should retry your -git build with that registry key and see if it fixes the problem.
Offline
I am marking this solved.
Today, I did an pacman upgrade, and it upgraded...
[2014-07-13 05:33] [PACMAN] upgraded nvidia-utils (337.25-3 -> 340.24-1)
[2014-07-13 05:33] [PACMAN] upgraded nvidia-libgl (337.25-3 -> 340.24-1)
[2014-07-13 05:34] [PACMAN] upgraded nvidia (337.25-4 -> 340.24-1)
[2014-07-13 05:34] [PACMAN] upgraded wine (1.7.21-1 -> 1.7.22-1)And when I run eve-online with wine, and quit, it now quits properly.
Thanks to the coders, maintainers, and those who fixed the issue.
Offline
I am marking this solved.
Today, I did an pacman upgrade, and it upgraded...
[2014-07-13 05:33] [PACMAN] upgraded nvidia-utils (337.25-3 -> 340.24-1) [2014-07-13 05:33] [PACMAN] upgraded nvidia-libgl (337.25-3 -> 340.24-1) [2014-07-13 05:34] [PACMAN] upgraded nvidia (337.25-4 -> 340.24-1) [2014-07-13 05:34] [PACMAN] upgraded wine (1.7.21-1 -> 1.7.22-1)And when I run eve-online with wine, and quit, it now quits properly.
Thanks to the coders, maintainers, and those who fixed the issue.
I can confirm this! ![]()
Offline
As wine multimedia has also been updated I presume the fix is in there too?
I'm building it now so if no-one knows I'll edit this post when it finishes building.
Offline
Pages: 1