Forum Replies Created
-
Posts
-
Hi, this happens because NoMachine no longer has accessibility permissions. If you’ve updated from version 7 to version 8 of the NoMachine software, you will need re-enable permissions in the macOS security and privacy section.
Open macOS Settings -> Security & Privacy -> Privacy and add ‘nxnode’ to the list of applications allowed in the accessibility list. If nxnode is already listed, remove and re-add it.
Please submit the logs as requested.
How to gather debug logs for support requests
https://kb.nomachine.com/AR07K00677It would also be a good idea to update to the latest version of NoMachine if you are still on v7.
Edit: Topic about sound is solved. A new topic is required if another issue is found.
Hi,
we are aware of a similar issue and a possible workaround (which will be released in the next available maintenance) is to start the client with the following Terminal command:
DISPLAY=localhost:0.0 open -a NoMachineLet us know if this helps.
Hi,
it looks like
nexexec --authis timing out. Try extending the timeout in the following key available in the server.cfg file#
# Set for how long the server will wait for the authentication phase
# to be completed on the system. By default timeout is set to 30
# seconds. Increase this value when the authentication process on
# the system takes longer. This setting applies also to two-factor
# authentication.
#
#AuthorizationTimeout 30Could you please try reinstalling NoMachine again and then disabling egl with
sudo /usr/NX/bin/nxserver --eglcapture no.Does this help?
Hi, thanks for taking the time to report this. From the log it seems that you need to install gcc make and headers. Take a look at the article here about USB:
What to do if USB support is disabled on Linux with NoMachine 6 or later installed
https://kb.nomachine.com/AR12J00658First let’s rule out that it’s not being caused by a setting in NoMachine. Could you could try turning off screen blanking in the NoMachine server settings on the Macbook if it is enabled? Does that make the flickering stop in the NoMachine player window?
If that doesn’t help, then you should bear in mind that closing the lid on Macbooks switches the GPU off as a rule and AFAWK there isn’t a system configuration to keep the mac GPU on with the lid closed.
We are not aware of similar issues on Rocky Linux. Can you send us the logs of the affected machine? And the GDB stack of that process when CPU usage is high?
For the stack:
echo "y" | sudo gdb -p 'pidof nxnode.bin' -ex "thread apply all bt full" -ex "quit" &> gdb_nxnode.bin.logFor the NoMachine logs: https://kb.nomachine.com/DT07S00243
Submit everything to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
I think the next step will be to re-enable hardware decoding and see if the sluggishness comes back. If so, I’ll update with new CPU usage info
Ideally, we would need a screen of the Details tab of the Task Manager. If you reproduce it again, submit that.
Both Android and iOS have symbols which don’t exist in the corresponding X11 maps. That said, the next release will provide some improvements to how keyboard is handled when connecting from mobile devices. Keep your eyes open for that 🙂
Hi, thanks for reporting this. We’ve also reproduced it on Arch’s rolling release and will be opening a Trouble Report.
Hi, something similar to this has been dealt with before in the forums already. Please take a look at https://forums.nomachine.com/topic/enabling-a-user-does-not-enable-it. Does it help?
What NoMachine products do you have installed on both sides? Are they the latest versions?
Is it a physical desktop session with monitors attached? Or are you connecting to a headless? What’s the desktop environment running there?
You mention “first remote window” and “change focus to another window”. What are these windows? Application windows on the remote desktop? Steps and screenshots would be useful 🙂