-
Notifications
You must be signed in to change notification settings - Fork 223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gamescope aborting and coredumping #1272
Comments
Please send a backtrace |
@anthr76
|
Okay, sorry for the delay, i posted this right before going on a trip...
then i tried again, and it failed:
both of this backtraces are from within dwl. |
Does this still occur?
eglgears_x11 is probably part of some "mesa-utils" package on your distro. I would like to know if I am running into the same issue before I post about it. |
I appear to have a very similar issue. I am running nixos-unstable on an AMD framework 13 (1st gen) with radv. Here is the stderr log of running
Is there more information I can provide? |
gamescopes exit codes and aborts are a mess. if i cleanly exit a game i always get an exit code 134. also when runing a single gamescope command and do CRTL+C it aborts with code 134 and also does coredumping... wtf? |
It's a known issue |
I'm on nixos-unstable trying to run
gamescope -e -- steam
and getting:I also tried steam-gamescope wich is basically an alias to
gamescope --steam -- steam -tenfoot -pipewire-dmabuf
:mesa: Version: 24.0.5
gamescope: Version: 3.14.4
amdvlk: 2023.Q4.2 -- tried with and without amdvlk...
altough i do not think it is, if relevant, i'm using dwl (dwm for wayland) as a compositor and pipewire
here is the repo for my compositor: https://codeberg.org/ThiagoAssis/dwl/src/branch/personalMain
there is a folder in my branch with all the patches.
also: when i launch
steam-gasmescope
from tty, it works fine...The text was updated successfully, but these errors were encountered: