Skip to content
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

Mangoapp doesn't shut down after the running program/app closes #1284

Open
stele95 opened this issue Apr 7, 2024 · 12 comments
Open

Mangoapp doesn't shut down after the running program/app closes #1284

stele95 opened this issue Apr 7, 2024 · 12 comments

Comments

@stele95
Copy link

stele95 commented Apr 7, 2024

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:

  1. Run gamescope -- sh -c "mangoapp& vkcube" from the terminal
  2. Close vkcube
  3. Repeat steps 1. and 2. a couple times
  4. 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
Screenshot_20240407_111008

@flightlessmango
Copy link
Owner

use gamescopes --mangoapp argument instead

@stele95
Copy link
Author

stele95 commented Apr 7, 2024

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

@flightlessmango
Copy link
Owner

what's the full command you're using?

@stele95
Copy link
Author

stele95 commented Apr 8, 2024

gamescope --mangoapp -- vkcube

@flightlessmango
Copy link
Owner

What git version of mangohud and gamescope are you using?

@stele95
Copy link
Author

stele95 commented Apr 11, 2024

@flightlessmango
Copy link
Owner

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

@stele95
Copy link
Author

stele95 commented Apr 11, 2024

mangohud-git 0.7.2.rc2.r22.g1e13c38-1
gamescope-git 3.14.2.r97.g41389f7-1

@MacharaStormwing
Copy link

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.

@flightlessmango
Copy link
Owner

@MacharaStormwing this is likely a completely different issue, please create a new issue for it

@kodemeister
Copy link

kodemeister commented Apr 26, 2024

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.

@flightlessmango
Copy link
Owner

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants