search

ValveSoftware / gamescope

SteamOS session compositing window manager
Other
2.89k stars 192 forks source link

Gamescope crashing when launching on my steam deck in desktop mode. #1042

Open xrishox opened 8 months ago

xrishox commented 8 months ago

I'm trying to use gamescope on my steam deck in desktop mode. I've tried it with ordinary applications on the desktop like kate for example and then I've tried it using lutris on flatpak with flatpak gamescope and it crashes in both instances.

outside of flatpak example:

gamescope -- kate
Tracing is enabled
wlserver: [backend/headless/backend.c:68] Creating headless backend
vulkan: selecting physical device 'AMD Radeon Graphics (RADV VANGOGH)': queue family 1 (general queue family 0)
vulkan: physical device supports DRM format modifiers
vulkan: supported DRM formats for sampling usage:
vulkan:   AR24 (0x34325241)
vulkan:   XR24 (0x34325258)
vulkan:   AB24 (0x34324241)
vulkan:   XB24 (0x34324258)
vulkan:   RG16 (0x36314752)
vulkan:   NV12 (0x3231564E)
vulkan:   AB4H (0x48344241)
vulkan:   XB4H (0x48344258)
vulkan:   AB48 (0x38344241)
vulkan:   XB48 (0x38344258)
vulkan:   AB30 (0x30334241)
vulkan:   XB30 (0x30334258)
vulkan:   AR30 (0x30335241)
vulkan:   XR30 (0x30335258)
vulkan: Creating Gamescope nested swapchain with format 44 and colorspace 0
wlserver: Running compositor on wayland display 'gamescope-0'
wlserver: [backend/headless/backend.c:16] Starting headless backend
wlserver: [xwayland/server.c:108] Starting Xwayland on :0
wlserver: [types/wlr_compositor.c:681] New wlr_surface 0x56328d65e4d0 (res 0x56328d65d180)
wlserver: [xwayland/server.c:273] Xserver is ready
pipewire: stream state changed: connecting
pipewire: stream state changed: paused
pipewire: stream available on node ID: 121
vulkan: Creating Gamescope nested swapchain with format 44 and colorspace 0
pipewire: renegotiating stream params (size: 1280x720)
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_STAYS_ON_TOP
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_BELOW
wlserver: [types/wlr_compositor.c:681] New wlr_surface 0x56328d4fea20 (res 0x56328d56e7d0)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
Errors from xkbcomp are not fatal to the X server
(EE) failed to read Wayland events: Broken pipe
Segmentation fault (core dumped)

inside of flatpak in lutris example:

