Warpinator 1.6.0, on Debian 11 and on NixOS unstable.
When running warpinator -m bubblewrap in the terminal, it enters a /bin/sh shell instead of launching the app.
$ warpinator -m bubblewrap
Using bubblewrap for incoming file isolation. Write access for the application will be limited to the save directory only.
sh-5.2$
Since when I warpinator -m landlock and/or warpinator -m legacy it starts the gtk app, I expect the bubblewrap mode to do the same thing. Or do I have to manually execute warpinator again in the shell?
Warpinator 1.6.0, on Debian 11 and on NixOS unstable.
When running
warpinator -m bubblewrap
in the terminal, it enters a/bin/sh
shell instead of launching the app.Since when I
warpinator -m landlock
and/orwarpinator -m legacy
it starts the gtk app, I expect the bubblewrap mode to do the same thing. Or do I have to manually execute warpinator again in the shell?Relevant launch_args I think:
https://github.com/linuxmint/warpinator/blob/f34a0cf5dadbca9f420b4d87fcf5b913e390aa7e/src/warpinator-launch.py#L150