September 14, 2021 at 16:43 #35257Alex09stParticipant
Hi, Thank you for this feedback which worked for one user running Mac OS 10.14 (For sure that was a 10.xx not sure about the 14); For this user, as soon as sharing the device was selected in NoMachine, the security app of MacOS poped up and we were able to accept the use of the extension 192.168.100.1.September 15, 2021 at 02:06 #35275
No problem, happy to help – I would certainly be willing to install the debug package to collect more info.
Just let me know what I need to do.September 15, 2021 at 17:47 #35299
Check your inbox Nyquist 😉November 9, 2021 at 11:22 #36169
Nyquist, did you manage to install the debug package we provided?November 19, 2021 at 08:15 #36325
Apologies for the delayed response – have had some server moves happening in a data centre and it’s been madness.
I did get the debug package thank you and downloaded as soon as I received your email.. Finally today I got around to the install!
All the terminal stuff executes as expected and it says the procedure to collect logs finished successfully but there is no log archive in that output folder on my MacBook.
I thought it might have something to do with permissions on the directory and messed around with that but to no avail. So then tried uninstalling the application and reinstalling using the debug package but despite saying it completes there is nothing in that log archive directory.
I will play around a bit more and see if I can figure out what’s not happening.November 19, 2021 at 19:22 #36349
Thanks for letting us know.
When you have time, you could collect the logs manually. See here for more info:
Any questions, we’re here 🙂November 27, 2021 at 04:25 #36458
Thanks for that.. I ran the command to enable logs but then double checked based on the info in that latest knowledge base you sent the link too.. That appears to work as expected as those debug flags mentioned were un-commented in the .cfg files just as outlined in the manual procedure.
So then I connected and went through some normal processes re-producing what I see.. Then archived the log directory manually.
I have sent this attached to email with some additional details of the exact process I went through – sent reply to your original email with the links for the debug package.
Let me know if you have any problems receiving this.November 29, 2021 at 10:40 #36471
We got your logs and extra info. Thank you!November 29, 2021 at 13:43 #36473
Can you send us the $HOME/.nx directory from the server side? They are missing from the logs that you sent.November 30, 2021 at 06:20 #36477
This has been sent – attachment was bit over 2MB, let me know is there are any problems receiving.January 4, 2022 at 11:57 #36914
Hi, based on the logs, we need to narrow debug down further. Can you check your email inbox? We would need you to try a second debug package and resubmit logs.January 7, 2022 at 04:40 #36956
No problem – have sent this off now in archive split across a few emails – details in the first email.
Hope that all makes sense! And is helpful.. 🙂January 31, 2022 at 14:30 #37253
The logs show that this is not a NoMachine problem. In your case of the big cursor, NoMachine shows it because this is the info that is received from the OS.February 1, 2022 at 11:09 #37261
Ok, interesting outcome, and coincidental timing..
I had not noticed this previously or using any other software, but over the last few days I have been running a test network environment using VMware Fusion, sometimes very erratically when the cursor is within the virtual machine screen space it flickers between a normal and huge cursor for a few seconds (it’s using VMware Tools so the cursor transition from host to guest screens is fluid/automatic).
It looked very familiar to what I see with the NoMachine + OBS Studio combination (though I have never seen that flicker).
OBS Studio is running in the background when this happens – I have yet to test whether the VMware Fusion “cursor flicker” goes away without it running, it happens very rarely and erratically so it’s a hard one to test.
I have put off upgrading OS X but this is inevitable at some point in the near future, will be interesting to see if the issue persists or changes after that. If I get any further useful information I will share with the community on here.
Hopefully this thread may be useful as it stands if anyone else experiences this behaviour.
This topic was marked as solved, you can't post.