[probonopd]

Repository: https://github.com/GreyTen1/vFinder

vFinder, a file explorer for former macOS users

• Stars: 5
• Release with the AppImage: v0.3.0-alpha (2026-10-23T00:46:57Z); newest release: v0.4.0-alpha
• AppImage asset: vfinder-0.3.0-alpha-x86_64.AppImage
• License: unknown

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

@GreyTen1: 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:

• vfinder-0.3.0-alpha-x86_64.AppImage from release v0.3.0-alpha (the name looks like a pre-release)

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

• 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:

vfinder: /lib/x86_64-linux-gnu/libc.so.6: weak version `GLIBC_2.39' not found (required by vfinder)
vfinder: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libgdk-3.so.0)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /run/firejail/appimage/usr/lib/libgdk-3.so.0)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libgdk-3.so.0)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /run/firejail/appimage/usr/lib/libgdk_pixbuf-2.0.so.0)
vfinder: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libcairo.so.2)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /run/firejail/appimage/usr/lib/libcairo.so.2)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libcairo.so.2)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /run/firejail/appimage/usr/lib/libgobject-2.0.so.0)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /run/firejail/appimage/usr/lib/libglib-2.0.so.0)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.43' not found (required by /run/firejail/appimage/usr/lib/libglib-2.0.so.0)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libglib-2.0.so.0)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /run/firejail/appimage/usr/lib/libdbus-1.so.3)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libdbus-1.so.3)
vfinder: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libwebkit2gtk-4.1.so.0)
vfinder: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.43' not found (required by /run/firejail/appimage/usr/lib/libwebkit2gtk-4.1.so.0)

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 4b61c8a. Full log

[GreyTen1]

/retest

[github-actions]

❌ Test failure

Tested:

• vFinder_0.4.0-alpha_amd64.AppImage from release v0.4.0-alpha (the name looks like a pre-release)

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

• 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:

vfinder: /lib/x86_64-linux-gnu/libc.so.6: weak version `GLIBC_2.39' not found (required by vfinder)
vfinder: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libgdk-3.so.0)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /run/firejail/appimage/usr/lib/libgdk-3.so.0)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libgdk-3.so.0)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /run/firejail/appimage/usr/lib/libgdk_pixbuf-2.0.so.0)
vfinder: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libcairo.so.2)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /run/firejail/appimage/usr/lib/libcairo.so.2)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libcairo.so.2)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /run/firejail/appimage/usr/lib/libgobject-2.0.so.0)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /run/firejail/appimage/usr/lib/libglib-2.0.so.0)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.43' not found (required by /run/firejail/appimage/usr/lib/libglib-2.0.so.0)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libglib-2.0.so.0)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /run/firejail/appimage/usr/lib/libdbus-1.so.3)
vfinder: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libdbus-1.so.3)
vfinder: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libwebkit2gtk-4.1.so.0)
vfinder: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.43' not found (required by /run/firejail/appimage/usr/lib/libwebkit2gtk-4.1.so.0)

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 4b61c8a. Full log

[GreyTen1]

/retest

[github-actions]

✅ Test passed

Please check that the screenshot shows the application's main window.

vFinder

Tested:

• vFinder_0.4.0-alpha_amd64.AppImage from release v0.4.0-alpha (the name looks like a pre-release)

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

Warnings:

• The window is mostly dark, so the application seems to start in a dark theme although the test system is not set to dark mode. Please use a light mode by default and use the dark theme only when the system is configured for dark mode (e.g. the GTK/Qt or theme setting) or the user chooses it in the settings.
• The AppImage contains no update information, so users cannot update it with AppImageUpdate or similar tools. Please consider embedding it when building the AppImage (e.g., appimagetool -u) and publishing the .zsync file next to the AppImage; see https://docs.appimage.org/packaging-guide/optional/updates.html

Commit 4b61c8a. Full log