- This topic has 3 replies, 3 voices, and was last updated 3 months, 1 week ago by
.
-
Posts
-
I am having a similar problem to the one described here. I installed v9 on a Mac Mini M2 Pro running Sequoia 15.5. I got the background items dialog
, and the login items were installed 
. However, when I launched the program, I didn’t get the “nxnode/nxexec would like to control…” dialogs I usually see on first start. The NoMachine window did not appear, and after a short while the application stopped responding 
. I was able to select the “File..Open” dialog box, but nothing else.I restarted, uninstalled and tried installing v8.16.1 (which I had successfully installed on other machines). Same issue. Under activity monitor there were two NoMachine processes and one “NoMachine Monitor” process. I have attached samples of each. After taking samples, I restarted, noticed that NoMachine wasn’t starting at login. So I added that in System Settings, as well as adding NoMachine manually to Accessibility and Full Disk Access. I also moved my .nx directory and restarted. No effect.
Please advise.
Hello and thank you for the detailed info. It seems there is a problem to access the fonts database to initialize the application.
You can try to validate all fonts in order to exclude that any of them is corrupted. You should open Font Book application, select an item in the fonts list, press Command + A to select them all, then use the File > Validate selection menu. Let me know if you’ve one or more troublesome fonts.
If this doesn’t help, could you kindly try to create a new user on your macOS, and check if with that user the NoMachine client opens correctly? With a new user the fonts cache would be empty, so we would confirm if there is a problem with the cache before cleaning it up.
Thank you for your help.FontBook found a serious error with a system font, so I couldn’t repair it. I then cleared the cache using
sudo atsutil databases -removeThis also threw errors, but upon computer restart NoMachine launched. I am now having issues with port forwarding and display issues, but will post those as separate topics.
This topic was marked as solved, you can't post.