Start monitoring process.
No CAP_SYS_NICE, falling back to regular-priority compute and threads.
Performance will be affected.
wlserver: [backend/headless/backend.c:68] Creating headless backend
vulkan: selecting physical device 'AMD Radeon Graphics (RADV VANGOGH)': queue family 1 (general queue family 0)
vulkan: physical device supports DRM format modifiers
vulkan: supported DRM formats for sampling usage:
vulkan:   AR24 (0x34325241)
vulkan:   XR24 (0x34325258)
vulkan:   AB24 (0x34324241)
vulkan:   XB24 (0x34324258)
vulkan:   RG16 (0x36314752)
vulkan:   NV12 (0x3231564E)
vulkan:   AB4H (0x48344241)
vulkan:   XB4H (0x48344258)
vulkan:   AB48 (0x38344241)
vulkan:   XB48 (0x38344258)
vulkan:   AB30 (0x30334241)
vulkan:   XB30 (0x30334258)
vulkan:   AR30 (0x30335241)
vulkan:   XR30 (0x30335258)
vulkan: Creating Gamescope nested swapchain with format 44 and colorspace 0
wlserver: Running compositor on wayland display 'gamescope-0'
wlserver: [backend/headless/backend.c:16] Starting headless backend
wlserver: [xwayland/server.c:108] Starting Xwayland on :0
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86CameraAccessEnable
> Warning:          Could not resolve keysym XF86CameraAccessDisable
> Warning:          Could not resolve keysym XF86CameraAccessToggle
> Warning:          Could not resolve keysym XF86NextElement
> Warning:          Could not resolve keysym XF86PreviousElement
> Warning:          Could not resolve keysym XF86AutopilotEngageToggle
> Warning:          Could not resolve keysym XF86MarkWaypoint
> Warning:          Could not resolve keysym XF86Sos
> Warning:          Could not resolve keysym XF86NavChart
> Warning:          Could not resolve keysym XF86FishingChart
> Warning:          Could not resolve keysym XF86SingleRangeRadar
> Warning:          Could not resolve keysym XF86DualRangeRadar
> Warning:          Could not resolve keysym XF86RadarOverlay
> Warning:          Could not resolve keysym XF86TraditionalSonar
> Warning:          Could not resolve keysym XF86ClearvuSonar
> Warning:          Could not resolve keysym XF86SidevuSonar
> Warning:          Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
wlserver: [types/wlr_compositor.c:673] New wlr_surface 0x5612f1ad62b0 (res 0x5612f1ad95e0)
wlserver: [xwayland/server.c:273] Xserver is ready
pipewire: pw_context_connect failed
Warning: failed to setup PipeWire, screen capture won't be available
gamemodeauto: 
fsync: up and running.
xwm: Unhandled client message: _NET_STARTUP_INFO_BEGIN
xwm: Unhandled client message: _NET_STARTUP_INFO
xwm: Unhandled client message: _NET_STARTUP_INFO
wlserver: [types/wlr_compositor.c:673] New wlr_surface 0x5612f1cf3b00 (res 0x5612f1c22200)
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
wlserver: [types/wlr_compositor.c:673] New wlr_surface 0x5612f1cf3f10 (res 0x5612f1c22440)
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
xwm: got the same buffer committed twice, ignoring.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
Errors from xkbcomp are not fatal to the X server
(EE) failed to read Wayland events: Connection reset by peer
X connection to :0 broken (explicit kill or server shutdown).
X connection to :0 broken (explicit kill or server shutdown).
X connection to :0 broken (explicit kill or server shutdown).
X connection to :0 broken (explicit kill or server shutdown).
Monitored process exited.
Initial process has exited (return code: 139)
Exit with return code 139

I'm on steamos 3.5.7. It does this on both my oled and my non oled and it does it whether I'm on stable or preview.

ITdevkc commented 7 months ago

I can confirm this issue. I am also on 3.5.7 and experience the same issue. Kate, bottles (flatpak), and glxgears exit with the same error. vkcube "runs" as in it doesn't crash, but no window is displayed, and a Vulkan error is displayed (refusing to make swapchain [unsupported vkformat])

The issue also seems to persist in game mode, if a shortcut is added to Steam with a gamescope command.

DocMAX commented 7 months ago

Same here, crashing with -tenfoot enable. Works without. (nvidia!)

