Skip to content

Add SRT_Router - #6815

Open
probonopd wants to merge 1 commit into
masterfrom
discover/SRT_Router
Open

probonopd wants to merge 1 commit into
masterfrom
discover/SRT_Router

Conversation

@probonopd

Copy link
Copy Markdown
Member

Repository: https://github.com/stoatworks-labs/srt-router

A crosspoint-based SRT router: any number of SRT inputs/outputs with a broadcast-router-style crosspoint (each output picks one live-switchable source), a web UI, and runtime add/remove. Pure relay (no transcode); NDI transport included. Rust. Downloads: https://stoatworks-labs.com/software/srt-rout

  • Stars: 5
  • Release with the AppImage: v0.2.4 (2026-09-18T02:02:31Z)
  • AppImage asset: SRT.Router_0.2.4_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.

Possibly not from the application's authors: the README says "not affiliated" (label not-upstream). Please check whether the catalog should list this AppImage, or rather one from the application's own project.

Discovered on GitHub as publishing AppImages on its releases, by
discover-apps.yml. Needs a maintainer's review.
@probonopd probonopd added auto-discovered not-upstream The AppImage is not published nor linked by the application author labels Sep 29, 2026
@github-actions github-actions Bot added error-app-exits Test failed: the application quit or crashed right after starting error-not-executable Test failed: a file inside the AppImage is not executable labels Sep 29, 2026
@github-actions

Copy link
Copy Markdown
Contributor

❌ Test failure

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

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

  • A file inside the AppImage is not executable. Please check the file permissions before packaging the AppImage.
  • The application quit or crashed right after starting. The error below usually shows why.

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/libappindicator3.so.1: libappindicator3.so.1); 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 a1e6caf. Full log

@probonopd probonopd removed the not-upstream The AppImage is not published nor linked by the application author label Oct 1, 2026
@stoatworks-labs

Copy link
Copy Markdown

/retest

@probonopd probonopd closed this Nov 9, 2026
@probonopd probonopd reopened this Nov 9, 2026
@github-actions github-actions Bot added error-glibc-too-new Test failed: built on a too new system (needs a newer glibc) and removed error-not-executable Test failed: a file inside the AppImage is not executable labels Nov 9, 2026
@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

❌ Test failure

Tested:

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:

av-launcher: /lib/x86_64-linux-gnu/libc.so.6: weak version `GLIBC_2.39' not found (required by av-launcher)
av-launcher: /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)
av-launcher: /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)
av-launcher: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libcairo.so.2)
av-launcher: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libcairo.so.2)
av-launcher: /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)
av-launcher: /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)
av-launcher: /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)
av-launcher: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libwebkit2gtk-4.1.so.0)
av-launcher: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libgtk-3.so.0)
av-launcher: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libgtk-3.so.0)
av-launcher: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libsoup-3.0.so.0)
av-launcher: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libgio-2.0.so.0)
av-launcher: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libjavascriptcoregtk-4.1.so.0)
av-launcher: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libjavascriptcoregtk-4.1.so.0)
av-launcher: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libpango-1.0.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 a1e6caf. Full log

stoatworks-labs added a commit to stoatworks-labs/srt-router that referenced this pull request Nov 9, 2026
The AppImage catalogue (AppImage/appimage.github.io#6815) runs every
AppImage on the oldest Ubuntu LTS still in standard support. v0.2.5's
launcher was built on ubuntu-latest (24.04, glibc 2.39) and died there
with "GLIBC_2.38 not found", both in av-launcher and in the GTK/cairo
libraries linuxdeploy copied in from the runner. The CLI tarballs, .deb
and .rpm had the same floor.

Build every Linux row on 22.04 (glibc 2.35) instead: the CLI x86_64 and
aarch64 rows and the launcher's Linux row. The rust-cache key now
includes the runner image, so build scripts cached on 24.04 are never
restored onto 22.04, where they would not run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@stoatworks-labs

Copy link
Copy Markdown

/retest

@probonopd probonopd closed this Nov 9, 2026
@probonopd probonopd reopened this Nov 9, 2026
@github-actions github-actions Bot removed error-app-exits Test failed: the application quit or crashed right after starting error-glibc-too-new Test failed: built on a too new system (needs a newer glibc) labels Nov 9, 2026
@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

✅ Test passed

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

SRT_Router

SRT_Router

Tested:

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

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants