Skip to content

Add DRH_Launcher - #9233

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

probonopd wants to merge 1 commit into
masterfrom
discover/DRH_Launcher

Conversation

@probonopd

Copy link
Copy Markdown
Member

Repository: https://github.com/Tutez64/DRH-Launcher

Official launcher for Dungeon Rampage Haxe.

  • Stars: 8
  • Release with the AppImage: v0.3.0 (2026-09-08T20:19:54Z)
  • AppImage asset: DRH-Launcher_0.3.0_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.

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 30, 2026
@github-actions

Copy link
Copy Markdown
Contributor

❌ Test failure

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

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

Tutez64 added a commit to Tutez64/DRH-Launcher that referenced this pull request Oct 12, 2026
Fixes AppImage/appimage.github.io#9233

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

Tutez64 commented Oct 23, 2026

Copy link
Copy Markdown

/retest

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

DRH-Launcher: /lib/x86_64-linux-gnu/libc.so.6: weak version `GLIBC_2.39' not found (required by DRH-Launcher)
DRH Launcher panicked: panicked at /home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/xkbcommon-dl-0.4.2/src/x11.rs:59:28:
Library libxkbcommon-x11.so could not be loaded.

thread 'main' (4) panicked at /home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/xkbcommon-dl-0.4.2/src/x11.rs:59:28:
Library libxkbcommon-x11.so could not be loaded.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

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

Tutez64 added a commit to Tutez64/DRH-Launcher that referenced this pull request Oct 28, 2026
@Tutez64

Tutez64 commented Oct 28, 2026

Copy link
Copy Markdown

/retest

@probonopd probonopd closed this Oct 28, 2026
@probonopd probonopd reopened this Oct 28, 2026
@github-actions github-actions Bot added error-message-on-screen Test failed: the screenshot shows an error message 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 28, 2026
@github-actions

Copy link
Copy Markdown
Contributor

❌ Test failure

DRH_Launcher

DRH_Launcher

Tested:

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

  • The screenshot shows an error message (see below).
  • 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.

First error in the log:

ERROR: The screenshot shows an error message: DRH Launcher Home Options Ll 4 Not installed @ Discord Mods Install DRH Launcher? a(S ey Cedar DRH Launc
Screenshot: letters by script: 190 Latin, 0 Chinese/Japanese/Korean, 0 Arabic, 0 Cyrillic/Greek

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

@Tutez64

Tutez64 commented Oct 28, 2026

Copy link
Copy Markdown

The remaining failure is a false positive: "Not installed" in the screenshot is not an error. It is DRH Launcher's status line for the game it manages ("Dungeon Rampage Haxe: Not installed"), which is the normal state on a fresh system, next to an "Install DRH" button.

Could a maintainer review it and merge? Thanks!

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

error-message-on-screen Test failed: the screenshot shows an error message

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants