Roon stuck on launch screen with spinning wheel on MacStudio (ref#LABUWF)

What’s happening?

· My Roon software won't start up

Describe the issue

I'm using Roon on my MacStudio (Sequoia 15.1.1), but tonight - for no apparent reason - when I launch it the black start window remains with the Roon logo and after a few seconds the spinning wheel appears and I have to exit the software by forcing it to quit. I've already tried restarting my Mac, but the problem persists... any help?

Describe your network setup

I have a working modem connected to Internet, no connection problems

A little update, I tried the following:

  • Navigate to my Roon Database Location
  • Find the folder that says “Roon Server” and “Roon”
  • Rename the “RoonServer” folder to “RoonServer_old” and “Roon” to “Roon_old”
  • Reinstall the Roon App from our Downloads Page to generate a new Roon folder

Again, the problem is launching the application, also starting as the first time (showing the startup screen with the button “Get started”) it freeze after two second with the spinning wheel.

Tried again restoring my original folders “Roon” and “Roon Server” but no difference.

Note: my database is on the startup disk of my MacStudio, all the folders are accessible.

Past week I’ve updated to Sequoia Os 15.1, but Roon worked without any problems. The only thing that happened was that yesterday I installed the Sequoia update to 15.1.1.

Hey @Marco_Maroccolo,

Thanks for writing in, and great troubleshooting work so far!

With the recent Sequoia updates, there’ve been reports of handshake issues between Roon and the new macOS.

As a next step, can you please navigate to macOS System Settings > Privacy & Security > Local Network , and make sure Roon is allowed. If it is already enabled, toggle it off and on again. Then reboot your Mac, and see if the same issue persists.

If that doesn’t help, it may be worth revisiting your Mac firewall settings, and ensuring Roon has proper access. You can learn more about that here :

It can sometimes be an easy test to temporarily disable your Mac firewall to see if your issues still persist.

We’ll be on standby for your reply! :raised_hands:

Thank you Benjamin for your help,
I’ve tried to disable and re-enable Roon and Roon Server on Local Network of Mac OS, after the reboot nothing change. Also: I’m not using a Firewall at all (in my system preferences is disabled).
I already noted - but not reported in my previous messages - that the Roon app in top bar of the finder is constantly trying to connect to the server and change status from “Roon Server Status: Started / Not Responding / Error”.

Exact same here

Any news on your side? Now when I launch Roon app I got a “Roon quit unexpectedly” error (here the log). The app in top bar is always giving me the “Roon Server Status: Started / Not Responding / Error”.

Hi @Marco_Maroccolo,
I think the next step here is to look at your Roon Server logs. You can either turn on your Roon server for a few minutes or use the directions found here and send over a set of logs to our File Uploader.

I also wanted to note that Tech Support will be off on November 28th and 29th. We will be back on Monday, December 2.

Hi Daniel. I’ve submitted the Logs folder using your File Uploader.

Hi @Marco_Maroccolo,
Thanks for sending the logs to us. Unfortunately they didn’t have the information we need. Can you please send us the RoonGoer logs? After that try a fresh database and see if your issues persist:

  • Create a Backup of your current database
  • Exit out of Roon + RoonServer (from taskbar area)
  • Navigate to your Roon Database Location
  • Find the folder that says “Roon Server” and “Roon”
  • Rename the “RoonServer” folder to “RoonServer_old” and “Roon” to “Roon_old”
  • Reinstall the Roon App from our Downloads Page to generate a new Roon folder
  • Verify if the issue persists on a fresh database before restoring the backup

Here is the process outlined from a macOS machine:
roonoldmac

Daniel,
I sent you the folder with RoonGoer Logs via Uploader.
I then followed your instructions. After reinstalling Roon, if I launch it, this window appears:

…but after a few seconds the spinning wheel appears and the application remains blocked. Forcing me to force it out.

  • Marco.

Hi @Marco_Maroccolo ,

Thanks for the update. Do you get any Apple crash reports when this issue happens? Do you happen to have any data in the Roon/Logs folder? If you can send any MacOS crash reports and the Roon/Logs folder to the uploader, they may be useful to debug this issue.

Thank you for your assistance. I already sent the logs via Uploader a few days ago, but I also uploaded them today (Roon Logs and Roon Server Logs).
Anyway, I have solved the problem.
I performed general maintenance on my MacStudio using OnyX app. After doing this and launching Roon, the program did not freeze and allowed me to configure it. When finished, I exited Roon and replaced the ‘Roon’ and ‘Roon Server’ folders - the new ones it created - with the old ones that I had renamed ‘Roon_OLD’ and ‘Roon Server_OLD’. At this point, I relaunched Roon, and it saw my library again. At the moment, it all seems to be working as before. One I think, important note: I have tried many times in recent days to follow the operation of deleting the Roon and Roon Server folders and reinstalling the Roon app, but nothing seemed to work: every time the Roon Server app started, it gave the error I wrote in the previous messages, and the Roon app as soon as it started would freeze. I usually keep my MacStudio’s operating system pretty tidy, so I exclude a priori that I have done anything that could affect the functioning of Roon.
The problem is Apple’s system updates: although I wait months before upgrading to a new version, they always seem to be a leap in the dark. Using OnyX was new to me, but I didn’t know what to do anymore, and it seemed to me that having to install an operating system from scratch on a MacStudio to make Roon work was a bit too much. So, I have no idea what OnyX did, but it worked. So, for now, I think I’ve solved it.

2 Likes

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.