> Warning:          Could not resolve keysym XF86NextElement
> Warning:          Could not resolve keysym XF86PreviousElement
> Warning:          Could not resolve keysym XF86AutopilotEngageToggle
> > Warning:          Warning:          Could not resolve keysym XF86NextElement
Could not resolve keysym XF86MarkWaypoint
> Warning:          > Could not resolve keysym XF86Sos
Warning:          > Could not resolve keysym XF86PreviousElement
> Warning:          Could not resolve keysym XF86AutopilotEngageToggle
> Warning:          Could not resolve keysym XF86MarkWaypoint
Warning:          > Could not resolve keysym XF86NavChart
Warning:          > Could not resolve keysym XF86Sos
Warning:          Could not resolve keysym XF86FishingChart
> Warning:          > Could not resolve keysym XF86NavChart
Warning:          Could not resolve keysym XF86SingleRangeRadar
> Warning:          Could not resolve keysym XF86FishingChart
> Warning:          Could not resolve keysym XF86DualRangeRadar
> Warning:          > Could not resolve keysym XF86SingleRangeRadar
Warning:          Could not resolve keysym XF86RadarOverlay
> Warning:          Could not resolve keysym XF86DualRangeRadar
> Warning:          Could not resolve keysym XF86TraditionalSonar
> > Warning:          Warning:          Could not resolve keysym XF86RadarOverlay
Could not resolve keysym XF86ClearvuSonar
> > Warning:          Could not resolve keysym XF86TraditionalSonar
> Warning:          Could not resolve keysym XF86ClearvuSonar
> Warning:          Could not resolve keysym XF86SidevuSonar
Warning:          > Warning:          Could not resolve keysym XF86NavInfo
Could not resolve keysym XF86SidevuSonar
> Warning:          Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
Errors from xkbcomp are not fatal to the X server
vkCreateInstance failed with error -9
BInit - Unable to initialize Vulkan!
glx: failed to create dri3 screen
failed to load driver: nouveau
glx: failed to create dri3 screen
failed to load driver: nouveau
glx: failed to create dri3 screen
failed to load driver: nouveau
glx: failed to create dri3 screen
failed to load driver: nouveau
BRefreshApplicationsInLibrary 1: 1ms
crash_20231224230533_29.dmp[14456]: Uploading dump (out-of-process)
/tmp/dumps/crash_20231224230533_29.dmp
/home/docmax/.local/share/Steam/steam.sh: Zeile 798: 13965 Speicherzugriffsfehler  (Speicherabzug geschrieben) "$STEAMROOT/$STEAMEXEPATH" "$@"
wlserver: [types/wlr_compositor.c:692] New wlr_surface 0x559624a2f130 (res 0x559624b540d0)
xwm: got the same buffer committed twice, ignoring.
crash_20231224230533_29.dmp[14456]: Finished uploading minidump (out-of-process): success = yes
crash_20231224230533_29.dmp[14456]: response: CrashID=bp-0d59bb05-4663-456e-9d65-5f5652231224
crash_20231224230533_29.dmp[14456]: file ''/tmp/dumps/crash_20231224230533_29.dmp'', upload yes: ''CrashID=bp-0d59bb05-4663-456e-9d65-5f5652231224''
gamescope: children shut down!
(EE) failed to read Wayland events: Connection reset by peer
(EE) failed to read Wayland events: Broken pipe
Speicherzugriffsfehler (Speicherabzug geschrieben)
SipiRaussi commented 7 months ago

I have similar issue here

Context (Environment)

Distro: Gentoo Linux Kernel: 6.5.2-rt-rt8-gentoo-dist Mesa: 23.1.9 GPU: AMD Radeon RX 5700 XT (Navi 10 / RDNA1) DE: Gnome 44.4 (Wayland) Gamescope: 3.13.19

Crash log

$ gamescope --prefer-vk-device 1002:731f -- glxgears
vblank: Using timerfd.
wlserver: [backend/headless/backend.c:67] Creating headless backend
ATTENTION: default value of option vk_khr_present_wait overridden by environment.
vulkan: selecting physical device 'AMD Radeon RX 5700 XT (RADV NAVI10)': queue family 1 (general queue family 0)
vulkan: physical device supports DRM format modifiers
vulkan: supported DRM formats for sampling usage:
vulkan:   AR24 (0x34325241)
vulkan:   XR24 (0x34325258)
vulkan:   AB24 (0x34324241)
vulkan:   XB24 (0x34324258)
vulkan:   RG16 (0x36314752)
vulkan:   NV12 (0x3231564E)
vulkan:   AB4H (0x48344241)
vulkan:   XB4H (0x48344258)
vulkan:   AB48 (0x38344241)
vulkan:   XB48 (0x38344258)
vulkan:   AB30 (0x30334241)
vulkan:   XB30 (0x30334258)
vulkan:   AR30 (0x30335241)
vulkan:   XR30 (0x30335258)
vulkan: Creating Gamescope nested swapchain with format 64 and colorspace 0
wlserver: Running compositor on wayland display 'gamescope-0'
wlserver: [backend/headless/backend.c:17] Starting headless backend
wlserver: [xwayland/server.c:108] Starting Xwayland on :2
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86CameraAccessEnable
> Warning:          Could not resolve keysym XF86CameraAccessDisable
> Warning:          Could not resolve keysym XF86CameraAccessToggle
> Warning:          Could not resolve keysym XF86NextElement
> Warning:          Could not resolve keysym XF86PreviousElement
> Warning:          Could not resolve keysym XF86AutopilotEngageToggle
> Warning:          Could not resolve keysym XF86MarkWaypoint
> Warning:          Could not resolve keysym XF86Sos
> Warning:          Could not resolve keysym XF86NavChart
> Warning:          Could not resolve keysym XF86FishingChart
> Warning:          Could not resolve keysym XF86SingleRangeRadar
> Warning:          Could not resolve keysym XF86DualRangeRadar
> Warning:          Could not resolve keysym XF86RadarOverlay
> Warning:          Could not resolve keysym XF86TraditionalSonar
> Warning:          Could not resolve keysym XF86ClearvuSonar
> Warning:          Could not resolve keysym XF86SidevuSonar
> Warning:          Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
wlserver: [types/wlr_compositor.c:692] New wlr_surface 0x564ef7621bb0 (res 0x564ef7604500)
wlserver: [xwayland/server.c:273] Xserver is ready
pipewire: stream state changed: connecting
pipewire: stream state changed: paused
pipewire: stream available on node ID: 84
vulkan: Creating Gamescope nested swapchain with format 64 and colorspace 0
pipewire: renegotiating stream params (size: 1280x720)
wlserver: [types/wlr_compositor.c:692] New wlr_surface 0x564ef75ba9f0 (res 0x564ef75e8b70)
xwm: got the same buffer committed twice, ignoring.
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
> Warning:          Could not resolve keysym XF86CameraAccessEnable
> Warning:          Could not resolve keysym XF86CameraAccessDisable
> Warning:          Could not resolve keysym XF86CameraAccessToggle
> Warning:          Could not resolve keysym XF86NextElement
> Warning:          Could not resolve keysym XF86PreviousElement
> Warning:          Could not resolve keysym XF86AutopilotEngageToggle
> Warning:          Could not resolve keysym XF86MarkWaypoint
> Warning:          Could not resolve keysym XF86Sos
> Warning:          Could not resolve keysym XF86NavChart
> Warning:          Could not resolve keysym XF86FishingChart
> Warning:          Could not resolve keysym XF86SingleRangeRadar
> Warning:          Could not resolve keysym XF86DualRangeRadar
> Warning:          Could not resolve keysym XF86RadarOverlay
> Warning:          Could not resolve keysym XF86TraditionalSonar
> Warning:          Could not resolve keysym XF86ClearvuSonar
> Warning:          Could not resolve keysym XF86SidevuSonar
> Warning:          Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
(EE) failed to read Wayland events: Broken pipe
Segmentation fault
DocMAX commented 7 months ago

can't believe amd (5700 xt) have problems too. gamescope overall seem to be a hit and miss thing.

Joshua-Ashton commented 7 months ago

Please provide a backtrace from coredumpctl or gdb

SipiRaussi commented 7 months ago

I got the gamescope working! I had 2 vulkan drivers: AMDGPU-PRO and RADV, on my machine. I removed AMDGPU-PRO drivers and upgraded Mesa to 23.3.1.

I think gamescope had problems when choosing a driver. Unfortunately I wasn't able to generate coredump file...

Joshua-Ashton commented 7 months ago

No, the mere presence of AMDGPU-Pro breaks everything related to Gamescope becoming a DRM master as it opens DRM_NODE_MASTER at physical device enum time.

I made an issue about this long ago but it seems it has been ignored.

I guess it's time to add some annoying text in Gamescope to avoid issues being made about this.

JohannRL commented 7 months ago

I face the same issue, here is the coredump you requested:

            Stack trace of thread 24420:
            #0  0x0000558d8082bd1b n/a (gamescope + 0x59d1b)
            #1  0x0000558d80840501 n/a (gamescope + 0x6e501)
            #2  0x0000558d80841b7f n/a (gamescope + 0x6fb7f)
            #3  0x00007f12e46e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
            #4  0x00007f12e449d44b n/a (libc.so.6 + 0x8744b)
            #5  0x00007f12e4520e40 n/a (libc.so.6 + 0x10ae40)

            Stack trace of thread 24399:
            #0  0x00007f12e44e59e5 clock_nanosleep (libc.so.6 + 0xcf9e5)
            #1  0x00007f12e44ea5e7 __nanosleep (libc.so.6 + 0xd45e7)
            #2  0x00007f12e4e4f882 n/a (libSDL2-2.0.so.0 + 0x140882)
            #3  0x00007f12e4e5f33c n/a (libSDL2-2.0.so.0 + 0x15033c)
            #4  0x00007f12e4de5cd3 n/a (libSDL2-2.0.so.0 + 0xd6cd3)
            #5  0x00007f12e4e5ec7a n/a (libSDL2-2.0.so.0 + 0x14fc7a)
            #6  0x0000558d8084a487 n/a (gamescope + 0x78487)
            #7  0x00007f12e46e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
            #8  0x00007f12e449d44b n/a (libc.so.6 + 0x8744b)
            #9  0x00007f12e4520e40 n/a (libc.so.6 + 0x10ae40)

            Stack trace of thread 24397:
            #0  0x00007f12e4513c0f __poll (libc.so.6 + 0xfdc0f)
            #1  0x0000558d808485ff n/a (gamescope + 0x765ff)
            #2  0x0000558d807f4353 n/a (gamescope + 0x22353)
            #3  0x00007f12e4439850 n/a (libc.so.6 + 0x23850)
            #4  0x00007f12e443990a __libc_start_main (libc.so.6 + 0x2390a)
            #5  0x0000558d808162c5 n/a (gamescope + 0x442c5)

            Stack trace of thread 24418:
            #0  0x00007f12e4521266 epoll_wait (libc.so.6 + 0x10b266)
            #1  0x00007f12db3f5579 n/a (libspa-support.so + 0x13579)
            #2  0x00007f12db3e8be3 n/a (libspa-support.so + 0x6be3)
            #3  0x00007f12e4a9326f n/a (libpipewire-0.3.so.0 + 0x4126f)
            #4  0x00007f12e449d44b n/a (libc.so.6 + 0x8744b)
            #5  0x00007f12e4520e40 n/a (libc.so.6 + 0x10ae40)

            Stack trace of thread 24427:
            #0  0x00007f12e4499f0e n/a (libc.so.6 + 0x83f0e)
            #1  0x00007f12e449cab5 pthread_cond_timedwait (libc.so.6 + 0x86ab5)
            #2  0x00007f12e338c8fd n/a (libvulkan_radeon.so + 0x18c8fd)
            #3  0x00007f12e449d44b n/a (libc.so.6 + 0x8744b)
            #4  0x00007f12e4520e40 n/a (libc.so.6 + 0x10ae40)

            Stack trace of thread 24424:
            #0  0x00007f12e4499f0e n/a (libc.so.6 + 0x83f0e)
            #1  0x00007f12e449c7a0 pthread_cond_wait (libc.so.6 + 0x867a0)
            #2  0x00007f12e46d9e11 __gthread_cond_wait (libstdc++.so.6 + 0xd9e11)
            #3  0x0000558d80822ee5 n/a (gamescope + 0x50ee5)
            #4  0x00007f12e46e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
            #5  0x00007f12e449d44b n/a (libc.so.6 + 0x8744b)
            #6  0x00007f12e4520e40 n/a (libc.so.6 + 0x10ae40)

            Stack trace of thread 24400:
            #0  0x00007f12e4499f0e n/a (libc.so.6 + 0x83f0e)
            #1  0x00007f12e449c7a0 pthread_cond_wait (libc.so.6 + 0x867a0)
            #2  0x00007f12e345c41e n/a (libvulkan_radeon.so + 0x25c41e)
            #3  0x00007f12e343998c n/a (libvulkan_radeon.so + 0x23998c)
            #4  0x00007f12e345c34c n/a (libvulkan_radeon.so + 0x25c34c)
            #5  0x00007f12e449d44b n/a (libc.so.6 + 0x8744b)
            #6  0x00007f12e4520e40 n/a (libc.so.6 + 0x10ae40)

            Stack trace of thread 24423:
            #0  0x00007f12e44ea3a7 wait4 (libc.so.6 + 0xd43a7)
            #1  0x0000558d80841916 n/a (gamescope + 0x6f916)
            #2  0x00007f12e46e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
            #3  0x00007f12e449d44b n/a (libc.so.6 + 0x8744b)
            #4  0x00007f12e4520e40 n/a (libc.so.6 + 0x10ae40)

            Stack trace of thread 24403:
            #0  0x00007f12e45192ed syscall (libc.so.6 + 0x1032ed)
            #1  0x0000558d808483de n/a (gamescope + 0x763de)
            #2  0x00007f12e46e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
            #3  0x00007f12e449d44b n/a (libc.so.6 + 0x8744b)
            #4  0x00007f12e4520e40 n/a (libc.so.6 + 0x10ae40)

            Stack trace of thread 24421:
            #0  0x00007f12e44e59e5 clock_nanosleep (libc.so.6 + 0xcf9e5)
            #1  0x00007f12e44ea5e7 __nanosleep (libc.so.6 + 0xd45e7)
            #2  0x0000558d808480c7 n/a (gamescope + 0x760c7)
            #3  0x00007f12e46e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
            #4  0x00007f12e449d44b n/a (libc.so.6 + 0x8744b)
            #5  0x00007f12e4520e40 n/a (libc.so.6 + 0x10ae40)

            Stack trace of thread 24419:
            #0  0x00007f12e4513c0f __poll (libc.so.6 + 0xfdc0f)
            #1  0x0000558d8086c512 n/a (gamescope + 0x9a512)
            #2  0x00007f12e46e1943 execute_native_thread_routine (libstdc++.so.6 + 0xe1943)
            #3  0x00007f12e449d44b n/a (libc.so.6 + 0x8744b)
            #4  0x00007f12e4520e40 n/a (libc.so.6 + 0x10ae40)
            ELF object binary architecture: AMD x86-64
