Skip to content

Add Luminous - #6392

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

probonopd wants to merge 1 commit into
masterfrom
discover/Luminous

Conversation

@probonopd

Copy link
Copy Markdown
Member

Repository: https://github.com/esoltys/luminous

A high-performance home for the music you already own. Luminous is a fast, local-first player for your own audio library.

  • Stars: 28
  • Release with the AppImage: v0.99.1 (2026-08-11T00:13:28Z); newest release: v2.6.0
  • AppImage asset: Luminous_0.99.1_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.

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

@esoltys: 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.35

  • 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

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 0bb527a. Full log

@esoltys

esoltys commented Sep 29, 2026

Copy link
Copy Markdown

Luminous deliberately stopped shipping an AppImage after v0.99.1 because of an upstream Tauri/WebKitGTK EGL issue (the bundled graphics stack collides with the host's, giving a blank window), so the 0.99.1 build this found is stale and known-broken. Linux users should use the .deb/.rpm or Flatpak from the releases page.

Please close.

@probonopd probonopd added the toolchain-issue This issue may affect all AppImages built with an certain toolchain label Sep 29, 2026
@probonopd

Copy link
Copy Markdown
Member Author

Hi @esoltys, thanks for your response. Do you happen to know a Tauri GitHub Issue describing this situation? I would like to help them produce properly working AppImages. It can be done.

@esoltys

esoltys commented Sep 29, 2026 •

Copy link
Copy Markdown

tauri-apps/tauri#11988

[Edit]

  • tauri-apps/tauri#15665 (July 2026): default AppImages fail on distros with Mesa 25 or newer because the bundler packs in too many libraries.
  • tauri-apps/tauri#15976 (September 2026): reports the exact EGL_BAD_PARAMETER crash from bundled libwayland/libxkbcommon/libxcb on newer Mesa. A maintainer made this the tracking issue for the EGL problem.
  • tauri-apps/tauri#10749 (2024): similar Fedora 40 failure, closed as not planned. tauri-apps/tauri#5143, the general "blank screen" issue, is still open.

Oh, maybe it's been fixed by tauri-apps/tauri#16062 From a few days ago. Hmm.

@esoltys

esoltys commented Sep 29, 2026

Copy link
Copy Markdown

Feature: Restore AppImage distribution with GPU rendering (Tauri CLI 2.12 fix)

@esoltys

esoltys commented Sep 29, 2026

Copy link
Copy Markdown

Yeah, builds for both Wayland and X11 look good. I'll have an AppImage in the next release and I'll post it here.

@esoltys

esoltys commented Oct 14, 2026

Copy link
Copy Markdown

/retest

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

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

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

@esoltys

esoltys commented Oct 14, 2026

Copy link
Copy Markdown

Hmm. I'll have to look in to changing my workflow to build on ubuntu-22.04 instead of ubuntu-24.04 for the appimage. I'll see what I can do.

@esoltys

esoltys commented Oct 14, 2026

Copy link
Copy Markdown

/retest

@probonopd probonopd closed this Oct 14, 2026
@probonopd probonopd reopened this Oct 14, 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 error-glibc-too-new Test failed: built on a too new system (needs a newer glibc) labels Oct 14, 2026
@github-actions

Copy link
Copy Markdown
Contributor

✅ Test passed

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

Luminous

Luminous

Tested:

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

Warnings:

Commit 0bb527a. Full log

@esoltys

esoltys commented Oct 15, 2026

Copy link
Copy Markdown

@probonopd Anything else you need from me?

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

Labels

auto-discovered screenshot-ok Test passed; the screenshot was checked and looks fine toolchain-issue This issue may affect all AppImages built with an certain toolchain

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants