Upgraded AMD video card launcher is fine but client crashes

Running linux mint mate, EVE has been working great for a long time but after upgrading my video card I’m getting:

STACKTRACE #1 logged at 02/11/2022 04:26:43 : Exception in stack-trace-all, shutdown bombing

Common path prefix = c:/buildagent/work/d2d8a22a74178531/eve/release/release

Traced at:
<pre>/carbon/common/lib/autoexec.py(137) <module>
<pre>/packages/monolithsentry/minidump.py(17) set_sentry_crash_key
<pre>/packages/monolithsentry/tags.py(16) get_tags
<pre>/packages/monolithsentry/tags.py(91) get_client_tags
<pre>/packages/gpuinfo/__init__.py(1) <module>
<pre>/packages/trinity/__init__.py(22) <module>
<pre>/packages/trinity/_singletons.py(14) <module>
<pre>/packages/trinity/_trinity.py(86) _ImportDll
<pre>/packages/trinity/_trinity.py(48) _RobustImport
<pre>/packages/trinity/_utils.py(9) Quit
<pre>/packages/logmodule/__init__.py(618) Quit
reason = 'Failed to import _trinity_stub ("ImportError(\'No module named _trinity_stub\',)")'

Thread Locals: session was None
Stackhash: -1120044611
Reported from: logmodule
STACKTRACE END

I have done a fair bit of searching but haven’t come up with anything that has helped. Any thoughts as to how I could fix this? Any help appreciated.

This doesn’t look like a video driver bug :frowning: was this on Sisi or TQ? What version of Wine are you running?

mearhard@Monolith:~$ wine --version
wine-7.0

I also updated amdgpu and vulkan… I was trying TQ. I can try SISI.

edit: Very much appreciate you replying.

Actually I do see gpuinfo/__init__.py being called now, so it could just be a misleading error message. What card did you get specifically?

I got the Asus Tuf RX6800XT 016G Gaming card.

Edit: One thing to note: I had an MSI Vega56 card before, and it was working on that one, and it was also working on a 580 that I have. Both on the same linux Mint system I’m trying to get the 6800xt working on.

Have you tried running EVE from terminal with wine evelauncher.exe and looking if you find anything in there that might help to locate the error?

Interesting, I don’t have an “evelauncher.exe”… I basically uncompressed my version of the launcher and ran evelauncher/evelauncher.sh:

#!/bin/sh
appname=`basename "$0" | sed s,\.sh$,,`

dirname=`dirname "$0"`
tmp="${dirname#?}"

if [ "${dirname%$tmp}" != "/" ]; then
dirname="$PWD/$dirname"
fi
LD_LIBRARY_PATH="$dirname:$LD_LIBRARY_PATH"
export LD_LIBRARY_PATH
export QTDIR=$dirname
export QT_PLUGIN_PATH=$dirname/plugins
export GRPC_DEFAULT_SSL_ROOTS_FILE_PATH=$dirname/roots.pem
"$dirname/$appname" "$@"

I’m not running it in steam. Steam doesn’t work at all. Funny story though- I did a new install of ubuntu on an unused partition, uncompressed my evelauncher tar.gz and it worked easy peasy. So I know it works. I just need to figure out how I’ve messed up my primary linux install to stop it from working.

Ah, looks like you’re using the native launcher. It’s been unmaintained for awhile I believe and may stop working altogether in the near future–I’d recommend migrating to steam or the Windows launcher for future proofing. I unfortunately can’t help troubleshoot the Linux launcher as I don’t use it. Note that for steam you probably have to tell it to use an experimental wine build, as there were some showstopping bugs that were fixed late in the 6.x cycle. I don’t know if they’ve rebased to 7.0 yet but that should have all the fixes.

Here’s a quick step by step I wrote awhile back to help people get the Windows launcher working with DXVK in case you’re interested: New launcher... new Linux error? - #375 by Renard_DuGaulle

Thanks mate, I’ll give that procedure a go.

I’ve been working on getting your solution working, and I’m getting closer:

I can now get the launcher to come up but if I try to log in I get a message: could not open login window check internet and try again". Only thing that comes up in the logs is:

LoadFailed ..\..\..\src\customwebpage.cpp in CustomWebPage::onLoadFinished : Couldn't open https://login.eveonline.com/account/logoff?lang=en&ReturnUrl=%2Fv2%2Foauth%2Fauthorize%3Fclient_id%3DeveLauncherTQ%26response_type%3Dcode%26scope%3DeveClientLogin%2520cisservice.customerRead.v1%2520cisservice.customerWrite.v1%26redirect_uri%3Dhttps%253A%252F%252Flogin.eveonline.com%252Flauncher%253Fclient_id%253DeveLauncherTQ%26state%[redacted]%26code_challenge_method%3DS256%26code_challenge%[redacted]%26showRemember%3Dtrue

At least the launcher launches though.

Son of a gun it’s working with the windows installer. Learned a lot about wine today, thanks!

2 Likes

Awesome, glad to hear it!

I spoke too soon…

I am having this weird error where I successfully log in and it says it can’t open a window. Adding a couple of accounts worked, but I have a ton of them left to add.

LoadFailed ..\..\..\src\customwebpage.cpp in CustomWebPage::onLoadFinished : Couldn't open https://login.eveonline.com/account/logoff?lang=en&ReturnUrl=%2Fv2%2Foauth%2Fauthorize%3Fclient_id%3DeveLauncherTQ%26response_type%3Dcode%26scope%3DeveClientLogin%2520cisservice.customerRead.v1%2520cisservice.customerWrite.v1%26redirect_uri%3Dhttps%253A%252F%252Flogin.eveonline.com%252Flauncher%253Fclient_id%253DeveLauncherTQ%26state%[redacted]%26code_challenge_method%3DS256%26code_challenge%[redacted]%26showRemember%3Dtrue

Any thoughts as to what could be wrong?

Hm that’s a tough one, I’ve never seen it before. Do you use a VPN? It looks like some sort of error with the authentication handler

I’ve been getting a lot of those little errors too. It may or may not coincide with a tweak I made to my pfsense – added pfblockerng to knock down ads and stuff. Seems to dislike the certificate it gets from the pfsense. :slight_smile:

On my mint machine, it constantly requests to login to account, then says it couldn’t open the login page but still presents me with accounts to launch and functions fine. On a Garuda (arch base) machine it started failing out entirely. I probably need to take a peek at the dnsbl settings.

I am now getting this error when trying to add new accounts to the launcher. Searching the forums, this seems to have popped up in the past for windows clients even, so not sure what is going on but it’s going to be a PITA to debug. It looks like as a workaround for now, you can go to settings->tools/cache in the launcher and go to server list and click “play on Sisi:”, this will launch the client and let you log in that way.

Well that’s freakin bizarre. I tracked down the function that was throwing the error and as soon as I set a breakpoint, it started working and let me add all my characters…