Logon screen disables mouse and keyboard input

[MK]

Hi,

I am able to use mouse and keyboard only if I login to a previously logged user session. If I log that user out or try to switch user input freezes. The same happens if I connect to freshly rebooted Mac with no users logged on.

Latest client and server version. Mac has latest Big Sur, client uses win 10 with all updates installed.

Very similar to https://forums.nomachine.com/topic/nomachine-cant-control-the-mouse-or-keyboard-when-remoting-in

and https://forums.nomachine.com/topic/after-connecting-to-mac-the-mouse-doesnt-work

I have reset Accessibility and Screen recording permissions in Mac OS Security Preferences.  Adding DisplayServerExtraOptions “-oldeventapi 1” to node.cfg only rendered the screen black, so I see nothing after the connection now. Disabling that option does nothing.

Any ideas?

[graywolf]

Would you try this:

1. Run a remote shell and connect to the macOS system

2. Use sudo to gain admin rights: sudo -i

3. Run these commands to unload NoMachine agents:

launchctl unload -wF /Library/LaunchDaemons/com.nomachine.server.plist

launchctl unload -wF -S LoginWindow /Library/LaunchAgents/com.nomachine.localnxserver.plist

4. Run these commands to reload:

launchctl load -wF /Library/LaunchDaemons/com.nomachine.server.plist

launchctl load -wF -S LoginWindow /Library/LaunchAgents/com.nomachine.localnxserver.plist

5. Restart nxserver:

/etc/NX/nxserver --restart

[MK]

On running last launchctl command I get the following error:

:~ root# launchctl load -wF -S LoginWindow /Library/LaunchAgents/com.nomachine.localnxserver.plist

/Library/LaunchAgents/com.nomachine.localnxserver.plist: service already loaded

Load failed: 37: Operation already in progress

Nothing changes.

[clatter-kilometer-womanly]

I am having the same problem and those commands do not fix the problem. Re-installation and re-enabling nxnode accessibility permissions won’t fix it either. Intel MacOS 11.6 NoMachine 7.6.2

[clatter-kilometer-womanly]

Here’s the Trouble Report with the workaround
https://knowledgebase.nomachine.com/TR08S10329

[graywolf]

Does the workaround in TR08S10329 fix the issue?

[MK]

Yes, thanks a lot, it fixes the issue in my case.

[mclaborn]

This worked for me also.

[graywolf]

Thanks for reporting. You can expect a stable fix in the next update.

[Author]

Posts