[Bug] AppImage Fails to Start — Forced to Use .deb Package Instead

[salem221094]

Problem Description

The AppImage fails to launch entirely. The only working workaround was to install the app via the .deb package.

Steps to Reproduce

1. Download and attempt to run the provided AppImage.
2. Observe that it fails to start.
3. Install via the .deb package instead — app starts successfully.

Expected Behavior

• The AppImage should launch without issues out of the box.
• If it fails, a clear and descriptive error message should be shown to help the user understand what went wrong.

Suggested Fix

• Investigate and fix the AppImage build/packaging configuration.
• Test the AppImage on common Linux distributions before release.

Priority: High

[Git-Rocky-Stack]

Jumping on this now...

[Git-Rocky-Stack]

Thanks for the detailed report — you flagged a real gap, and there's a fix up now (#15).

Root cause: the AppImage runtime needs FUSE 2 (libfuse.so.2) on the host to mount itself. Ubuntu 22.04+ stopped installing it by default, and 24.04 renamed the package to libfuse2t64 — so on a stock modern Ubuntu the AppImage dies before our code runs. Your .deb works because it installs as a normal package with no FUSE dependency. That "deb works, AppImage doesn't" split is the classic signature.

Unblock yourself right now — two options:

1. No install, run in place:

   ./Team-X-<version>-x64.AppImage --appimage-extract-and-run
   

2. Install FUSE 2 once:
   • Ubuntu 24.04: sudo apt install libfuse2t64
   • Ubuntu 22.04 / Debian: sudo apt install libfuse2
   • Fedora: sudo dnf install fuse-libs

(You're already on the .deb, which is honestly the smoothest Linux path — fine to stay there.)

What's being fixed (#15):

• README, quick-start, and FAQ now document the FUSE requirement + the one-liner workaround (our docs previously implied the AppImage was dependency-free — that was wrong, now corrected).
• The release pipeline now boots the AppImage headlessly before publishing, so a non-starting build can't ship again. Your "test it before release" point was spot on — we genuinely weren't.

One ask to close the loop: could you paste the exact error from running it in a terminal (./Team-X-*.AppImage), plus lsb_release -a? If it's the libfuse.so.2 message, we've nailed it. If instead you see a sandbox / user-namespace error (also common on 24.04), that's a separate issue and I'd want to chase that down too.

Appreciate you filing this properly.