[probonopd]

Repository: https://github.com/agentjp/bdinfo-rs

Memory-safe, zero-C-dependency Rust Blu-ray disc analyzer — a drop-in BDInfo report tool for BDMV folders and .iso images.

• Stars: 34
• Release with the AppImage: gui-v4.0.0 (2026-08-16T22:46:03Z); newest release: v4.0.0
• AppImage asset: bdinfo-rs-gui-x86_64-unknown-linux-gnu.AppImage
• License: LGPL-2.1

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.

[github-actions]

❌ Test failure

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

Names:

WARNING: AppImage name 'bdinfo-rs-gui-x86_64-unknown-linux-gnu.AppImage': should not contain 'Linux', since all AppImages are for Linux (e.g. 'App-1.0-x86_64.AppImage', not 'App-1.0-linux-x86_64.AppImage')

• The application quit or crashed right after starting. The error below usually shows why.
• Please check the remarks about the names below.

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

[agentjp]

Thanks for the discovery entry. The failure is on my side: the AppImage does not bundle libxkbcommon-x11, which winit loads at startup, so the app panics when the library is absent. The next GUI release will bundle it, and I'll comment /retest once it is published. thanks!

[agentjp]

/retest

[github-actions]

✅ Test passed

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

bdinfo-rs

Tested:

• bdinfo-rs-gui-x86_64-unknown-linux-gnu.AppImage from release gui-v5.0.0

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

Names:

WARNING: AppImage name 'bdinfo-rs-gui-x86_64-unknown-linux-gnu.AppImage': should not contain 'Linux', since all AppImages are for Linux (e.g. 'App-1.0-x86_64.AppImage', not 'App-1.0-linux-x86_64.AppImage')

Notes:

• File name 'bdinfo-rs': all-lowercase names are typically used for command line tools, but the desktop file does not set Terminal=true. If this is a graphical application, please name the file after the application as it is spelled, with capitals where it has them (e.g. 'Krita'); if it is a command line tool, set Terminal=true in its desktop file.

Warnings:

• Please check the remarks about the names below.
• 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 b4bc649. Full log

[agentjp]

The screenshot shows the application's main window.
The remaining remarks are fixed in the repository and take effect with the next release:

• The AppImage is named bdinfo-rs-gui-x86_64.AppImage, without "linux".
• It embeds update information, with the .zsync files published alongside.

On the name note: this is a graphical application whose desktop file names it "bdinfo-rs GUI"; the project name is written in lowercase. If the entry should follow the application's name, bdinfo-rs_GUI would match it. Either is fine with me. I say it because I also publish a CLI that is named only bdinfo-rs, so I want to avoid any confusion for the AppImage catalog.

I'll comment /retest after the next release.