-
Notifications
You must be signed in to change notification settings - Fork 214
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
Crash when mangohud is enabled #512
Comments
Hi, same for me coredump
Arch, Linux 5.18.1, mangohud 0.6.7.1, vulkan-radeon 22.1.0, mesa 22.1.0, AMD 6900 XT |
Mangohud by itself doesnt work on gamescope. There is a specifically made binary for gamescope compatibility (mangoapp) that should be used. Disable or set the MANGOHUD environment variable to 0 so gamescope won't crash. |
also getting this issue recently
before i was able to run EDIT: somehow fixed it by reinstalling the latest gamescope-git package |
Same for me: I tried mangoapp but then I don't have any output (but I don't know if related to gamescope, and if it is, not related to this report) |
to use mangoapp you would need something like this though mango app currently has a bug where it will keep running even after everything else exits so you'll have to force kill it afterwards |
Is integration a possibility? Spawning the separate sh shell works, but gets tricky trying to use this in various places (Lutris command prefix for example) Either gamescope knowing about mangoapp as an argument or mangoapp accepting a launch command akin to gamescope?
I think the separate shell is throwing off Lutris due to losing the previous environment variables.
EDIT: WOOPS. Single quotes helps.
Maybe something else is going wrong. |
Steps to reproduce
gamescope glxgears
Actual result
Crashes, with these messages in the journal:
Works when ran with
MANGOHUD=0
--
Fedora 36 GNOME/Wayland, gamescope 3.11.9-1.fc36, AMD 6800 XT, Mesa 22.0.3
The text was updated successfully, but these errors were encountered: