Upgraded Roonserver from Debian Bookworm to Trixie, some caveats

Call me impatient but this is also my first time upgrading over releases a Debian system. I expected it to go smoothly, which is true 99% of the progress.
After the upgrade, I noticed that my Roonserver is no longer startable, examining the journal, turns out it was missing the ICU libraries

Jul 22 21:33:10 roonserver systemd[1]: Started roonserver.service - RoonServer.
Jul 22 21:33:10 roonserver start.sh[934]: Process terminated. Couldn't find a valid ICU package installed on the system. Please ins>
Jul 22 21:33:10 roonserver start.sh[934]:    at System.Environment.FailFast(System.String)
Jul 22 21:33:10 roonserver start.sh[934]:    at System.Globalization.GlobalizationMode+Settings..cctor()
Jul 22 21:33:10 roonserver start.sh[934]:    at System.Globalization.CultureData.CreateCultureWithInvariantData()
Jul 22 21:33:10 roonserver start.sh[934]:    at System.Globalization.CultureData.get_Invariant()
Jul 22 21:33:10 roonserver start.sh[934]:    at System.Globalization.CultureInfo..cctor()
Jul 22 21:33:10 roonserver start.sh[934]:    at System.Globalization.CultureInfo.get_CurrentUICulture()
Jul 22 21:33:10 roonserver start.sh[934]:    at System.TimeZoneInfo.GetUtcStandardDisplayName()
Jul 22 21:33:10 roonserver start.sh[934]:    at System.TimeZoneInfo.CreateUtcTimeZone()
Jul 22 21:33:10 roonserver start.sh[934]:    at System.TimeZoneInfo..cctor()
Jul 22 21:33:10 roonserver start.sh[934]:    at System.DateTime.get_Now()
Jul 22 21:33:10 roonserver start.sh[934]:    at Base.Utils..cctor()
Jul 22 21:33:10 roonserver start.sh[934]:    at Base.Utils.SetApplicationName(System.String, System.String)
Jul 22 21:33:10 roonserver start.sh[934]:    at Sooloos.App.Main(System.String[])

Reinstalling libicu-dev had it going again.

Not sure at which stage the libs got wiped out, but if you are in the same boat, just install the library and it should be good to go.

1 Like

Thanks. Hit this error testing the upgrade of a debian incus container in truenas scale.
No problems with my promox roon container (maybe depends on whether you upgrade or dist-upgrade).

The package you need is actually libicu76. Was libicu72 in bookworm, but it is not in trixie. In proxmox I still had the old libicu72.

I have had no issues with Bookworm when adding a network share from Roon client, but with Trixie I keep getting the Could not connect to share: Unauthorized message.

Anyone else having smb share probems?

Is that added via NFS as I remember someone on reddit mentioning changes to NFS that needs config changes.

Shares that worked before were added viasmb://host/share format.

Sorry, I don’t use samba, can’t really provide help.

Test to mount the share from the command line

mount -t cifs //<server>/<share> <mountpoint> -o username=<sambauser>

I set up a spare machine today using trixie and had the problem of being unable to connect to a network share for either storage or to restore my backup.

I had no problem connecting to the share from the command line but it failed 100% of the time in the roon ui.

I connected a monitor to the box and every time I tried to log in via the Roon ui, it would post a notice about cifs and not using v1.

I am guessing Roon is using SMB1 (bummer) and it’s disabled in trixie. I made some edits to the smb.conf but an not enough of a Linux guru to make it work.

I installed Debian bookworm (12) and it worked immediately.

1 Like

I doubt that as even Roon OS has supported SMBv2 for 7 years

From what I find on Google, samba packages have been reorganized in trixie, so probably ample opportunity for things to break

A little birdie told me they had to install icu-devtools but wasn’t as a result of a failed access to a smb share.

Whilst it might not directly stop SMB from working, but it could cause issues with internationalised file names or certain operations. However, this is less likely to be the root cause of connection problems.

If this doesn’t work, you can blame @Peter_Bruderer :smiling_face_with_sunglasses:

Thanks, good to know, appreciate the info.

I ran the dietpi trixie upgrade script again, but this time on my running roon server, meaning the network shares were already connected. Roon is unable to connect to the network shares (qnap) and the console displays almost continuous errors of the type I was getting when I tried a fresh config, likely because roon is retrying the network mounts, which I would totally expect.

I also installed icu-devtools as suggested, it made no impovement. For anyone interested, I took a pic of the console errors, note they don’t appear in a ssh session, only on the console of the host when not logged in.

Thanks, I will give it another try since it doesn’t take long to reinstall bookworm and restore my roon backup if things go south.

I could be wrong here. Has been known.

Trixie has blocked use of SMB1, ok, and Roon supports SMB2.

This would lead me to think your NAS is only supporting SMB1 :man_shrugging:

If the NAS does support SMB2 and is enabled, Try

mount -t cifs //gnas02.localdomain/<share> </mnt/point> -o vers=2.1,username=<your username>,password=<your password>

1 Like

I had connected before but [without] specifying the version. It this case, it has no issues, connects immediately without error. I appreciate the assist.

root@rcore:/mnt# mkdir roontest
root@rcore:/mnt# mount -t cifs //gnas02.localdomain/musicshare /mnt/roontest -o vers=2.1,username=xxxx,password=xxxx
root@rcore:/mnt# ls ./roontest
@Recently-Snapshot musicroot
root@rcore:/mnt#

1 Like

Ugh, meant to say “without” specifying the version.

1 Like

The problem is still present in Roon 2.57. I noticed the same thing when updating my DietPi-based Roon server from 9.19 Bookworm to 9.20 Trixie.

I’ve created the following support topic to report my findings to Roon …

[Moderator edit: comments and replies have been moved the recently created support topic.]

1 Like