[probonopd]

Repository: https://github.com/RamazanKara/nightjar

Turn your PC into a console and play it on every screen you own. Nightjar streams your PC games to Android phones, handhelds, Android TV, Windows and Linux, with Steam, Epic, GOG, EA, Ubisoft, Battle.net and Xbox games in one console library. Near-zero decoding on Snapdragon 8 Elite. Works with Ruby

• Stars: 72
• Release with the AppImage: v4.0.0-alpha.2 (2026-10-29T14:03:11Z)
• AppImage asset: nightjar-desktop-4.0.0-alpha.2-linux-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

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

• nightjar-desktop-4.0.0-alpha.2-linux-x86_64.AppImage from release v4.0.0-alpha.2 (marked as a pre-release)

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

Names:

WARNING: AppImage name 'nightjar-desktop-4.0.0-alpha.2-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 application needs a library that is neither in the AppImage nor on the test system ("error while loading shared libraries", the first error below names it). Please bundle this library, and what it depends on, in the AppImage: an AppImage cannot rely on libraries that are not installed on every target 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:

/run/firejail/appimage/AppRun: error while loading shared libraries: libva.so.2: cannot open shared object file: No such file or directory

The application showed no window, but may be a system tray application (nightjar: app_indicator_new); running it again with a system tray
/run/firejail/appimage/AppRun: error while loading shared libraries: libva.so.2: cannot open shared object file: No such file or directory
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 d0e8b00. Full log

[RamazanKara]

/retest

[github-actions]

❌ Test failure

Tested:

• nightjar-desktop-4.0.0-x86_64.AppImage from release v4.0.0

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

• 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/nightjar: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/nightjar)
/run/firejail/appimage/nightjar: /lib/x86_64-linux-gnu/libc.so.6: weak version `GLIBC_2.39' not found (required by /run/firejail/appimage/nightjar)
/run/firejail/appimage/nightjar: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/lib/fallback/libva/libva.so.2)

The application showed no window, but may be a system tray application (nightjar: app_indicator_new); running it again with a system tray
/run/firejail/appimage/nightjar: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/nightjar)
/run/firejail/appimage/nightjar: /lib/x86_64-linux-gnu/libc.so.6: weak version `GLIBC_2.39' not found (required by /run/firejail/appimage/nightjar)
/run/firejail/appimage/nightjar: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/lib/fallback/libva/libva.so.2)
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 d0e8b00. Full log

[RamazanKara]

/retest

[github-actions]

✅ Test passed

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

Nightjar

Tested:

• nightjar-desktop-4.0.1-x86_64.AppImage from release v4.0.1

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