Hi @Kalgar1981 — that AppImage is a multi-call bundle: it ships every aMule tool (amule, amuled, amulecmd, amuleweb, amuleapi, …) in one file and picks which one to run from the name it's launched as (the same argv[0] trick GIMP and Krita use). Launched bare, it defaults to the monolithic GUI amule, which does require GTK+ and a display — exactly the error you hit on a headless box. amuled itself needs neither.

To run the daemon, invoke it under the amuled name via a symlink:

chmod +x aMule-3.0.1-Linux-arm64.AppImage

# daemon
ln -sf aMule-3.0.1-Linux-arm64.AppImage amuled
./amuled

# EC client, same trick
ln -sf aMule-3.0.1-Linux-arm64.AppImage amulecmd
./amulecmd

Renaming the file to amuled works too — the dispatcher strips the version/arch/.AppImage tail, so amuled, amuled.AppImage, and a symlink all resolve to the daemon.

If the AppImage won't even mount (headless images often ship without FUSE), install it with sudo apt install libfuse2, or run without it:

APPIMAGE_EXTRACT_AND_RUN=1 ./amuled

Let me know if amuled starts once it's invoked by name.

Uh oh!

Unable to start on headless Raspberry PI #498

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions