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

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)

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.

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

“roon_logs_support_upload.tar.gz” uploaded successfully

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!

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

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:

Hello Benjamin,

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

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

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:

My steps to update roon are:

  • Update Roon via the Roon Client GUI and confirm update message
  • Let Roon restart with the new installed V2.66
  • Get the “library Problem” message.

When should I do

this step when trying to update roon next time?

As far as I can see If rebuilding from my old library fails then

cannot solve the problem because the image cache isn’t built completely.

Or am I wrong with this?

Hi Benjamin,

I did some more testing (with help from chatgpt) and we now have a much clearer reproduction of the issue:

What I tested:

  • Reverted back to 2.64 (working normally)

  • Stopped RoonServer

  • Fully backed up /root/.RoonServer and /opt/RoonServer

  • Removed the entire cache by renaming:
    /root/.RoonServer/Cache

  • Restarted 2.64 and allowed it to completely rebuild metadata/image caches

  • Waited until the metadata queue finished processing (q size eventually reached 0)

  • No crashes under 2.64 during this rebuild process

After that, I updated again to 2.66.

Result:
The server itself stays running, but the library fails to load and the UI shows:

“There was an issue loading your library”

Most importantly, the logs now consistently show this:

Warn: CompressedPath exception: System.FormatException:
The input is not a valid hex string as its length is not a multiple of 2.

at System.Convert.FromHexString(ReadOnlySpan`1 chars)
at Sooloos.CompressedImageUri..ctor(String path)

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.LibraryAlbum._Load(...)
at Sooloos.Broker.Music.LibraryTrack._Load(...)
at Sooloos.Broker.Music.LibraryMutationEnv.Finish()
at Sooloos.Broker.Music.Library.EndMutation()

Info: [loadstatus] IsLibraryLoadFailed False => True

This appears reproducible even after a full cache rebuild.

The crash now seems specifically related to a malformed/corrupted CompressedImageUri associated with a performer image.

2.64 still loads the same library successfully.
2.66 consistently fails during Library.EndMutation().

Hopefully this helps narrow it down further.

I have also uploaded the last RoonServer_log.txt a few minutes ago.

If needed, I would also be available for a supervised remote debugging session on the affected Linux Mint server, since the issue appears to be reproducible.

I also archived the entire Database and Logs directories from the failed 2.66 state and can provide them if needed.

Hey @Stefanshine,

You have my utmost apologies for the long delay in getting back to you. It looks like your thread was auto-closed because we were slow in responding.

Thank you @Carl for re-opening it and pinging me. I’m sorry this slipped through the cracks Stefan!

At the moment, our development team is aware of this issue, and has a ticket in for further analysis. They haven’t shared any additional information outside of this, but work is being done behind the scenes to better understand what might be causing it.

We’ll be sure to keep you better informed as things progress, you have our apologies again for not responding sooner. :folded_hands:

Hello Benjamin,

thanks for your reply, am I the only one with this specific issue? Can you reproduce the errror?