Build 354 Roon no longer opening on macOS Mojave

I’ve been running Roon since a long time without issues but since I’ve updated to Mojave, Roon will crash while trying to open. I’ve installed the latest version Roon 1.5 (Build 354) also rebooted and even completely deinstalled Roon and fresh installed it on my iMac without any result. Roon keeps crashing all the time…

Process: Roon [2281]
Path: /Applications/Roon.app/Roon
Identifier: com.roon.Roon
Version: 1.0
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Roon [2281]
User ID: 501

Date/Time: 2018-09-26 07:50:20.237 +0200
OS Version: Mac OS X 10.14 (18A389)
Report Version: 12
Anonymous UUID: E4F3A9B3-9446-6D71-412A-7EAED75F383A

Time Awake Since Boot: 340 seconds

System Integrity Protection: enabled

Crashed Thread: 0 tid_307 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
Assertion failed: (_eventPort != NULL), function -[SPMediaKeyTap startWatchingMediaKeys], file SPMediaKeyTap.m, line 78.

https://community.roonlabs.com/t/is-roon-compatible-with-macos-10-14-mojave/49854/42

I have the same issue, @wizardofoz the latest version is supposed to have removed the need for the workaround.

So many thanks for the hint! Big kudos to “Wizardofoz (Mr Fix It)”!
Shame for Roon since they missed to mention anything in the changelog of their latest release!

This fixed my issue:

Head to System Preferences > Security & Privacy, Privacy Tab, then scroll to the Accessibility list. Here, click the plus button and add Roon.app to the allowed list. You may need to click the lock in the lower left corner to allow changes to this screen.

If you already see Roon in this list, highlight it and click the ‘-’ button to get rid of this existing entry. Then click the ‘+’ button and add Roon.app to the list again.

Sadly I can NOT confirm, that the latest release was able to fix my issue…
Only the workaround was able to fix the issue.

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