[probonopd]

Repository: https://github.com/kostyk348/CapsuleCraft

CapsuleCraft - zero-database, pure-MIME multimodal workspace and personal knowledge engine. Every note is an RFC 5322 .eml file. Native desktop + Web version too

• Stars: 5
• Release with the AppImage: v1.4.0 (2026-10-23T08:45:46Z)
• AppImage asset: CapsuleOS_1.4.0_amd64.AppImage
• License: MIT

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

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

• CapsuleOS_1.4.0_amd64.AppImage from release v1.4.0

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

Names:

WARNING: File name 'CapsuleCraft': does not match the name of the application in its desktop file ('CapsuleOS'); the file should be named after the application
WARNING: The names of the repository, the AppImage and the README differ: repository 'CapsuleCraft', AppImage 'CapsuleOS', README 'CapsuleCraft'

• A file inside the AppImage is not executable. Please check the file permissions before packaging the AppImage.
• AppRun.wrapped (or the launcher it starts) could not be executed. This typically happens with Tauri and linuxdeploy builds when a cached launcher was packaged with mode 0770 and is owned by root, so that it is not executable for the test user. Please make the AppDir readable and executable for everyone before packaging, e.g. chmod -R a+rX AppDir (and chmod a+x on AppRun and AppRun.wrapped) before running appimagetool.
• 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.
• Please check the remarks about the names below.
• The repository, the AppImage and the README (whichever exist) call the application by different names (see the remarks below). Please check that they all belong to the same application, and that the name of the file in data/ is the right one.

First error in the log:

/run/firejail/appimage/AppRun: line 12: /run/firejail/appimage/AppRun.wrapped: Permission denied

The application showed no window, but may be a system tray application (usr/lib/girepository-1.0/AyatanaAppIndicator3-0.1.typelib: app_indicator_new); running it again with a system tray
/run/firejail/appimage/AppRun: line 12: /run/firejail/appimage/AppRun.wrapped: Permission denied
No icon appeared in the system tray either
ERROR: The application exited within 11 seconds instead of showing a window

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 a57c004. Full log

[kostyk348]

Newest version should fit the requirements

[kostyk348]

/retest

[github-actions]

❌ Test failure

Tested:

• CapsuleCraft_1.5.0_amd64.AppImage from release v1.6.0

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

• A file inside the AppImage is not executable. Please check the file permissions before packaging the AppImage.
• AppRun.wrapped (or the launcher it starts) could not be executed. This typically happens with Tauri and linuxdeploy builds when a cached launcher was packaged with mode 0770 and is owned by root, so that it is not executable for the test user. Please make the AppDir readable and executable for everyone before packaging, e.g. chmod -R a+rX AppDir (and chmod a+x on AppRun and AppRun.wrapped) before running appimagetool.
• 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: line 12: /run/firejail/appimage/AppRun.wrapped: Permission denied

The application showed no window, but may be a system tray application (usr/lib/girepository-1.0/AyatanaAppIndicator3-0.1.typelib: app_indicator_new); running it again with a system tray
/run/firejail/appimage/AppRun: line 12: /run/firejail/appimage/AppRun.wrapped: Permission denied
No icon appeared in the system tray either
ERROR: The application exited within 11 seconds instead of showing a window

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 a57c004. Full log

[kostyk348]

/retest

[github-actions]

❌ Test failure

Tested:

• CapsuleCraft_1.7.0_amd64.AppImage from release v1.7.0

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

• 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: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.43' not found (required by /run/firejail/appimage/AppRun)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: weak version `GLIBC_2.39' not found (required by /run/firejail/appimage/AppRun)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /run/firejail/appimage/usr/bin/../lib/libssl.so.3)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libssl.so.3)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /run/firejail/appimage/usr/bin/../lib/libcrypto.so.3)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libcrypto.so.3)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /run/firejail/appimage/usr/bin/../lib/libbrotlienc.so.1)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /run/firejail/appimage/usr/bin/../lib/libbrotlidec.so.1)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /run/firejail/appimage/usr/bin/../lib/libzstd.so.1)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /run/firejail/appimage/usr/bin/../lib/libbrotlicommon.so.1)

ERROR: The application exited within 11 seconds instead of showing a window

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 a57c004. Full log

[kostyk348]

/retest

[kostyk348]

/retest

[github-actions]

❌ Test cancelled

Tested:

• CapsuleCraft_1.7.0_amd64.AppImage from release v1.7.0

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

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

ERROR: The application exited within 11 seconds instead of showing a window

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 a57c004. Full log

[github-actions]

❌ Test failure

Tested:

• CapsuleCraft_1.7.0_amd64.AppImage from release v1.7.0

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

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

ERROR: The application exited within 11 seconds instead of showing a window

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 a57c004. Full log

[kostyk348]

/retest

[github-actions]

❌ Test failure

Tested:

• CapsuleCraft_1.7.0_amd64.AppImage from release v1.7.0

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

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

ERROR: The application exited within 11 seconds instead of showing a window

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 a57c004. Full log

[kostyk348]

/retest

[github-actions]

✅ Test passed

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

CapsuleCraft

Tested:

• CapsuleCraft_1.7.0_amd64.AppImage from release v1.7.0

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 a57c004. Full log