Thinking about it, it makes way more sense to use the tarball version that Viper offers instead of the AppImage, as the later expects itself to be in a certain format.
This can cause issues like being unable to launch Viper after a manual language change in its settings menu, as can be seen in the log below:
$ flatpak run com.github._0negal.Viper
[3 zypak-helper] Portal v4 is not available
Gtk-Message: 00:28:34.096: Failed to load module "canberra-gtk-module"
Gtk-Message: 00:28:34.096: Failed to load module "canberra-gtk-module"
[3:0417/002834.120552:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
APPIMAGE env is not defined, current application is not an AppImage
Checking for Northstar updates...
No Northstar update available.
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[35:0417/002834.283532:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
APPIMAGE env is not defined, current application is not an AppImage
^C
Thinking about it, it makes way more sense to use the tarball version that Viper offers instead of the AppImage, as the later expects itself to be in a certain format.
This can cause issues like being unable to launch Viper after a manual language change in its settings menu, as can be seen in the log below: