Bug: Deep Rock Galactic Crashes on Steam Deck with Gamescope
113 °C
Bug #565

Deep Rock Galactic Crashes on Steam Deck with Gamescope

Status: Closed
Priority:
High
Added by:
gin_rx
on June 16, '25
Assigned to:
Unassigned
Due date:
Reported for:

Steps to Reproduce

  1. While playing DRG and doing missions, everything is running fine. FPS, utilization, temp, and etc are all stable.
  2. Throughout the mission it will randomly crash.
  3. The screen goes black with the sounds still on.
  4. Suddenly my deck oled goes on reboot.

Explanation

DRG keep crashing on my deck oled resulting on reboot. I’ve tried all possible fixes from trying different proton and verifying integrity. None works.

PID: 1253 (gamescope-wl)

UID: 1000 (deck)

GID: 1000 (deck)

Signal: 11 (SEGV)

Timestamp: Sun 2025-06-15 11:47:36 PDT (1min 29s ago)

Command Line: gamescope --generate-drm-mode fixed --xwayland-count 2 -w 1280 -h 800 --default-touch-mode 4 --hide-cursor-delay 3000 --max-scale 2 --fade-out-duration 200 --cursor-scale-height 720 -e -R /run/user/1000/gamescope.yLASN6g/startup.socket -T /run/user/1000/gamescope.yLASN6g/stats.pipe -O $'*,eDP-1'

Executable: /usr/bin/gamescope

Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/gamescope-session.service

Unit: user@1000.service

User Unit: gamescope-session.service

Slice: user-1000.slice

Owner UID: 1000 (deck)

Boot ID: 8a64797570c743c7a7a75d79b43f5869

Machine ID: e3a45d11c3224f63bb8d7b64e59d6b2b

Hostname: steamdeck

Storage: /var/lib/systemd/coredump/core.gamescope-wl.1000.8a64797570c743c7a7a75d79b43f5869.1253.1750013256000000.zst (inaccessible)

Message: Process 1253 (gamescope-wl) of user 1000 dumped core.

Stack trace of thread 1253:

#0 0x00007ff3cb1bcf4b n/a (libwayland-server.so.0 + 0x8f4b)

#1 0x00007ff3cb1bd282 wl_resource_post_event (libwayland-server.so.0 + 0x9282)

#2 0x00005601e0967bca n/a (/usr/bin/gamescope + 0xb7bca)

#3 0x00007ff3cb1bc47e wl_signal_emit_mutable (libwayland-server.so.0 + 0x847e)

#4 0x00005601e0a3c238 n/a (/usr/bin/gamescope + 0x18c238)

#5 0x00007ff3cb1bebbb n/a (libwayland-server.so.0 + 0xabbb)

#6 0x00007ff3cb1bedd2 wl_client_destroy (libwayland-server.so.0 + 0xadd2)

#7 0x00007ff3cb1befda n/a (libwayland-server.so.0 + 0xafda)

#8 0x00007ff3cb1be112 wl_event_loop_dispatch (libwayland-server.so.0 + 0xa112)

#9 0x00005601e0968c9f n/a (/usr/bin/gamescope + 0xb8c9f)

#10 0x00005601e08ea04a n/a (/usr/bin/gamescope + 0x3a04a)

#11 0x00007ff3ca53c488 n/a (libc.so.6 + 0x27488)

#12 0x00007ff3ca53c54c __libc_start_main (libc.so.6 + 0x2754c)

#13 0x00005601e0908ff5 n/a (/usr/bin/gamescope + 0x58ff5)

Stack trace of thread 1311:

#0 0x00007ff3ca5b2b62 n/a (libc.so.6 + 0x9db62)

#1 0x00007ff3ca5a6dd3 n/a (libc.so.6 + 0x91dd3)

#2 0x00007ff3ca5a745c n/a (libc.so.6 + 0x9245c)

#3 0x00007ff3ca5a9b8e pthread_cond_wait (libc.so.6 + 0x94b8e)

#4 0x00007ff3bf0521be n/a (libvulkan_radeon.so + 0x2521be)

#5 0x00007ff3bf02947c n/a (libvulkan_radeon.so + 0x22947c)

#6 0x00007ff3bf05211d n/a (libvulkan_radeon.so + 0x25211d)

#7 0x00007ff3ca5aa688 n/a (libc.so.6 + 0x95688)

#8 0x00007ff3ca62e96c n/a (libc.so.6 + 0x11996c)

Stack trace of thread 1314:

#0 0x00007ff3ca5b2b62 n/a (libc.so.6 + 0x9db62)

#1 0x00007ff3ca5a6dd3 n/a (libc.so.6 + 0x91dd3)

#2 0x00007ff3ca5a6e14 n/a (libc.so.6 + 0x91e14)

#3 0x00007ff3ca6213fe __poll (libc.so.6 + 0x10c3fe)

#4 0x00005601e09999a9 n/a (/usr/bin/gamescope + 0xe99a9)

#5 0x00007ff3ca8e1c34 execute_native_thread_routine (libstdc++.so.6 + 0xe1c34)

#6 0x00007ff3ca5aa688 n/a (libc.so.6 + 0x95688)

#7 0x00007ff3ca62e96c n/a (libc.so.6 + 0x11996c)

Stack trace of thread 1312:

#0 0x00007ff3ca5b2b62 n/a (libc.so.6 + 0x9db62)

#1 0x00007ff3ca5a6dd3 n/a (libc.so.6 + 0x91dd3)

#2 0x00007ff3ca5f79c2 clock_nanosleep (libc.so.6

Watchers

Screenshots

None

Video Clips

None

Log Files

None

Device

No device information

[ #1 ] 3 months ago by

Please go to our Discord in the Bug Discussion forum, as there might be players who have had similar issues and found solution. We are not able to support Linux/steamdeck here

You don't have permission to comment on this issue.