Oxygeneralist

[Oxygeneralist]

Sorry, I currently don’t have access to the Windows installation because my iMac is awaiting me to do a big repair job on it. I’ll contact you when it’s back up and running with Windows 10 installed, but that will be under Boot Camp at that point with the latest version of Windows 10 instead of 1909. I also don’t know when I’m going to get around to the repair or whether I’ll be successful with it.

[Oxygeneralist]

Can now confirm that the issue persists with Sticky Keys disabled.

[Oxygeneralist]

Hi Tor, thanks for your reply.

Sticky Keys is disabled on my Windows machine, but the ‘press shift 5 times’ setting to toggle it on/off was enabled. I’ve now disabled that as well. I doubt that Sticky Keys has been switched on recently due to accidental keypresses and I would never normally use it. But, just in case I accidentally toggled it and then untoggled it, I’ll keep an eye on it for a while and keep you updated.

[Oxygeneralist]

Just to update this with one method for a workaround, I’ve discovered that if I disconnect, and then restart the NoMachine server on macOS the screen will return to its former (i.e. correct) resolution. However, unless it can be automated on disconnection, it’s no better than going into System Preferences to reset the resolution.

[Oxygeneralist]

Thank you fra81,

Adding the above key to the node.cfg file and restarting NoMachine seems to have fixed this issue for me. I have only tested very briefly though, so I’ll report back if the issue recurs.

[Oxygeneralist]

Hi fra81,

First let me make a slight correction to my OP: I use the software in Resize Remote Display mode in conjunction with Full Screen.

Very brief testing shows the problem occurs in Full screen and Windowed modes, using either Scale to Window and Resize Remote Display. It does not occur in Viewport mode.

I will add the key to the file you suggested and update this post or make a new one to let you know if it worked.

[Oxygeneralist]

Thanks Britgirl, that’s helpful to know. I’ll work around it by streaming from my iDevices instead of my Mac.

[Oxygeneralist]

Yes, but this error only occurs when connected using NoMachine. I can play the same music to my HomePod Mini, without any errors, if I am not connected with NoMachine.

[Oxygeneralist]

Same issue here, except the problem first started happening after updating to NoMachine 6.13.1 on macOS and 6.12.3 on Windows. It hasn’t gone away after updating to 7.0.211 on both OS, though mouse pointer dragging did work correctly for a minute or two after updating.

I’m running macOS 11.1 and Windows 10 Education Version 1909, OS Build 18363.1316

[Author]

Posts