Existing connection prevents screensaver on host

[nargolast]

Situation:
Host machine has screensaver configured to kick in on 3 minutes inactivity. NoMachine server is running as service. While no client is connected screensaver starts after 3 minutes of inactivity.

Expected behaviour:
While a client is connected the screensaver should become active after 3 minutes inactivity

Actual behaviour:
While client is connected the screensaver never becomes active.

Both host and client run:
Microsoft Windows 10 Pro, Version 10.0.19042 Build 19042
NoMachine 7.7.4

[fra81]

Hi,

the current behaviour is intentional. It is assumed that, as long as the remote connection is active, the remote user is watching it. Also, a black screen in the remote desktop may lead the remote user to believe there is a problem with the connection. However, we understand that this may not be the expected behaviour for some users, so we are going to add an option to choose a different behaviour. Therefore I opened the following Feature Request:

https://knowledgebase.nomachine.com/FR02T04241

[nargolast]

Hi,

Thank you, that does make sense.

But I hope that option comes soon 😉 as my remote has a monitor prone to burn-in and I use it as a side machine (always connected but not always in actual use).

Am I correct that this was new with 7.7.x? Because it did work my way before (sorry, I do not know from what exact version I updated to 7.7.4).

[fra81]

The current behaviour is in place since NoMachine version 7.0.

[nargolast]

Thanks!

I prefer not to go back to 6.x, so may I give a gentle push 😉 to have the aformentioned option implemented sooner than “Target: 8”, which I understand as version 8.x?

 

[Britgirl]

It’s target is the first release of v8, or if not the first, the next one 🙂

[Author]

Posts