Add DeezerDiscordRPC

[probonopd]

Repository: https://github.com/CuteTenshii/deezer-discord-rpc

A Discord RPC for Deezer

• Stars: 153
• Latest release: 1.3.9 (2026-05-11T09:15:14Z)
• AppImage asset: DeezerDiscordRPC-linux-x86_64.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.

[github-actions]

❌ Test failure

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

DeezerDiscordRPC

Compatibility: not self-contained: uses the C library of the system; uses an old AppImage runtime that needs the C library (and libfuse2) of the system; references glibc 2.25

Names:

WARNING: AppImage name 'DeezerDiscordRPC-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')

• Please check the remarks about the names below.
• The window is empty, e.g., only a menu bar on a blank background. The application must show its content when started without arguments and without network access.

First error in the log:

ERROR: The window appears to be empty (100% one color, almost no text)
Screenshot: letters by script: 0 Latin, 0 Chinese/Japanese/Korean, 0 Arabic, 0 Cyrillic/Greek

Commit 2153b46. Full log

[CuteTenshii]

"without Internet" well, this is a... Deezer client, so of course it requires Internet

Compatibility: not self-contained: uses the C library of the system; uses an old AppImage runtime that needs the C library (and libfuse2) of the system; references glibc 2.25

I made a new release https://github.com/CuteTenshii/deezer-discord-rpc/releases/tag/1.3.10 that may fix this

@probonopd

[github-actions]

❌ Test failure

DeezerDiscordRPC

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

Names:

WARNING: AppImage name 'DeezerDiscordRPC-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')

• Please check the remarks about the names below.
• The window is empty, e.g., only a menu bar on a blank background. The application must show its content when started without arguments and without network access.

First error in the log:

ERROR: The window appears to be empty (100% one color, almost no text)
Screenshot: letters by script: 0 Latin, 0 Chinese/Japanese/Korean, 0 Arabic, 0 Cyrillic/Greek
code/worker.sh: line 11: 14155 Killed                  firejail --quiet --noprofile --net=none --appimage ./"$FILENAME"

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 2153b46. Full log

[CuteTenshii]

/retest

[github-actions]

✅ Test passed

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

DeezerDiscordRPC

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

Names:

WARNING: AppImage name 'DeezerDiscordRPC-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')

Warnings:

• Please check the remarks about the names below.
• The screenshot may show an error message; please check it.
• 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 2153b46. Full log

[probonopd]

/AppStream

[github-actions]

How to add AppStream metadata (and your own screenshots)

The catalog page of an application can show a description, a summary, links and, above all, screenshots of your choice. They come from an AppStream metainfo file inside the AppImage.

1. Write the file. Save it as usr/share/metainfo/<id>.metainfo.xml inside the AppDir (the directory the AppImage is made from), where <id> is the <id> of the file, e.g. io.github.yourname.YourApp:

<?xml version="1.0" encoding="UTF-8"?>
<component type="desktop-application">
  <id>io.github.yourname.YourApp</id>
  <name>YourApp</name>
  <summary>One line saying what it does</summary>
  <metadata_license>CC0-1.0</metadata_license>
  <project_license>MIT</project_license>
  <description>
    <p>A few sentences about the application.</p>
  </description>
  <launchable type="desktop-id">yourapp.desktop</launchable>
  <url type="homepage">https://github.com/yourname/YourApp</url>
  <screenshots>
    <screenshot type="default">
      <caption>The main window</caption>
      <image>https://raw.githubusercontent.com/yourname/YourApp/main/screenshots/main.png</image>
    </screenshot>
  </screenshots>
  <releases>
    <release version="1.0.0" date="2024-01-31"/>
  </releases>
</component>

• <launchable> names the .desktop file of the AppImage.
• The screenshot is a web address (https://…) of a PNG image that stays there, e.g. a file in your repository. The file itself does not go into the AppImage.
• <project_license> is the license of the application, as an SPDX identifier.

2. Check it: appstreamcli validate --no-net usr/share/metainfo/<id>.metainfo.xml (from the appstream package of your distribution).

3. Put it into the AppImage.

• appimagetool, linuxdeploy, and other tools that build from an AppDir: copy the file to AppDir/usr/share/metainfo/ before building. appimagetool checks it while building.
• electron-builder: add it to the AppImage with extraFiles, e.g. in package.json: "linux": { "extraFiles": [ { "from": "build/<id>.metainfo.xml", "to": "usr/share/metainfo/<id>.metainfo.xml" } ] }.
• Other tools: see https://docs.appimage.org/packaging-guide/optional/appstream.html

4. Publish a new release with the new AppImage, then comment /retest on the pull request.

Note about screenshots: the automated test still runs the application and takes a screenshot of its own. The test needs it to check that the application starts and shows a window, so the test has to pass as before. But if the AppStream metadata names a screenshot, the catalog page shows that screenshot (the one marked type="default", else the first) instead of the automated one.