General inquiry regarding error message

General system Gaming, sound and video
1

Hello,

I haven’t had too many problems regarding gaming specific problems on my machine, but I did have an question about what this means from a troubleshooting perspective.

image
image332×258 23 KB

Attached is a popup message I received after attempting to boot Hearthstone. My normal process is that I have the Battle.net client launch-able via Steam, which is the same way I boot other launchers like HoyoPlay etc, and then I’m just able to launch Hearthstone regularly. There was an update to the Hearthstone game itself recently, but I haven’t had issues in the past with launching after an in-client update. From looking online and from other games, it seems like a problem with either a corrupt Visual C++ library or the update bricking connectivity to like, Vulkan shaders or something and triggering a force close. Any tips? system info below

Operating System: EndeavourOS
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.7-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor
Memory: 32 GiB of RAM (30.4 GiB usable)
Graphics Processor 1: AMD Radeon RX 9070 XT
Graphics Processor 2: AMD Ryzen 7 7800X3D 8-Core Processor
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7E62
System Version: 2.0

2

for context i did try a fresh install of the game, which prompted the same message, a forum board for a separate game had apparently similar issues solved via reinstall, so I would figure that I would at least try that

3

A couple of things:

  1. try different versions of Proton
  2. try running Plasma with X11
4

okay so I normally ran the Battle.net launcher in Proton Experimental, running it in Proton Hotfix got the game to boot. Thanks!

5

Proton Glorious Eggroll (ProtonGE) is another Proton option well worth trying too.

6

i do already have GE installed, but I typically havent used it specifically for non-steam game launchers

7

Between the three mentioned so far, it’s the least Steam option, in that it’s unofficially developed by someone not affiliated with Valve :sweat_smile:

But that’s all good, I don’t think any of that really matters. The important thing is you found a solution that works :wink::+1:

8

Just out of curiosity (and nobody else mentioned it) why are you running a terribly outdated system on a rolling distro ?

9

Good catch @keescase :+1:

10

Thanks yes I had to check if this was a old topic from some time ago or had gone back in time or something like that :grinning_face:

11

i hadnt been at my computer for a couple months (work) and none of my immediate family are Linux-oriented to the point of being able to update for me, so as a result I’ve been putting it off since I got back

12

That’s understandable @Schmeatus :+1:

If you hit any issues again, you might try running an update first (particularly if you’re overdue), it may be simply resolved with that.

13

that isn’t to say I’m particularly Linux-oriented myself, EndeavourOS is my first rolling distro, so I’ve had to troubleshoot an okay amount of things here and there

for something like this where the versions are this far out of date, I believe I was told that I’m supposed to update incrementally? Is that true or can I just run the stock -Syu command that I normally do?

14

I’d suggest a two step approach.

First, update your official packages:

eos-update

Once that completes, restart, then update AUR packages as well:

eos-update --aur

The reason for this, is if you have packages that need to be compiled, it’s important to have an up-to-date build environment, hence the first step.