Warhammer 40k:Darktide crashing to desktop
Having random crashes when playing Warhammer 40k:Darktide
While playing the game entire desktop will ficker to black and then crash to desktop with all open programs, except for terminal, crashing. Terminal will become unresponsive as well. Unable to exit it at all unless I do full restart. I included a screen recording of terminal from post crash. Never seen this behaviour before. So far I've had no issues from any other games, even ones I'd consider more demanding like Cyberpunk or Monster Hunter:Wilds. Any advice would be appreciated as I'm pretty stumped. I verified everything is up to date. I was unable to reproduce this issue while on Windows. Thinking this is KDE crashing or an app within KDE causing the issue, but I'm pulling straws on this one.
22 Replies
So after bashing my head against the wall I changed my proton over to GE-Proton 10-17 and the crashing stopped....
To anyone that does not know how to install on bazzite you can use ProtonUp-QT and then install the above version. Once this is done you need to go into steam, right click the game, select compatibility, enable force use, then scroll down until you find GE-Proton. Will make this as the resolution after a couple of days. Though I find it very odd that the game was able to completely crash KDE while using proton hotfix.
Well nvm game crashes came back
I was able to run the game in windows with no issues. At this point I'm pretty much at a loss. If anyone has any feedback or knowledge it would be appreciated.
Have you tried playing the game with valve's official Proton 9.0-4? That's what I've been playing on.
Yeah, that' what I was orginally have constant crashes on..
you say the terminal crashes as well?
Yeah, the whole desktop will crash/flicker. It's like KDE is dying
I know but does the terminal still work after this happens
No
shit, so much for running journalctl to diagnose the issue.
I can pull up the older logs if needed via something like this journalctl -b -2
do that, because it's the only way you're gonna find out exactly what happened
Hmmm will see if I can post it here. Will probably add to OP
In the meantime, you say this crashes KDE, Have you tried running darktide in gamescope?
I have not... didn't even occur to me to try gamescope
I have used to to get HDR working in the past
Don't get your hopes up, it might not fix the issue, but I figure starting a whole ass display server with gamescope might give you a crash buffer layer
Hopefully or it'll make the issue worse. Which could help narrow it down better
bazzite comes with something called scopebuddy, read up on that if you're using a version of bazzite with "gaming mode"
ScopeBuddy - Bazzite Documentation
Bazzite is a custom image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices.
Thank you will have that a look. I was able to find a log where I had the crashes occur multiple times. Uploading it soonish
Be sure to report it on the github issue tracker, not just here https://github.com/ublue-os/bazzite/issues
GitHub
ublue-os/bazzite
Bazzite makes gaming and everyday use smoother and simpler across desktop PCs, handhelds, tablets, and home theater PCs. - ublue-os/bazzite
when you narrow down the issue
Really hoping it's not my CPU. I'm already on my 2nd RMA from intel and if it is the issue.. this point I'm a yeet this thing into the sun
So it's now staring to happen in other games and I was able to catch the errors right after :
Oct 13 19:07:24 bazzite xwaylandvideobridge[3054]: The X11 connection broke (error 1). Did the X11 server die?
Oct 13 19:07:24 bazzite gmenudbusmenuproxy[2622]: The X11 connection broke (error 1). Did the X11 server die?
Oct 13 19:07:24 bazzite flatpak[5200]: XIO: fatal IO error 13 (Permission denied) on X server ":0"
Oct 13 19:07:24 bazzite xembedsniproxy[2628]: The X11 connection broke (error 1). Did the X11 server die?
Oct 13 19:07:24 bazzite kaccess[2623]: The X11 connection broke (error 1). Did the X11 server die?
Oct 13 19:07:24 bazzite ksmserver[2529]: The X11 connection broke (error 1). Did the X11 server die?
Oct 13 19:07:24 bazzite kwin_wayland[2292]: kwin_xwl: The X11 connection broke (error 1)
Oct 13 19:07:24 bazzite gmenudbusmenuproxy[24485]: Qt: Session management error: Could not open network socket
Oct 13 19:07:24 bazzite xembedsniproxy[24487]: Qt: Session management error: Could not open network socket
Oct 13 19:07:26 bazzite maliit-keyboard[24602]: QSGContext::initialize: depth buffer support missing, expect rendering errors
Oct 13 19:07:26 bazzite maliit-keyboard[24602]: QSGContext::initialize: stencil buffer support missing, expect rendering errors
Oct 13 19:07:36 bazzite env[5765]: [umu.main:78] DEBUG: DXVK_LOG_LEVEL=error
Oct 13 19:08:33 bazzite flatpak[26066]: XIO: fatal IO error 13 (Permission denied) on X server ":0"
Oct 13 19:08:33 bazzite xembedsniproxy[24487]: The X11 connection broke (error 1). Did the X11 server die?
Oct 13 19:08:33 bazzite kaccess[24486]: The X11 connection broke (error 1). Did the X11 server die?
Oct 13 19:08:33 bazzite flatpak[25630]: XIO: fatal IO error 13 (Permission denied) on X server ":0"
Oct 13 19:08:33 bazzite kwin_wayland[2292]: kwin_xwl: The X11 connection broke (error 1)
Oct 13 19:08:33 bazzite gmenudbusmenuproxy[24485]: The X11 connection broke (error 1). Did the X11 server die?
Oct 13 19:08:33 bazzite flatpak[25962]: [53:0100/000000.700083:ERROR:connection.cc(68)] X connection error received.
Oct 13 19:08:34 bazzite xembedsniproxy[26541]: Qt: Session management error: Could not open network socket
Oct 13 19:08:34 bazzite gmenudbusmenuproxy[26539]: Qt: Session management error: Could not open network socket
Oct 13 19:08:38 bazzite plasmashell[24755]: XIO: fatal IO error 2 (No such file or directory) on X server ":0"
Any suggestions would be appreciated
Unfortanetly this did not work. It did reduce crashes on most games. But Darktide and few others did not improve. Also began seeing other system issues, audio cut outs, random freezes, and other OS issues. I rebased to 42.20251002 and my issues went away. Not sure what change was made in the recent update to cause this. Guessing something with KDE and/or the X11 Wayland bridge.