[probonopd]

Repository: https://github.com/anuzdhk/tuck-filemanager

file manager for linux

• Stars: 14
• Release with the AppImage: v0.1.2 (2026-11-06T08:53:34Z)
• AppImage asset: Tuck-0.1.2-x86_64.AppImage
• License: GPL-3.0

Found by .github/workflows/discover-apps.yml, which looks for GitHub
repositories that publish AppImages but are not in the catalog yet. This
entry was not tested by a human; please review it before merging.

[github-actions]

❌ Test failure

@anuzdhk: this pull request adds the AppImage from your GitHub repository to the AppImage catalog; the test reports the following. Could you have a look?

Tested:

• Tuck-0.1.2-x86_64.AppImage from release v0.1.2

Compatibility: not self-contained: uses the C library of the system; references glibc 2.39

Notes:

• File name 'tuck-filemanager': all-lowercase names are typically used for command line tools, but the desktop file does not set Terminal=true. If this is a graphical application, please name the file after the application as it is spelled, with capitals where it has them (e.g. 'Krita'); if it is a command line tool, set Terminal=true in its desktop file.

• The AppImage needs a newer C library (glibc, or the C++ library libstdc++) than the test system has; the error names the version that is missing (e.g. GLIBC_2.38). The test runs on the oldest Ubuntu LTS release that is still in standard support (see https://ubuntu.com/about/release-cycle), because an AppImage is meant to run on any current Linux distribution, including older ones, and glibc can only be as old as the system the AppImage was built on: a program built on a newer system links against symbols that older systems do not have. The fix is to build on the oldest still-supported LTS release (in GitHub Actions, the oldest ubuntu-* runner still offered, or a container of that release), not on the newest system. If the program itself needs a newer compiler, build in a container of the old release with a newer toolchain (e.g. the toolchain PPAs), statically link what needs it, or bundle the C library together with its dynamic loader (ld-linux) in the AppImage: then the host's glibc does not matter at all (the test reports X-AppImage-Libc=bundled). See https://docs.appimage.org/reference/best-practices.html#binaries-compiled-on-old-enough-base-system

• The application quit or crashed right after starting; the error below usually shows why. Note that the test runs the application without network access, on purpose, and that this is a requirement for the catalog: an AppImage must start without network (users are offline too). If the application needs a server, a login or an update check to start, please make it show its window (or at least a message) first and connect afterwards, and handle a failed connection instead of exiting.

First error in the log:

/run/firejail/appimage/AppRun.wrapped: /lib/x86_64-linux-gnu/libc.so.6: weak version `GLIBC_2.39' not found (required by /run/firejail/appimage/AppRun.wrapped)
/run/firejail/appimage/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.31' not found (required by /run/firejail/appimage/usr/bin/../lib/libpoppler-glib.so.8)
/run/firejail/appimage/AppRun.wrapped: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libglib-2.0.so.0)
/run/firejail/appimage/AppRun.wrapped: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libcairo.so.2)
/run/firejail/appimage/AppRun.wrapped: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libcairo.so.2)
/run/firejail/appimage/AppRun.wrapped: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libvte-2.91-gtk4.so.0)
/run/firejail/appimage/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.15' not found (required by /run/firejail/appimage/usr/bin/../lib/libvte-2.91-gtk4.so.0)
/run/firejail/appimage/AppRun.wrapped: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libgtk-4.so.1)
/run/firejail/appimage/AppRun.wrapped: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libgtk-4.so.1)
/run/firejail/appimage/AppRun.wrapped: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libpango-1.0.so.0)
/run/firejail/appimage/AppRun.wrapped: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libgio-2.0.so.0)
/run/firejail/appimage/AppRun.wrapped: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libgtksourceview-5.so.0)
/run/firejail/appimage/AppRun.wrapped: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found (required by /run/firejail/appimage/usr/bin/../lib/libarchive.so.13)
/run/firejail/appimage/AppRun.wrapped: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libarchive.so.13)
/run/firejail/appimage/AppRun.wrapped: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libadwaita-1.so.0)
/run/firejail/appimage/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /run/firejail/appimage/usr/bin/../lib/libpoppler.so.147)

What next: once the AppImage is fixed (e.g. in a new release), comment /retest here to test it again. If it should not be in the catalog after all, close this pull request; an app that is already in the catalog can be removed by a maintainer with /remove.

Commit c340494. Full log

[anuzdhk]

/retest

[github-actions]

❌ Test failure

Tested:

• Tuck-0.1.4-x86_64.AppImage from release v0.1.4

• The AppImage could not be mounted. appimage.github.io currently supports only AppImages with a SquashFS file system; other formats such as DwarFS (used, e.g., by uruntime and quick-sharun) are not supported yet.

First error in the log:

ERROR: Could not mount the AppImage. appimage.github.io currently supports only AppImages with a SquashFS file system

What next: once the AppImage is fixed (e.g. in a new release), comment /retest here to test it again. If it should not be in the catalog after all, close this pull request; an app that is already in the catalog can be removed by a maintainer with /remove.

Commit c340494. Full log