So far it looks to be a configuration issue more than anything.
After putting in winbind, I can get it to launch only if I manually run the launcher from the command line. If I run it via Lutris GUI, it fails.
Just need to narrow down what the difference is between the 2 & we might get somewhere
Currently still WIP. Will try to keep everyone posted, if I manage to find what is missing
Steam is a bit harder, you’ll need a patched version of Proton (Proton includes Wine amongst other things) in order to run it. But it’s not clear yet how or if there is a fix for Wine let alone Proton. Sorry…
What did you do when you “put in winbind”? I’m on arch without lutris, and I have samba which is supposed to include support for winbind. Is there something you did in winecfg or did you just install a package via apt?
Soon to follow: stop supporting MacOS and after that stop supporting Windows.
This was via apt ( as i’m running Ubuntu 20.04 )
Not entirely sure if that’s the actual issue so far - still investigating the differences between my working & non-working setups
You may also want to check whether you have native or builtin MSVC runtime (and which version).
That’d be helpful. I’m currently not using any MSVC runtimes, confirmed the winbind service is running on my machine and I’m getting the stack overflow.
I’m not installing Windows only to run EVE.
Here’s the thing - i’m launching the same prefix each time, just via different methods.
Just to make sure it wasn’t different versions of wine, both use the same one ( currently - staging ). Definitely something that Lutris is adding to the environment is messing with things…
Can you check the prefix with winecfg and list what your overrides are? I want to try to replicate on my box so we can fix it for non-Lutris wine as well
Ubuntu , mine seems to be working fine so far
mind sharing your configuration? Might help in identifying what others are missing
Small update - managed to trace my specific issue down to a DLL override done by lutris for d3d11=n ( presumably as i’m using the DXVK based installer? ) - removing this appears to get everything running.
Still digging as to why though…
EDIT - not all the time, still occasionally fails - probably a red herring…
EDIT 2 - My hunch appears to be the case after all. I did a clean install without DXVK and ESYNC and it appears to launch fine. Just need to understand why…
I am currently installing eve in lutris, the launcher launches, but unable to login. Possibly due to the keystore changes.
Could you share your lutris installation config?
Everything launches fine via SteamPlay if I force the use of Proton 5.0-10.
Seems that i’m in the same boat as yourself now.
removing the DXVK at least got me to get the launcher going, but so far - logging in causes a crash
Managed to get a stack trace of teh crash when attempting to login:
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
EIP:7b010f56 ESP:0084da44 EBP:0084dab8 EFLAGS:00200246( - -- I Z- -P- )
EAX:0084da50 EBX:0084db14 ECX:00000008 EDX:0084dae8
ESI:e06d7363 EDI:42a20488
Stack dump:
0x000000000084da44: 0084daa80084da60 e06d73637b028246
0x000000000084da54: 0000000000000001 000000037b010f56
0x000000000084da64: 0084db1419930520 003e2bf842a20488
0x000000000084da74: 0084dae80084daa0 000000007b016716
0x000000000084da84: 000e000c00000000 003e2bf8003e2c00
0x000000000084da94: 0084dac00084daa0 000000007b60bc9c
0x000000000084daa4: 0084dae87b61bf20 199305200084dacc
0x000000000084dab4: 0084daf400000000 00000002429ba116
0x000000000084dac4: 429ba1160084daf4 00000001e06d7363
0x000000000084dad4: 0084dae800000003 7b60bc9c7b61bf20
0x000000000084dae4: 199305200084db14 42a204880084db14
0x000000000084daf4: 429223387b60dd08 42a204880084db14
Backtrace:
=>0 0x000000007b010f56 EntryPoint+0xffffffffffffffff() in kernelbase (0x000000000084dab8)
1 0x00000000429ba116 EntryPoint+0x820() in cryptopp (0x000000000084daf4)
2 0x0000000042922338 EntryPoint+0xffffffffffffffff() in cryptopp (0x000000007b60dd08)
3 0x0000000025ff5dec (0x000000008b55ff8b)
0x000000007b010f56 EntryPoint+0xffffffffffffffff in kernelbase: subl $4,%esp
Wine-dbg>bt
Backtrace:
=>0 0x000000007b010f56 EntryPoint+0xffffffffffffffff() in kernelbase (0x000000000084dab8)
1 0x00000000429ba116 EntryPoint+0x820() in cryptopp (0x000000000084daf4)
2 0x0000000042922338 EntryPoint+0xffffffffffffffff() in cryptopp (0x000000007b60dd08)
3 0x0000000025ff5dec (0x000000008b55ff8b)
Does look crypto related as it’s happening in cryptopp, will keep digging
Out of interest - does it look any different if you don’t get the launcher to save your account details?
Was hoping to see if we could get around it, but so far no luck…
Nope, appears to be the same crash when you don’t save account info. Good thought though!