~/apps/LosslessCut-linux*.AppImage
[35849:0224/233348.633441:FATAL:sandbox/linux/suid/client/setuid_sandbox_host.cc:166] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I’m aborting now. You need to make sure that /tmp/.mount_LossleOtd8cF/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap (core dumped)
$HOME/apps/LBRY_*.AppImage
[36233:0224/233554.366594:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I’m aborting now. You need to make sure that /tmp/.mount_LBRY_0oSPBa5/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap (core dumped)
$ /home/user/apps/session-desktop-linux-x86_64-*.AppImage
[62637:0225/002423.306576:FATAL:content/browser/zygote_host/zygote_host_impl_linux.cc:128] No usable sandbox! If you are running on Ubuntu 23.10+ or another Linux distro that has disabled unprivileged user namespaces with AppArmor, see
Chromium Docs - AppArmor User Namespace Restrictions vs. Chromium Developer Builds . Otherwise see Chromium Docs - Linux SUID Sandbox Development for more information on deve
loping with the (older) SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
Please how can i fix it (or workaround it) beside using –no-sandbox switch which i am unsure if is good idea security-wise and without manually extracting and reworking appimage each time it is released?
Similar topic that does not mention other solution: