MangoHud
MangoHud copied to clipboard
Mangoapp doesn't shut down after the running program/app closes
Describe the bug
After starting a mangoapp instance with gamescope -- sh -c "mangoapp& vkcube"
or any other program in the same way and then closing that program/app, mangoapp instance remains running.
List relevant hardware/software information
- Linux Distribution: EndeavourOS
- MangoHud version: latest git installed from AUR mangohud-git package
To Reproduce Steps to reproduce the behavior:
- Run
gamescope -- sh -c "mangoapp& vkcube"
from the terminal - Close vkcube
- Repeat steps 1. and 2. a couple times
- Check running processes
Expected behavior mangoapp should shut down after the program/app is closed
Screenshots
List of running processes after repeating reproduction steps 1. and 2. a couple of times
use gamescopes --mangoapp
argument instead
The behaviour is the same. Mangoapp still stays after shutting down gamescope instance.
Additional info that might be important, I'm on KDE Plasma 6 under Wayland.
Terminal log after clicking close:
gamescope: Received Terminated signal, forwarding to child! gamescope: Received Terminated signal, attempting shutdown! (EE) failed to read Wayland events: Broken pipe
what's the full command you're using?
gamescope --mangoapp -- vkcube
What git version of mangohud and gamescope are you using?
Both are installed through AUR
- https://aur.archlinux.org/packages/mangohud-git
- https://aur.archlinux.org/packages/gamescope-git
Since they are git versions they install whatever is the latest commit when you decided to install, which means only you know what git version it actually is.
With some luck pacman -Q mangohud gamescope
should tell us which commit it is
or you can reinstall both packages and check which commit was latest at the time
mangohud-git 0.7.2.rc2.r22.g1e13c38-1 gamescope-git 3.14.2.r97.g41389f7-1
I have a similar issue but with steam: When I add mangohud &command% to the launch parameters of the steam game, the game remains in memory and running in background (no gui seen). I use mangohud v0.7.1 in nobara linux 39.
@MacharaStormwing this is likely a completely different issue, please create a new issue for it
I had the same issue on gamescope
3.14.3 from Arch repos. Installing gamescope-git
package from AUR fixed stale mangoapp
processes. It seems like the bug was fixed in gamescope
3.14.6 or even in the very latest commits.
While using gamescope --mangoapp
, gamescope is handling starting and terminating mangoapp, so it should probably be reported there as well if it's still an issue
This should be resolved by using gamescope --mangoapp