Open perroboc opened 1 year ago
sjohal21
commented
2 months ago Exact same issue here, on nearly the same setup (exact same GPU, Arch, KDE, so on) on the latest version of Gamescope. Exiting the game from within its menu works fine, but ALT + F4 seemingly just breaks everything.
davidfrickert
commented
2 months ago same issue here. it seems that when you alt + f4, the game stays running somehow, e.g.:
davidjf 32552 2.6 0.0 4600 1632 ? S 18:57 0:00 /home/davidjf/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper/pressure-vessel/libexec/steam-runtime-tools-0/srt-bwrap --args 32 /usr/lib/pressure-vessel/from-host/bin/pressure-vessel-adverb --generate-locales --fd 21 --regenerate-ld.so-cache /var/pressure-vessel/ldso --add-ld.so-path /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu --add-ld.so-path /usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu --set-ld-library-path /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/aliases:/usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu/aliases --overrides-path /usr/lib/pressure-vessel/overrides --exit-with-parent --subreaper --assign-fd=1=6 --assign-fd=2=7 --shell=none --terminal=none -- /home/davidjf/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper/pressure-vessel/bin/steam-runtime-launcher-interface-0 container-runtime /usr/share/steam/compatibilitytools.d/proton-ge-custom/proton waitforexitandrun /home/davidjf/.local/share/Steam/steamapps/common/Hades II/Ship/Hades2.exe /c ../ /steampowered /VerboseScriptLogging=false /DebugKeysEnabled=false /UnsafeDebugKeysEnabled=false /LiveCreateTextures=false /CheckNonExistingTextures=false /DirectLoadShell=true /SaveCollectionRate=1
davidjf 32640 0.1 0.0 30344 5376 ? Ss 18:57 0:00 /usr/lib/pressure-vessel/from-host/bin/pressure-vessel-adverb --generate-locales --fd 21 --regenerate-ld.so-cache /var/pressure-vessel/ldso --add-ld.so-path /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu --add-ld.so-path /usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu --set-ld-library-path /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/aliases:/usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu/aliases --overrides-path /usr/lib/pressure-vessel/overrides --exit-with-parent --subreaper --assign-fd=1=6 --assign-fd=2=7 --shell=none --terminal=none -- /home/davidjf/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper/pressure-vessel/bin/steam-runtime-launcher-interface-0 container-runtime /usr/share/steam/compatibilitytools.d/proton-ge-custom/proton waitforexitandrun /home/davidjf/.local/share/Steam/steamapps/common/Hades II/Ship/Hades2.exe /c ../ /steampowered /VerboseScriptLogging=false /DebugKeysEnabled=false /UnsafeDebugKeysEnabled=false /LiveCreateTextures=false /CheckNonExistingTextures=false /DirectLoadShell=true /SaveCollectionRate=1
davidjf 32681 0.2 0.0 882540 23812 ? Ssl 18:57 0:00 C:\windows\system32\services.exe
davidjf 32684 0.1 0.0 546456 23344 ? Ssl 18:57 0:00 C:\windows\system32\winedevice.exe
davidjf 32694 3.7 0.1 728220 40752 ? Ssl 18:57 0:00 C:\windows\system32\winedevice.exe
davidjf 32707 0.2 0.0 414484 23636 ? Ssl 18:57 0:00 C:\windows\system32\plugplay.exe
davidjf 32715 0.0 0.0 196868 14788 ? Ssl 18:57 0:00 C:\windows\system32\svchost.exe -k LocalServiceNetworkRestricted
davidjf 32723 0.8 0.1 428444 60580 ? Ssl 18:57 0:00 C:\windows\system32\explorer.exe /desktop
davidjf 32732 0.0 0.0 471344 18892 ? Ssl 18:57 0:00 C:\windows\system32\rpcss.exewell, small workaround, in a script where you call gamescope, ensure you kill exe processes. this is obviously not ideal as it might kill more stuff than you want to but since i dont run wine outside of games i'm ok with it (at least until the core issue is fixed)
#!/usr/bin/env bash
SDL_VIDEODRIVER=x11 gamescope -w 2560 -h 1600 -W 2560 -H 1600 -f "$@"
pkill -f "\.exe"
Wgelyjr
commented
1 month ago Seeing this issue on Fedora 40 KDE.
I've enabled a game to use gamescope with these launch options:
gamescope -h 1080 -H 1080 -r 144 -f -- %command%, and the game runs great, until I close it with Alt+F4. I am unable to launch the game again in the same session, and have to log out and in back again. In the "broken" session, I'm able to start a game without gamescope just fine, even after Alt+F4.I'm using Arch, KDE Plasma, X11, pipewire, AMDGPU.
Here's the journal of me starting the game and hitting Alt+F4
Then trying to start it again, it doesnt run:
And then, trying to start it yet again, it's stuck:
The last time I could see a
gamescopeprocess running in the background:Killing the process and trying to start the game again yields the same results:
If I clear the Launch Options, and log back into the KDE Session, I'm able to close the game by Alt+F4 and launch it again just fine: