Don’t know whether this is expected behaviour, but after rebooting with Build 253 installed, I first had to log in, then I got the eternal jellyfish for about 4 minutes before finally landing on a Deauthorize screen. Clicking the button finally got me into Roon (where I left it, so that was fine).
I have about 60,000 tracks in the library (local and Qobuz)
BTW: Yay! for UEFI support and the CD Ripper fix…
Edit: Second observation: the Metadata Improver was Paused, so I needed a second reboot (which took around 2 minutes 40 seconds this time.
One other thing that might be relevant - I have another Core (used as a test system) running on Windows 10 - the deauthorize screen showed both systems (even though the Windows 10 system was sleeping at the time)
I clicked “go back above”, which brought me to the login screen. I entered my credentials, the jellyfish appeared for longer than usual (probably not 4 minutes, but 1 or 2), then I landed back on the same “already signed in” screen. Tried “go back” again, rinse and repeat.
Haven’t done anything else yet, didn’t dare unauthorizing, should I?
By the way it would be really nice if all earlyaccess release announcement could be pinned, when I get home in the evening they often have already dropped far down. This one was particularly easy to miss because no software prompt
So, not that I want to subject myself to this exact set of issues, but just for clarity’s sake, how does one (a) know that there’s an update to Roon OS, and (b) install said RoonOS update? If I go to the web admin interface for my ROCK, I’m on 1.0 build 227 and there’s nothing in the buttons that suggest there’s anything I could do.
Version 1.0 (build 227) stable
Running 203 days, 20 hours, 31 minutes, 16 seconds.