Forum / NoMachine for Mac / Inputs stop working after rest after NoMachine update
- This topic has 7 replies, 3 voices, and was last updated 1 month, 4 weeks ago by Britgirl.
-
AuthorPosts
-
October 14, 2024 at 14:55 #50215daedalus1115Participant
Hello. I regularly connect to NoMachine from my Win11 desktop to my M1 Mac Mini and it’s been great until recently. After the most recent update to NoMachine on my Mac mini, however, I frequently have an issue where when I go back to NoMachine client on Windows, the connection is frozen. Mouse and input no longer work. I have to reconnect, which gets real annoying throughout the day. Sometimes the first reconnect results in a black screen. I reconnect again and it works. Any idea what is going on here? I did not have this issue until the most recent NoX update.
On the Mac it’s NoX 8.14.2.
October 14, 2024 at 17:15 #50224BritgirlKeymasterI assume you’ve got 8.14 on the Windows computer as well.
When you say “after rest” in the title, do you mean you start the session to the Mac and leave the session open/running, and then go back to it after some time?
October 14, 2024 at 20:35 #50226daedalus1115ParticipantYes. I usually alt-tab out of the client on my Windows box and use some other apps for a while. Or step away from the PC for a bit. I go back to resume my session, and my mouse and keyboard no longer work on the remote Mac. I can see the screen, but not do anything. I can move the mouse around, but it won’t click on anything. Same with keyboard, does nothing. I have to close the client and reconnect to get back to work.
October 16, 2024 at 16:46 #50265bucuParticipantCan you tell us if any of power saving options regarding display from Lock Screen tab in System Settings on your macOS are set? If yes can you please try running this command:
sudo mv /Applications/NoMachine.app/Contents/Frameworks/lib/libnxsck.dylib /Applications/NoMachine.app/Contents/Frameworks/lib/libnxsck.dylib-bak
and then restart nxserver with:sudo /etc/NX/nxserver --restart
and let us know if anything has changed?October 17, 2024 at 17:56 #50291daedalus1115ParticipantThank you for the suggestion. I did not run the command, but I did check the lock screen settings. There were 10 and 20 min time limits set under “Start Screen Saver When Inactive” and “Turn display off when inactive”. I turned these to “Never” and that seems to have fixed the issue.
Should these settings be interfering with the connection when enabled?
October 18, 2024 at 15:09 #50302bucuParticipantNo, they shouldn’t. We are aware of thisĀ problem and it will be fixed in next release.
October 20, 2024 at 17:02 #50313daedalus1115ParticipantHello, just to confirm: are these the expected MacOS settings for NoMachine to function properly? Thank you.
October 24, 2024 at 08:48 #50393BritgirlKeymasterHi, NoMachine is designed to work out of the box with all Mac configurations. It’s not necessary to configure the Mac in any particular way.
-
AuthorPosts
This topic was marked as solved, you can't post.