I’m sitting in the same boat.
For a while I tried other Music-SW but renewed my License this morning and made a new installation.
I can remember that I had similar problems the last time I used Roon but “somehow” it worked.
However, these are my observations.
First of all I’m running OMV alongside with docker (docker-compose).
I’v a running Emby installation in “host mode”. I recreated my “Roon” Container with the same config I had before (also “host mode”) and couldn’t even connect to it with my android device because the server didn’t start.
What I saw was the following message in the Log:
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
I also tried a “native” installation with the same error.
After longer searching I stumbled about this thread.
So, I stopped Emby and after a restart the Roon container (image: steefdebruijn)was up and running.
So it seems to be something network related.
Now I tried to put Emby “bridge mode” and couldn’t start it because I received a message that port 1900 (DLNA discovery) is in use.
Same problem here with Roon Core installed on bare-metal machine with Ubuntu 18.04 LTS. On a docker test environment, I was able to grep the ports used by Roon when you start it (no connection nor remote nor screen connected, just after starting the service). 1900 is definitely part of it.
I wanted to reach out and let you know that we released Roon 1.7 Build 571, which includes some improvements that we believe should help here. Please give the update a try and let us know if it helps!
Considering the large amount of time to fix, I had moved to another server. I just reinstalled on Arch and it appears emby and Roon are peacefully coexisting now. Will see how it goes after a few updates. Thanks for the heads up. Now I can shut off another VM.