Library issue after updating Roon Server to 2.65 on Linux Mint 22.3 (ref#CAXNIW)

Support
1

Hi! What’s not quite right with Roon?

· Music won’t play or issues with my library

Music won’t play or issues with my library

· Trouble creating or restoring backups

Tell us what's going on

· After Roon Server Update from 2.64 to 2.65 I get the error "there was an issue with your library". Roon Server is installed on a Linux Mint 22.3 machine and I have tried to restore a few backups from 1-11 days ago (all generated with V2.64) but always with the same error.

Tell us about your home network

· Router icotera i6850 and two FRITZ!Box 4040 WLAN Routers (working as WLAN-access points and LAN-Switches)

2

Additional technical details:

  • Linux Mint 22.3 XFCE

  • glibc and OpenSSL meet current Roon 2.65 requirements (“getconf GNU_LIBC_VERSION
    openssl version
    glibc 2.39
    OpenSSL 3.0.13 30 Jan 2024 (Library: OpenSSL 3.0.13 30 Jan 2024))”

  • Roon Server 2.64 runs fully stable

  • Upgrade to 2.65 (Build 1653) installs successfully

  • Server starts normally

  • Logs show full library loading successfully (~52k tracks / ~4.3k albums)

  • Clients detect the server, but library access fails

  • Multiple valid 2.64 backups (1–11 days old) all trigger the same issue under 2.65

  • Full rollback to 2.64 immediately restores complete functionality

  • tested on Linux client and on Windows client => similar behavior

This strongly suggests the issue may be related to 2.65 library migration rather than backup corruption or unsupported Linux dependencies.

3

Hi @Stefanshine,

Thanks for the detailed notes. Can you please send us the RoonServer/Logs folder for review and let us know once uploaded?
https://workdrive.zohoexternal.com/collection/nocvrfc5b2ddab55140af8640f1d7ce13291e/external

4

“roon_logs_support_upload.tar.gz” uploaded successfully

5

Hi @Stefanshine,

Thanks for uploading those! Unforatunly, they didn’t capture any events surrounding the upgrade process and the database failures.

Could you please reproduce the issue in full, grab a fresh set of logs, and re-send them over?

Thank you!

6

“roon_logs_support_2026-05-09_12-40-44.tar.gz” uploaded successfully. => Forget this please, I’m uploading newer logs at the moment, takes about an hour till it’s finished.

7

Hi @Stefanshine,

We’re not seeing any server logs on our end. I’d be curious to see if updating to 2.66 would result in the same issues - is this something you’d be able to try?

We’ll be monitoring for your reply. Thank you! :folded_hands:

8

Hello Benjamin,

I’ve uploaded the following files again, this time without compression as seperate files:

grafik
grafik638×639 84 KB

9

And in the log files you can see that I have also tried V2.66 and it’s the same issue.

10

Hey @Stefanshine,

Thanks for this! We can see the exact crash this time around:

Critical: Library.EndMutation: System.NullReferenceException: Object reference not set to an instance of an object.
 at Sooloos.CompressedImageUri.ToString()
 at Sooloos.CompressedImageUri..ctor(String path)
 at Sooloos.Broker.Image..ctor(MPImage image, Image successor_to)
 at Sooloos.Broker.ImageCollection.TryGetBestImage(...)
 at Sooloos.Broker.Music.LibraryPerformer._Load(...)
 ...
 at Sooloos.Broker.Music.Library.EndMutation()
→ [loadstatus] IsLibraryLoadFailed False => True

We’ll bring this to our development team, but it may also be helpful to try to identify the problematic performer image.

The crash happens while loading a specific performer whose image has a null/broken URI. You could try:

# Look for any null or 0-byte image files in the Roon cache/database
find ~/.RoonServer -name "*.db" -o -name "*.jpg" -o -name "*.png" | xargs ls -la 2>/dev/null | grep " 0 "

If you find corrupted/zero-byte image files in the Roon image cache, clearing them (with 2.64 stopped) might let 2.65/2.66 proceed past the crash.

Another thought, If you want to try 2.65/2.66 again before a patch

  • Stop Roon
  • Clear the image cache: rm -rf ~/.RoonServer/Cache/
  • Start 2.66 and see if the library loads. The metadata service will re-fetch images, which may avoid the corrupted URI that's triggering the crash.
Back up first before trying this, even though your backups already work under 2.64.

Thank you, @Stefanshine! :+1: