[probonopd]

Repository: https://github.com/Chaos-Tic/Lorenz

Local file conversion at your cursor: drag a file, tap Shift, Ctrl or Alt, release on a choice. Windows and Linux.

• Stars: 5
• Release with the AppImage: v1.2.1 (2026-10-24T09:07:46Z)
• AppImage asset: Lorenz-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.

[github-actions]

✅ Test passed

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

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

Lorenz

Tested:

• Lorenz-x86_64.AppImage from release v1.2.1

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

Warnings:

• The application showed no window but an icon in the system tray, so it was tested as a system tray application: the screenshot shows what clicking its icon opened (its window, or its menu with the icon). Please check that it shows the application working.
• 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 2e46faf. Full log

[Chaos-Tic]

Hi @probonopd ,

Thanks for discovering and adding Lorenz!

Lorenz is designed as a cursor and tray companion that pops up radial wheels on demand (rather than a traditional persistent window), which explains why the automated headless test only caught the basic tray menu.

Could we please use this screenshot for the catalog instead, which properly showcases the UI and main feature?

Thank you!

[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.

[Chaos-Tic]

/retest

[github-actions]

✅ Test passed

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

Lorenz

Tested:

• Lorenz-x86_64.AppImage from release v1.2.2

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

Warnings:

• The application showed no window but an icon in the system tray, so it was tested as a system tray application: the screenshot shows what clicking its icon opened (its window, or its menu with the icon). Please check that it shows the application working.

Commit 2e46faf. Full log

[Chaos-Tic]

/retest

[github-actions]

✅ Test passed

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

Lorenz

Tested:

• Lorenz-x86_64.AppImage from release v1.2.3

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

Warnings:

• The application showed no window but an icon in the system tray, so it was tested as a system tray application: the screenshot shows what clicking its icon opened (its window, or its menu with the icon). Please check that it shows the application working.

Commit 2e46faf. Full log

[Chaos-Tic]

Update: since v1.2.3 the AppImage ships AppStream metadata whose default screenshot is the wheels image above, and the test log shows the generated entry uses it. The tray-menu capture is only the launch check, so nothing needs changing on your side. Thanks!