It looks like this could be a KDE issue. System journal logs for an affected period would help to identify where/what the problem is — the Nvidia driver in particular is quite noisy in journal when something goes wrong.
It looks like this could be a KDE issue. System journal logs for an affected period would help to identify where/what the problem is — the Nvidia driver in particular is quite noisy in journal when something goes wrong.
If there's any kind of additional logging I could fetch or tests I could run I'm completely down to help, just tell me what to do.
I've ran the command "journalctl -f", reproduced the screenshot crash and then copied the log here:
Log.txt
Hope I did everything correctly.
Jan 26 21:04:56 fedora spectacle[49369]: QWaylandGLContext::makeCurrent: eglError: 0x3003, this: 0x7fdce000ec00
Jan 26 21:04:56 fedora spectacle[49369]: QRhiGles2: Failed to make context current. Expect bad things to happen.
Jan 26 21:04:56 fedora spectacle[49369]: KCrash: Application 'spectacle' crashing... crashRecursionCounter = 2
Jan 26 21:04:56 fedora spectacle[49369]: Failed to create RHI (backend 2)
Jan 26 21:04:56 fedora spectacle[49369]: Failed to initialize graphics backend for OpenGL.
eglMakeCurrent() in Spectacle fails with EGL_BAD_ALLOC, i.e. that auxiliary buffers cannot be allocated. I wonder whether the system runs out of VRAM or something.
I wonder whether the system runs out of VRAM or something.
Good catch! I just checked the Vram usage and it was fluctuating between 7.9 and 8Gb (Out of an available 8Gb) which is odd as when I ran windows on the same machine on the same settings it was significantly lower. Lowering the settings to medium does result in the Vram usage dropping to a comfortable 6Gb and none of the issues I had outside of the game occur. As it's stable at 5.8-6Gb it doesn't seem like the issue is a memory leak.
I'm not sure if I should close the thread or if the unusually high Vram usage is something worth looking in to. The game's requirements page does suggest 8Gb should be enough to run it at max settings.
Either way, thanks a bunch!
ge-proton10-26x1 2026-01ge-proton10-28x1 2026-01
Compatibility Report
System Information
I confirm:
steam-3247750.log
Symptoms
I'm sorry in advance for a lackluster report but I'll do my best.
After loading in to the HUB (or being in any mission) the following issues occur while the game is running:
All of these issues resolve themselves shortly after the game has been turned off and I have been unable to reproduce the issues with any other game. There are also other issues like discord restarting itself but as that's not as reproducible I'm not as confident that that's the games fault.
Reproduction
Start the game, load in to the hub or any mission, attempt any of the things described in the Symptoms list. EX: Attempt to take a screenshot with spectacle or ksnip.
Again, sorry for not being more precise but I genuinely have no clue what's happening and wish you the best luck trying to find out.
Best regards -TwistedBOLT