Linux ARM build?

[FrenchGithubUser]

Hey, this software seems great! But I'm running linux on ARM (asahi linux), would it be possible to provide builds for it?

[BLCK-B]

Hey. I have just tried Linux ARM runner and it passed build. AppImage for ARM will be added 🙂.
I plan to release a new version very soon.

[FrenchGithubUser]

wow that was quick, thanks!

[BLCK-B]

It's available now. Lets hope it works, since I have no way to test it.

[FrenchGithubUser]

Here are the execution logs, but no GUI shows up:

./MRT-13.0.0-linux-arm64.AppImage 
2026-05-10T07:35:54.167Z - Electron log: Contents at Level 0: /tmp/.mount_MRT-13pLXMvl/resources - app.asar

2026-05-10T07:35:54.174Z - Electron log: Contents at Level 1: /tmp/.mount_MRT-13pLXMvl - .DirIcon,AppRun,LICENSE.electron.txt,LICENSES.chromium.html,buildResources,chrome-sandbox,chrome_100_percent.pak,chrome_200_percent.pak,chrome_crashpad_handler,icudtl.dat,libEGL.so,libGLESv2.so,libffmpeg.so,libvk_swiftshader.so,libvulkan.so.1,locales,mrt,mrt.desktop,mrt.png,resources,resources.pak,snapshot_blob.bin,usr,v8_context_snapshot.bin,vk_swiftshader_icd.json

2026-05-10T07:35:54.174Z - Electron log: buildResources is present

[5114:0510/093554.262352:ERROR:dbus/object_proxy.cc:573] Failed to call method: org.freedesktop.systemd1.Manager.StartTransientUnit: object_path= /org/freedesktop/systemd1: org.freedesktop.systemd1.UnitExists: Unit app-org.chromium.Chromium-5114.scope was already loaded or has a fragment file.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.
Waiting for backend ready.

[BLCK-B]

You could try extracting the AppImage and running backend manually: chmod +x buildResources/MusicReleaseTracker ./buildResources/MusicReleaseTracker.

If any errors are logged at all, they can be found in user.home/MusicReleaseTracker/errorlogs.txt

[FrenchGithubUser]

I did this and it worked fine, I could access the web UI in a web browser, no apparent errors

[BLCK-B]

If you can run the backend again manually, and then (at the same time) start the AppImage successfully, then it may point to a simple timeout issue.