Client start exception after today update - steam [SOLVED]

No dice here. Running the Steam launcher on pop-os 21.04.

I tried Proton Experimental, 6.3, 5.13, and 5.0. It was last working on 5.0 yesterday, but it wont launch today.

Ill try reinstalling and see if that helps.

1 Like

Well done CCP.
I get Linux isnt supported, but can we see the numbers you have on how many users do play this game on Mac and how many on Linux?

And dont tell you do not have those numbers cause you do

No luck on reinstall. Also tried Proton 6.18-GE2 with the same results. I just get stuck on the CCP splash screen.

Note to self, make a backup of the copypasta file before reinstalling.

image

Using:
ā€“vanilla wine 6.0.1,
ā€“windows launcher version 1850297
ā€“copying launchdarkly_client.pyd from the sharedcache/tq/bin64 folder to sharedcache/tq folder and setting read only.

Eve now runs fine again.

2 Likes

I have a different problem before I can even try to launch eve. When have typed my login name and password to the launcher login prompt, it complains ā€œCould not open login window. Check internet connection and try again.ā€ Internet is obviously working ok because every time I try this, ccp sends me a verification code email. So apparently the ā€˜login windowā€™ it is talking about is the popup window that asks the verification code.

I can run sisi client by using the login prompt in the client itself but if I try this with tq client, it just complains that I should use the launcher to log in.

This exact same problem happens with the latest launcher version, several older versions I tried that have worked before and even with the unofficial native linux launcher. But in the linux launcherā€™s case I donā€™t get the email.

Iā€™m using Ubuntu 20.04 and winehq-devel 6.19.

Thanks! it works!!!

On Mint 20.02 using steam proton 5.10
Tried all the methods working my way down this thread. Confirm copying launchdarkly_client.pyd to the following finally made the client open properly:

/home/username/.steam/debian-installation/steamapps/common/Eve Online/SharedCache/tq

I also set read only.

1 Like

I found out that the issue has been detected few weeks agoā€¦
https://bugs.winehq.org/show_bug.cgi?id=51821

I applied the proposed patch on proton-ge and it resolved my issue. I will upload it somewhere once the properbuild is done

Iā€™m playing in Linux Mint 20.2 via Steam. I was on Proton 5.10 but tried Proton-GE for this. No luck. I have my games installed on a separate SSD, but even putting the launchdarkly_client.pyd into the correct folder there (SteamLibrary/steamapps/common/Eve Online/SharedCache/tq) didnā€™t work. Iā€™m not technically proficient enough to know how to apply a patch to Proton-GE or I would give that a try, too, but for now, Iā€™m more or less locked out of New Eden. :frowning:

Itā€™s building. will take a little time. Hope I will manage to stay awake until

Hope it will work for you. See you ingame o7

Sadly no :frowning:

The path problem may be a bit deeper here when you use linux launcher with ā€œuse custom wineā€ pointing to system wine installation:

[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/_evelocalization.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/x86_64-unix/_geo2.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/_geo2.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/x86_64-unix/_pyfsd.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/_pyfsd.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/x86_64-unix/_spacemouse.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/_spacemouse.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/x86_64-unix/_audio2.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/_audio2.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/x86_64-unix/_videoplayer.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/_videoplayer.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/x86_64-unix/_destiny.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/_destiny.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 327005] openat(AT_FDCWD, "/usr/lib/wine/x86_64-unix/_eveplanetresources.dll.so", O_RDONLY) = -1 ENOENT (No such file or directory)

As you may imagine, those files are not present in /usr/lib -

/wineenv/drive_c/tq/bin64/spacemouse.pyd
/wineenv/drive_c/tq/bin64/_spacemouse.dll
/wineenv/drive_c/sisi/bin64/spacemouse.pyd
/wineenv/drive_c/sisi/bin64/_spacemouse.dll

Fortunately, the patch by @Renard_DuGaulle should solve this as well since it all looks to be related to loading dlls from relative paths.

where is this patch? I donā€™t see it in this thread, and have local wine.

Update: I see a Proton patch with some instructions from github, but that didnā€™t work for me. Iā€™ve tried moving the launchdarkly_client.pyd file as instructed, with no luck.

Any other advice? Iā€™m on gentoo linux, using the Windows client under CCP Bartenderā€™s native launcher

Itā€™s weird.
I didnā€™t do anything else.

Hi Peeps, I finally got this working for me on POP-OS just copy the launchdarkly_client.pyd from .steam/debian-installation/steamapps/common/Eve Online/SharedCache/tq/bin64 to one directory up (tq) and set permissions to readonly readonly readonly - then it seems to all be sorted.

I canā€™t use the Steam launcher. Itā€™s horribly slow and unstable. Certain accounts donā€™t start at all, others freeze, etc. Has anybody gotten the Windows launcher to install on Linux?

UPDATE: this bugreport includes a patch that should fix the issue. How do I install it?

That is the only way I have played eve - windows launcher, vanilla wine. The only issue is that you have to use an older launcher and make sure eve doesnā€™t update the launcher (only let it update the game) unless you have a version of wine that works with the newest launcher.

WFM. Great thanks to everyone involved in finding this fix!

fix not work with kubuntu 20.04/steam/proton5/6/6.19GE