PR #7765
AppImage launch test
Build AppImage with the static runtime toolset
Tested commit 5046bc938fed1a8dd0991136a31fc69726267129.
Result: launch checks pass
Built the actual T3 Code AppImage from the current PR and launched it inside a disposable Ubuntu 24.04 VM. The VM had FUSE 3 and no system libfuse.so.2. No extraction mode was used.
| Check | Observed result |
|---|---|
| Legacy-runtime control | Fails before Electron: dlopen(): error loading libfuse.so.2. |
| PR runtime | Mounts successfully. The kernel mount table shows a real read-only FUSE AppImage filesystem. |
| Application startup | Backend ready; main window created; full T3 interface rendered. |
| Sandbox fallback | Ubuntu denied the user-namespace probe. The launcher supplied --no-sandbox; it was not passed manually. |
| Close and restart | A new process mounted the AppImage and reopened T3 using the same isolated application state. |
The control used the same source and compiled application output, with only the runtime pin removed for packaging. That temporary change was restored.
Running inside the VM
What this establishes
The change fixes the missing-libfuse2 launch failure on the tested Ubuntu 24.04 x64 environment. FUSE support is still required for normal mounting.
The application was built with Electron 44.4.2 and electron-builder 26.15.6. The graphical check used Xvfb and --disable-gpu because the VM has no accelerated display.
Merge risk: no regression found in this launch test. Other distributions, ARM64, accelerated graphics, and the updater flow were not retested in this VM. Earlier fixture-based updater results are not counted as evidence for this run.
Cleanup
Removed the previous test worktree, fixtures, AppImages, extracted application files, and logs. The new test application and VM were stopped; the temporary VM, build checkout, keys, and artifacts were removed after capturing this report. The working repository was left unchanged.