Alright, I put some work on this today and have managed to work around this issue by creating a docker container to run Roon.
Dockerfile:
FROM ubuntu:latest
RUN apt-get update \
&& apt-get upgrade -y \
&& apt-get install -y curl bzip2 ffmpeg cifs-utils libasound2 \
&& apt-get clean \
&& apt-get autoclean
ENV ROON_INSTALLER roonserver-installer-linuxx64.sh
ENV ROON_INSTALLER_URL https://download.roonlabs.com/builds/${ROON_INSTALLER}
RUN curl ${ROON_INSTALLER_URL} -o /tmp/${ROON_INSTALLER}
RUN chmod 700 /tmp/${ROON_INSTALLER}
ENV ROON_DATAROOT /var/lib/roon-server
ENV ROON_ID_DIR /var/lib/roon-server
RUN yes | /tmp/${ROON_INSTALLER}
VOLUME [ "/var/lib/roon-server", "/srv/music", "/srv/roon" ]
ENTRYPOINT /opt/RoonServer/start.sh
run.sh:
#!/usr/bin/env bash
set -o xtrace
set -o errexit
docker build -t roon .
docker run \
--name roon \
--net host \
-d \
--device /dev/snd \
-v /var/lib/roon-server:/var/lib/roon-server \
-v /srv/music:/srv/music \
-v /srv/roon:/srv/roon \
roon
You may need to change the paths a bit to match what you had in your system. Make sure to use the overlay2 storage driver for Docker.
Hopefully this restores systems until they come up with an actual fix.
Listening to my local music again right now and didnāt lose my database or any data 