You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree to follow the Code of Conduct that this project adheres to.
I have searched the issue tracker for a bug that matches the one I want to file, without success.
If this is an issue with a particular app, I have tried filing it in the appropriate issue tracker for the app (e.g. under https://github.com/flathub/) and determined that it is an issue with Flatpak itself.
This issue is not a report of a security vulnerability (see here if you need to report a security issue).
Flatpak version
1.14.4
What Linux distribution are you using?
Debian
Linux distribution version
12
What architecture are you using?
x86_64
How to reproduce
flatpak run --command=sh org.gnome.Loupe
Start process via loupe& in sandbox
Use Loupe to view images which uses flatpak spawn --watch-bus to spawn image loaders
SIGKILL process id of loupe
Exit the flatpak run
Check flatpak ps. The loupe process is still listed, but the pid does not exist. Probably due to the loupe process still being listed, the processes spawned with --watch-bus are not killed.
Expected Behavior
Whenever the loupe process does not longer exist, the --watch-bus processes it spawned should be terminated.no longer exists
Actual Behavior
The --watch-bus processes keep existing until system restart.
It looks like it's possible to also trigger the bug in other ways than SIGKILL. But that is not sure and unclear how.
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Checklist
Flatpak version
1.14.4
What Linux distribution are you using?
Debian
Linux distribution version
12
What architecture are you using?
x86_64
How to reproduce
flatpak run --command=sh org.gnome.Loupe
loupe&
in sandboxflatpak spawn --watch-bus
to spawn image loadersSIGKILL
process id ofloupe
flatpak run
flatpak ps
. Theloupe
process is still listed, but the pid does not exist. Probably due to the loupe process still being listed, the processes spawned with--watch-bus
are not killed.Expected Behavior
Whenever the
loupe
process does not longer exist, the--watch-bus
processes it spawned should be terminated.no longer existsActual Behavior
The
--watch-bus
processes keep existing until system restart.It looks like it's possible to also trigger the bug in other ways than
SIGKILL
. But that is not sure and unclear how.Additional Information
No response
The text was updated successfully, but these errors were encountered: