Skip to content

Add TennoScope - #6700

Merged
probonopd merged 1 commit into
masterfrom
discover/TennoScope
Oct 11, 2026
Merged

probonopd merged 1 commit into
masterfrom
discover/TennoScope

Conversation

@probonopd

Copy link
Copy Markdown
Member

Repository: https://github.com/Deftera186/tennoscope

Local-first Warframe companion: relic reward overlay and value advisor

  • Stars: 23
  • Release with the AppImage: v0.12.0 (2026-09-24T16:32:59Z)
  • AppImage asset: TennoScope_0.12.0_amd64.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.

Possibly not from the application's authors: the README says "unofficial" (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

@Deftera186: 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/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 b5e5a91. Full log

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

Copy link
Copy Markdown

v0.13.0 is out with this fixed. It was a file mode, not a code problem.

AppRun.wrapped shipped at 770, and it was the only entry in the whole
payload without world read or execute. Your harness runs the image
sandboxed as a user who is neither owner nor group, so AppRun's
exec of it fell through to the other bits and died with EACCES
before a window could exist.

The build now normalizes world bits across the AppDir before packing and
asserts the extracted payload afterwards, so it cannot regress. Verified
on the published v0.13.0 asset: AppRun.wrapped is 775, no file lacks
world read, no executable lacks world execute.

The glibc 2.39 line in the compatibility report is a false alarm worth
ignoring: the only 2.39 symbols in the binary are weak imports
(pidfd_spawnp, pidfd_getpid), which the loader resolves to NULL
rather than failing on an older glibc.

/retest

@probonopd probonopd closed this Oct 2, 2026
@probonopd probonopd reopened this Oct 2, 2026
@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

❌ Test failure

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

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

@Deftera186

Copy link
Copy Markdown

The re-test ran, but it downloaded the wrong release. From the log:

URL from GitHub API:
https://github.com/Deftera186/tennoscope/releases/download/v0.11.0/TennoScope_0.11.0_amd64.AppImage

v0.11.0 predates the fix by three releases, so of course it still reports
the 0770 launcher. The PR description also still points at v0.12.0.

For the record, the artifact that is actually fixed is v0.13.0
(TennoScope_0.13.0_amd64.AppImage):

$ ./TennoScope_0.13.0_amd64.AppImage --appimage-extract
$ stat -c '%a' squashfs-root/AppRun.wrapped
775
$ find squashfs-root -type f ! -perm -004 | wc -l
0

Happy to re-run whenever the discovery picks a current release.

probonopd added a commit that referenced this pull request Oct 2, 2026
…hannel

A latest-beta.json update feed (TennoScope uploads one to the latest stable
release) made that release look like the beta channel, so the previous
release was picked instead (#6700).

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DZvaN9tm5taf5avUvVtmyq
probonopd added a commit that referenced this pull request Oct 2, 2026
…mes only; log the release choice (#9636)

* find-appimage: list the newest releases and the chosen one in the log

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DZvaN9tm5taf5avUvVtmyq

* find-appimage: only the tag and the AppImage names tell a release's channel

A latest-beta.json update feed (TennoScope uploads one to the latest stable
release) made that release look like the beta channel, so the previous
release was picked instead (#6700).

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DZvaN9tm5taf5avUvVtmyq

---------

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
@probonopd

Copy link
Copy Markdown
Member Author

/retest

@probonopd probonopd closed this Oct 2, 2026
@probonopd probonopd reopened this Oct 2, 2026
@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

❌ Test failure

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

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

@Deftera186

Copy link
Copy Markdown

/retest

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

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

❌ Test failure

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

  • The AppImage was built on a system that is too new. Please build it on the oldest still-supported Ubuntu LTS release so that it runs on all supported systems.
  • The application quit or crashed right after starting. The error below usually shows why.

First error in the log:

tennoscope: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.39' not found (required by tennoscope)
tennoscope: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libpipewire-0.3.so.0)
tennoscope: /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)
tennoscope: /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)
tennoscope: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libcairo.so.2)
tennoscope: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/lib/libcairo.so.2)
tennoscope: /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)
tennoscope: /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)
tennoscope: /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)
tennoscope: /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)
tennoscope: /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)
tennoscope: /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)
tennoscope: /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)
tennoscope: /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)
tennoscope: /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)
tennoscope: /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)

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

@Deftera186

Copy link
Copy Markdown

/retest

v0.13.1 is the latest release and its AppImage is the one to test now. Two things changed since the last run:

  • The Linux AppImage is built on Ubuntu 22.04 again, with PipeWire 1.0.0 built from source inside the job so the app's bindings compile against jammy's toolchain. What linuxdeploy bundles is jammy-built, so nothing in the AppDir references newer than glibc 2.35. Checked with the catalog's own code/check-libc.sh against the published asset: X-AppImage-Glibc-Required=GLIBC_2.35.
  • The launcher modes from the v0.13.0 fix hold: AppRun 755, AppRun.wrapped 775, and zero files without world read.

Sorry the earlier retests kept downloading v0.11.0; that one predates both fixes.

@probonopd probonopd closed this Oct 11, 2026
@probonopd probonopd reopened this Oct 11, 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 Oct 11, 2026
@github-actions github-actions Bot added the screenshot-ok Test passed; the screenshot was checked and looks fine label Oct 11, 2026
@github-actions

Copy link
Copy Markdown
Contributor

✅ Test passed

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

TennoScope

TennoScope

Tested:

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

Warnings:

Commit b5e5a91. Full log

@probonopd
probonopd merged commit f304cd0 into master Oct 11, 2026
11 of 15 checks passed
@probonopd
probonopd deleted the discover/TennoScope branch October 11, 2026 07:05
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