JohannRL commented 7 months ago

It seems this issue here is similar.

SipiRaussi commented 7 months ago

No, the mere presence of AMDGPU-Pro breaks everything related to Gamescope becoming a DRM master as it opens DRM_NODE_MASTER at physical device enum time.

Alright, good to know 👍

TakaiSaisei commented 6 months ago

Same issue here. Steam Deck, SteamOS 3.5.7. Doesn't happen on other distributions tho (like Bazzite)

skaiteo commented 6 months ago

Same issue here, running 3.5.7 and the latest client updates. It used to work on 3.4.x, but I recently decided to reimage to 3.5.x, and it stopped working. The last few lines of error are similar to the first post.

Gatinhoonline commented 6 months ago

Enter the developer settings and update to Main version 3.6, very important, right after in “desktop” mode update Steam to beta version, it has to be updated through desktop mode. let me know if it's resolved

ITdevkc commented 6 months ago

Enter the developer settings and update to Main version 3.6, very important, right after in “desktop” mode update Steam to beta version, it has to be updated through desktop mode. let me know if it's resolved

Indeed, updating to SteamOS 3.6 and Steam Beta has resolved the issue for me. Both Desktop Gamescope and Game Mode (nested) Gamescope work properly again. It really is an awesome piece of software.

In non-nested mode in Game Mode, the scaling slider (in the performance menu) does not appear to work, but I may be using that wrong, and it may be a different issue entirely.

Thanks for the fix, it works great!!

skaiteo commented 5 months ago

@Gatinhoonline it works, thanks! gamescope command runs perfectly in desktop mode and I can launch a game in gamescope through Steam, FSR works as well. However, the cursor is glitchy (disappears and only appears for fractions of a second when moving it), DeckyLoader doesn't work in the Beta Client.

EDIT: Now I'm on Release Candidate 3.5.14 and Stable Client, things are working perfectly, cursor also fine.