Skip to content

Add Clutch - #7893

Merged
github-actions[bot] merged 1 commit into
masterfrom
discover/Clutch
Oct 15, 2026
Merged

github-actions[bot] merged 1 commit into
masterfrom
discover/Clutch

Conversation

@probonopd

Copy link
Copy Markdown
Member

Repository: https://github.com/shitz/clutch

Clutch a modern transmission RPC client built in pure Rust using iced.

  • Stars: 16
  • Release with the AppImage: v0.14.0 (2026-04-11T18:52:19Z)
  • AppImage asset: clutch_0.14.0_x86_64.AppImage
  • License: Apache-2.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.

Discovered on GitHub as publishing AppImages on its releases, by
discover-apps.yml. Needs a maintainer's review.
@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

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

/bin/bash: line 1: /run/firejail/appimage/AppRun: Permission denied

The application showed no window, but may be a system tray application (usr/bin/clutch: app_indicator_new); running it again with a system tray
/bin/bash: line 1: /run/firejail/appimage/AppRun: 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 8cce872. Full log

@shitz

shitz commented Oct 12, 2026

Copy link
Copy Markdown

/retest

@probonopd probonopd closed this Oct 12, 2026
@probonopd probonopd reopened this Oct 12, 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 Oct 12, 2026
@github-actions

Copy link
Copy Markdown
Contributor

❌ Test failure

Tested:

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

Names:

WARNING: The names of the repository, the AppImage and the README differ: repository 'clutch', AppImage 'clutch', README 'Features'
  • 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.
  • 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:

clutch: /lib/x86_64-linux-gnu/libc.so.6: weak version `GLIBC_2.39' not found (required by clutch)
clutch: /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)
clutch: /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)
clutch: /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)
clutch: /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)
clutch: /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)
clutch: /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)
clutch: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libcrypto.so.3)
clutch: /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)
clutch: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libcairo.so.2)
clutch: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libcairo.so.2)
clutch: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libatk-bridge-2.0.so.0)
clutch: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libxkbcommon.so.0)
clutch: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libwayland-client.so.0)
clutch: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libXcursor.so.1)
clutch: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found (required by /run/firejail/appimage/usr/lib/libmount.so.1)

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 8cce872. Full log

@shitz

shitz commented Oct 12, 2026

Copy link
Copy Markdown

/retest

@probonopd probonopd closed this Oct 12, 2026
@probonopd probonopd reopened this Oct 12, 2026
@github-actions github-actions Bot removed the error-glibc-too-new Test failed: built on a too new system (needs a newer glibc) label Oct 12, 2026
@github-actions

Copy link
Copy Markdown
Contributor

❌ Test failure

Tested:

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 8cce872. Full log

@shitz

shitz commented Oct 15, 2026

Copy link
Copy Markdown

/retest

@probonopd probonopd closed this Oct 15, 2026
@probonopd probonopd reopened this Oct 15, 2026
@github-actions github-actions Bot added screenshot-ok Test passed; the screenshot was checked and looks fine and removed error-app-exits Test failed: the application quit or crashed right after starting labels Oct 15, 2026
@github-actions

Copy link
Copy Markdown
Contributor

✅ Test passed

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

Clutch

Clutch

Tested:

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

Warnings:

Commit 8cce872. Full log

@github-actions
github-actions Bot merged commit acefa62 into master Oct 15, 2026
11 of 14 checks passed
@github-actions
github-actions Bot deleted the discover/Clutch branch October 15, 2026 06:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-discovered screenshot-ok Test passed; the screenshot was checked and looks fine

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants