Skip to content

Add YaMusic - #10316

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

probonopd wants to merge 1 commit into
masterfrom
discover/YaMusic

Conversation

@probonopd

Copy link
Copy Markdown
Member

Repository: https://github.com/andfriden/YaMusic

для поддержки работы

  • Stars: 5
  • Release with the AppImage: v0.14.2 (2026-10-16T11:34:09Z)
  • AppImage asset: YaMusic-0.14.2-linux-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-glibc-too-new Test failed: built on a too new system (needs a newer glibc) labels Oct 16, 2026
@github-actions

Copy link
Copy Markdown
Contributor

❌ Test failure

@andfriden: this pull request adds the AppImage from your GitHub repository to the AppImage catalog; the test reports the following. Could you have a look?

Tested:

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

Names:

WARNING: AppImage name 'YaMusic-0.14.2-linux-x86_64.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 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.
  • Please check the remarks about the names below.

First error in the log:

/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /run/firejail/appimage/AppRun)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /run/firejail/appimage/usr/bin/../lib/libtag.so.1)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libtag.so.1)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libxkbcommon.so.0)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libglib-2.0.so.0)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libgssapi_krb5.so.2)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libdbus-1.so.3)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libpulsecommon-16.1.so)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libkrb5.so.3)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libk5crypto.so.3)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libkrb5support.so.0)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libsystemd.so.0)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libsndfile.so.1)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libsndfile.so.1)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libapparmor.so.1)
/run/firejail/appimage/AppRun: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /run/firejail/appimage/usr/bin/../lib/libcap.so.2)

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 79161db. Full log

@andfriden

Copy link
Copy Markdown

Спасибо за проверку. Причина в окружении сборки: Linux-джоб собирался на ubuntu-24.04, поэтому бинарник и библиотеки, которые упаковывает linuxdeploy, ссылались на GLIBC_2.38 и GLIBCXX_3.4.32 — на самом старом поддерживаемом LTS таких символов нет, и загрузчик падал до создания окна. К коду приложения это отношения не имеет.

Что сделано в v0.14.3:

  • сборка AppImage перенесена на самый старый поддерживаемый LTS (ubuntu-22.04), чтобы glibc/libstdc++ внутри образа были не новее тестовой системы;
  • имя файла приведено к конвенции каталога: YaMusic-0.14.3-x86_64.AppImage (без linux);
  • в CI добавлена проверка запуска: AppImage стартует на старом LTS без сети, и сборка падает, если приложение завершается сразу после старта.

Функциональность не менялась, изменения только в упаковке. Релиз: https://github.com/andfriden/YaMusic/releases/tag/v0.14.3

Замечание про linux в имени было предупреждением — поправил заодно. Релиз публикуется как pre-release; если для каталога это нежелательно, скажите, поправлю.

@andfriden

Copy link
Copy Markdown

/retest

@probonopd probonopd closed this Oct 16, 2026
@probonopd probonopd reopened this Oct 16, 2026
@github-actions github-actions Bot added error-not-english Test failed: see the test result comment 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 16, 2026
@github-actions

Copy link
Copy Markdown
Contributor

❌ Test failure

YaMusic

YaMusic

Tested:

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

  • The text on the screenshot is mostly not in English. AppImageHub is in English: please make the application start in English when the system language is English or not set (the test runs it with the C locale), e.g. by falling back to English instead of to another language.

First error in the log:

ERROR: The screenshot shows text mostly not in English but in Cyrillic or Greek script

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 79161db. Full log

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 error-not-english Test failed: see the test result comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants