Navidrome Daily: Artwork Failures, Sandbox Fix, and Release Repair

Navidrome fixed a cluster of quiet failures — Last.fm bot blocking that silently marked artists as imageless, artwork saved without group access, and ffprobe killed by the systemd sandbox. A pipeline fix also explains why version 0.64.1 shipped with only three architectures.

Duration: PT2M19S

Episode overview

This episode is a short developer briefing from Navidrome Daily.

It explains recent repository work in plain language.

  • Show: Navidrome Daily
  • Published: 2026-09-22T10:01:36Z
  • Audio duration: PT2M19S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good morning, it's Tuesday, September 22nd, 2026.

The throughline today is quiet failures being made visible — artwork marked missing when it wasn't, scans breaking under systemd, and a release going out incomplete.

First, artwork reliability. PR 6198 addresses Last.fm artist images. Last.fm now serves non-browser clients a Fastly bot challenge as a normal 200 response with valid HTML. The scraper found no O-G image tag, returned an empty list with no error, and the artwork worker treated that as definitive proof the artist has…

Related, PR 6189 fixes stored artwork permissions. Temporary file creation defaults to owner-only access, and the atomic rename carried that through, leaving final images unreadable to the group. Completed files are now set group-readable before the rename, which matters for shared-host and multi-user deployments.

Second, deployment and release integrity. PR 6190 adds the M-bind system call to the systemd sandbox allow list. On setups like Debian 13, the media probe tool can pull in a math library that needs that call. It was previously blocked, crashing the probe with a bad system call and leaving clients reporting no…

And commit 9e3deb4 scopes digest…

Nearby episodes from Navidrome Daily

  1. Security Hardening Across Libraries, Players and Artwork
  2. Weekly Recap - Jellyfin Compatibility and Security Hardening
  3. Jellyfin Onboarding Push and Portable Smart Playlists
  4. Jellyfin Catches Up, Last.fm Links Get Fixed
  5. Protocol Compatibility Cleanup
  6. Jellyfin Compatibility Gets Serious
  7. Compatibility and Architecture Cleanup
  8. Closing the 404 Gap