Reported via Discord — originally attached to #3230's automated triage report, where it was mismatched against an unrelated IPC framing bug. Filing separately so it gets tracked on its own merits.
Original report, quoted verbatim from #3230's body:
Reported by rgadagno7123 in #bugs (Discord, message 1535010190221512886).
Report (PII-redacted):
It does run and does show that breeze-viewer.desktop when i ran that command. I'm running Debian 13 plasma. also tried to install libfuse2 and got Note, selecting 'libfuse2t64' instead of 'libfuse2'
Analysis
The AppImage runtime depends on FUSE2 (libfuse2) to mount itself. On Debian 13, the package has been renamed/split to libfuse2t64 as part of the t64 64-bit time_t transition that affected many *2-suffixed compat packages across Debian 13 and Ubuntu 24.04+. apt install libfuse2 resolves to libfuse2t64 instead of the expected package name, and depending on how the AppImage's embedded loader probes for the library, it may fail to find it under the new name — leaving the viewer unable to mount and run.
Same family as #2614 — Linux viewer AppImage failing to open a window (that report is Ubuntu 24.04, GTK module load errors). Both are viewer-AppImage-on-modern-Debian/Ubuntu packaging problems; this one is specifically the FUSE2 / libfuse2t64 rename on Debian 13.
Provenance: surfaced while triaging #3230 (an IPC out-of-order-frame report). The IPC bug described there was already fixed in 63827f97d (PR #3013, 2026-08-02) before #3230 was filed; the Discord report attached to that issue was mismatched to the wrong symptom by automated triage. See bdunncompany's comment on #3230 for the full mismatch analysis.
Reported via Discord — originally attached to #3230's automated triage report, where it was mismatched against an unrelated IPC framing bug. Filing separately so it gets tracked on its own merits.
Original report, quoted verbatim from #3230's body:
Analysis
The AppImage runtime depends on FUSE2 (
libfuse2) to mount itself. On Debian 13, the package has been renamed/split tolibfuse2t64as part of thet6464-bittime_ttransition that affected many*2-suffixed compat packages across Debian 13 and Ubuntu 24.04+.apt install libfuse2resolves tolibfuse2t64instead of the expected package name, and depending on how the AppImage's embedded loader probes for the library, it may fail to find it under the new name — leaving the viewer unable to mount and run.Same family as #2614 — Linux viewer AppImage failing to open a window (that report is Ubuntu 24.04, GTK module load errors). Both are viewer-AppImage-on-modern-Debian/Ubuntu packaging problems; this one is specifically the FUSE2 /
libfuse2t64rename on Debian 13.Provenance: surfaced while triaging #3230 (an IPC out-of-order-frame report). The IPC bug described there was already fixed in
63827f97d(PR #3013, 2026-08-02) before #3230 was filed; the Discord report attached to that issue was mismatched to the wrong symptom by automated triage. See bdunncompany's comment on #3230 for the full mismatch analysis.