Open Kana-Starmarker opened 4 days ago
What Kisak said here probably applies to this as well: https://github.com/ValveSoftware/gamescope/issues/1557#issuecomment-2389969773
I'd try launching Steam and then using Gamescope in the game's launch options like gamescope <gamescope args here> -- %command%
or running all of Steam without Gamescope, like gamescope -e -- steam
Hi, thank you for replying. Sorry, I forgot to mention it, but it's the same problem when I do it through launch options. Even running something like gamescope -- vkcube
in terminal yields the same result.
Can you post a backtrace (coredumpctl info
on systemd) with debug symbols package installed/compiled from source, or the logs of WAYLAND_DEBUG=client gamescope -- vkcube
(attach as a file)? It looks similar to https://github.com/ValveSoftware/gamescope/issues/1451, which might be fixed by https://github.com/ValveSoftware/gamescope/pull/1611.
After the Steam client update yesterday I have been experiencing the same issue. Here are the results of running coredumpctl info:
PID: 5390 (gamescopereaper) UID: 1000 (graham) GID: 1000 (graham) Signal: 6 (ABRT) Timestamp: Wed 2024-11-06 11:29:44 CST (10min ago) Command Line: gamescopereaper -- /home/graham/.local/share/Steam/ubuntu12_32/steam-launch-wrapper /home/graham/.local/share/Steam/ubuntu12_32/reaper Ste amLaunch AppId=730 -- /home/graham/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper/_v2-entry-point --verb=waitforexitandrun -- $'/home/graham /.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/game/cs2.sh' -steam -threads 7 -vulkan -nojoy Executable: /usr/bin/gamescopereaper Control Group: /user.slice/user-1000.slice/session-3.scope Unit: session-3.scope Slice: user-1000.slice Session: 3 Owner UID: 1000 (graham) Boot ID: b38aff9e4c8d4721b3d2bc0baeb8bc17 Machine ID: 653d5887b0054737847d4b643f9adcd9 Hostname: archlinux Storage: /var/lib/systemd/coredump/core.gamescopereaper.1000.b38aff9e4c8d4721b3d2bc0baeb8bc17.5390.1730914184000000.zst (present) Size on Disk: 136.4K Message: Process 5390 (gamescopereaper) of user 1000 dumped core.
Stack trace of thread 5390:
#0 0x000071f8e62a53f4 n/a (libc.so.6 + 0x963f4)
#1 0x000071f8e624c120 raise (libc.so.6 + 0x3d120)
#2 0x000071f8e62334c3 abort (libc.so.6 + 0x244c3)
#3 0x000071f8e49f3044 n/a (libdbus-1.so.3 + 0xe044)
#4 0x000071f8e4a1a8eb _dbus_warn_check_failed (libdbus-1.so.3 + 0x358eb)
#5 0x000071f8e4a388c5 n/a (libgamemode.so.0 + 0x28c5)
#6 0x000071f8e6802140 gamemode_request_end (libgamemodeauto.so.0 + 0x1140)
#7 0x000071f8e680f0f2 n/a (ld-linux-x86-64.so.2 + 0x10f2)
#8 0x000071f8e68123ee n/a (ld-linux-x86-64.so.2 + 0x43ee)
#9 0x000071f8e624e891 n/a (libc.so.6 + 0x3f891)
#10 0x000071f8e624e95e exit (libc.so.6 + 0x3f95e)
#11 0x000071f8e6234e0f n/a (libc.so.6 + 0x25e0f)
#12 0x000071f8e6234ecc __libc_start_main (libc.so.6 + 0x25ecc)
#13 0x00005bce456e3b75 n/a (gamescopereaper + 0x5b75)
ELF object binary architecture: AMD x86-64
Is there an existing issue for this?
Are you using any gamescope patches or a forked version of gamescope?
Current Behavior
I can't use it. I've tried every fix I could find by searching online (like trying out modifiers like
--backend
). Tried switching to X11, still no dice. I've been trying to get it working for a while now, and I am this close to giving up.What shows when I run Stardew Valley via terminal with
gamescope -- steam steam://rungameid/413150
(but this applies to any other game):Steps To Reproduce
Hardware information
Software information
Which gamescope backends have the issue you are reporting?
Logging, screenshots, or anything else
No response