.NET 10 RoonBridge 2.71 (build 1683) on DietPi Endpoints (ref#EFOJUH)

[Neil_Small]

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

· Local files won't import or appear

Tell us what's going on

· The new Bridge won’t run on my DietPi Endpoints

Tell us about your home network

· Fiber to a NUC

[noris]

Hi @Neil_Small, thanks for reaching out to us on the forum

What OS version are you running, and are both of these DietPi installs?

QA is looking into this issue but any additional details you can share would be appreciated!

[Mikael_Ollars]

@Neil_Small

The new Bridge won’t run on my DietPi Endpoints

It seems there is a dependancy to libicu76, which is not present on all DietPi-installations.

apt install libicu76

The above solved my issues, and Roon Bridge showed up a few seconds after installation.

[mjw (You want nice, supportive? Call a damn helpline.)]

The dependency varies with OS version. On Trixie this is correct, but for Booworm libicu74 is fine, too.

I believe @Neil_Small resolved this via another thread and opted to upgrade to Trixie with libicu76.

[Wade_Oram]

For information I reported this issue in Feedback at:

RoonBridge 2.71 (build 1683) update fails on (some) DietPi Installations due to new libicu dependency

Edit: Changed dietpi version referenced. I have four Raspberry Pi 4bs running DietPi (10.6.2 Trixie) with all packages kept up to date. On three of these Raspberry Pis, the update to RoonBridge 2.71 proceeded without issue. However, on the 4th Raspberry Pi, post install the RoonBridge service failed to run. Looking at the logs, there was a dependency upon a missing library - libicu. Installing libicu using “apt install libicu76” allowed me to successfully start the Roon Bridge service on thi…

As can be seen from my own experience, not every Dietpi installation suffers the issue. Three of my four DietPi installations already had the required libicu76 (for Trixie or libicu74 on Bookworm) library present and encoutered no issues with the Roon Bridge 2.71 update but one did not.

The one Dietpi (Trixie) installation that did not have libicu installed was probably my most minimal one with an exceedingly small set of packages installed - dietpi-dashboard, Samba client, Samba Server, ALSA for USB audio and very little else. The other three installations were similar but not identical. In particular, different audio drivers were employed.

It would appear that DietPi, in its most minimal form does not install libicu. However, it also seems that in three of my installations another package was present with a dependency upon libicu that resulted in it being installed.

Edit and root cause (for me):

It turns out that I was wrong about the packages installed on the Dietpi system for which the Roon Bridge update failed. It did not have the Samba client or server installed whereas the other three did.

Looking further, it appears that, on my Dietpi Trixie systems, samba-libs have a dependency on libicu76

root@PiHeadphone:~# apt rdepends libicu76 | grep samba

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Depends: samba-libs (>= 76.1-1~)
Depends: samba-libs (>= 76.1-1~)
Depends: samba-libs (>= 76.1-1~)
root@PiHeadphone:~#

Thus, for me, the issue was that my Dietpi installation did not include the Samba client or server packages. Installing the Samba client or server would have installed libicu76 as it obviously did on my other three DietPi installations.