[probonopd]

Repository: https://github.com/stellio-app/stellio

Modern desktop application built with Python to seamlessly manage and run your local media and scripts.

• Stars: 5
• Release with the AppImage: v0.8.4 (2026-11-03T19:59:41Z)
• AppImage asset: Stellio-v0.8.4-linux-x86_64.AppImage
• License: AGPL-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

@stellio-app: 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:

• Stellio-v0.8.4-linux-x86_64.AppImage from release v0.8.4

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

Names:

WARNING: AppImage name 'Stellio-v0.8.4-linux-x86_64.AppImage': should not contain 'Linux', since all AppImages are for Linux (e.g. 'App-1.0-x86_64.AppImage', not 'App-1.0-linux-x86_64.AppImage')

• 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.
• Please check the remarks about the names below.

First error in the log:

[PYI-4:ERROR] Failed to load Python shared library '/run/firejail/appimage/usr/bin/_internal/libpython3.11.so.1.0': /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/_internal/libpython3.11.so.1.0)

The application showed no window, but may be a system tray application (usr/bin/_internal/gi_typelibs/Gtk-3.0.typelib: gtk_status_icon_new); running it again with a system tray
[PYI-4:ERROR] Failed to load Python shared library '/run/firejail/appimage/usr/bin/_internal/libpython3.11.so.1.0': /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/_internal/libpython3.11.so.1.0)
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 b564a84. Full log

[stellio-app]

/retest

[github-actions]

❌ Test failure

Tested:

• Stellio-v0.9.4-x86_64.AppImage from release v0.9.4

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:

Traceback (most recent call last):
  File "launcher.py", line 160, in <module>
  File "launcher.py", line 119, in main
  File "launcher.py", line 45, in _setup_bootstrap_logger
  File "pathlib.py", line 1116, in mkdir
OSError: [Errno 30] Read-only file system: '/run/firejail/appimage/usr/bin/logs'
[PYI-4:ERROR] Failed to execute script 'launcher' due to unhandled exception!

The application showed no window, but may be a system tray application (usr/bin/_internal/gi_typelibs/Gtk-3.0.typelib: gtk_status_icon_new); running it again with a system tray
Traceback (most recent call last):
  File "launcher.py", line 160, in <module>
  File "launcher.py", line 119, in main
  File "launcher.py", line 45, in _setup_bootstrap_logger
  File "pathlib.py", line 1116, in mkdir
OSError: [Errno 30] Read-only file system: '/run/firejail/appimage/usr/bin/logs'
[PYI-4:ERROR] Failed to execute script 'launcher' due to unhandled exception!

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

[stellio-app]

/retest

[github-actions]

✅ Test passed

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

Stellio

Tested:

• Stellio-v0.9.4-x86_64.AppImage from release v0.9.4

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