Forum Replies Created
-
Posts
-
If I understand correctly, what you need to do is set the “lock the physical screen on disconnect”. This is useful in conjunction with screen-blanking.
When the screen blanking feature is activated, the remote screen is blanked, and the remote keyboard and mouse are locked whilst the user is connected by NoMachine. I.e. operations made on the physical screen by the NoMachine user are not shown and the local user cannot interact with the desktop until the NoMachine user logs-out.
As soon as the session is disconnected, the remote screen is unblanked, mouse and keyboard are released. To avoid this, it’s possible to activate the automatic lock of the screen, even if the user didn’t lock the screen before disconnecting by NoMachine.
See here more details:
https://www.nomachine.com/protecting-the-host-screen-during-a-remote-control-session
and
How to enable screen blanking and the automatic lock of the screen
https://kb.nomachine.com/AR07M00851Please follow the steps that Tor wrote here and report back.
Windows client freeze and cannot restart without reboot (continued)
At the moment it’s not possible, but in Network (see our introductory page here https://www.nomachine.com/network) there are going to be a big number of different “tricks” to always be able to connect, so router hole-punching and so on, and among them also these “inverse connections”, so that you can “switch direction”.
Please run in a terminal on the machine where you installed NoMachine Terminal Server:
sudo /etc/NX/nxserver --version sudo /etc/NX/nxnode --versionHi, thanks for reaching out to us š
The key to understanding your issue is the input peripherals connected to the Mac (by the way, nice workaround!). Since you don’t need to activate the Player window to work on Mac, NoMachine is not deactivating your energy saving parameters. Try this: when the NoMachine Player is in fullscreen and before using the Mac, click in the Player window to activate it (i.e to give it focus)
Can you try disabling hardware decoding on the Fedora side, please?
First exit the Player on the machine you are connecting from by right clicking on the !M icon in the sytem tray and clicking Exit Player.
Edit %USERPROFILE%\.nx\config\player.cfg and set:
<option key=āEnable hardware accelerated decodingā value=āfalseā />
Then create a new session and check if you still have the white screen.
If you do, set that key to:
<option key=āEnable hardware accelerated decodingā value=ādisabledā />
and create a new session.
The first setting disables the use of HW decoding but the codec library is still loaded, while the second settings
disables completely the HW decoding and cannot be set via UI.Let us know the result. If it works,Ā it would be useful to know some hardware details so we can investigate internally. Which is the client side computer model, the graphics adapter name and the driver version?
Hi, you submitted to Linux and I assume you are connecting to Linux, but can you confirm the following please:
– NoMachine version on player and server sides
– Linux distro and version
– Desktop environment on Linux
– what application are you using?Does this happen in all applications?
Hi, thanks for letting us know. The NoMachine version is now 8.8.1. If you re-encounter the problem, get in touch.
Hi, “virtual session active” you probably mean the physical desktop session given that your question is about screen blanking.
A user must be “sudo” in order to disconnect another user By disconnecting that user, the screen will unblank.
From a terminal, run
sudo nxserver --disconnect [sessionID/username/display]I’ve just edited my previous reply to show that you must exit the Player (!M icon in tray, right click, Quit Player), then make the changes suggested, then you can restart the session.
We’ll keep this topic open for a while. If you encounter the problem again, let us know.
This may have happened after a graphics driver update. We suggest to disable hardware decoding on the client. First exit the Player on the machine you are connecting from by right clicking on the !M icon in the sytem tray and clicking Exit Player.
Edit %USERPROFILE%\.nx\config\player.cfg and set:
<option key=”Enable hardware accelerated decoding” value=”false” />
Then create a new session and check if it helps.
If not, set that key to:
<option key=”Enable hardware accelerated decoding” value=”disabled” />
and create a new session.
The first setting disables the use of HW decoding but the codec library is still loaded, while the second settings
disables completely the HW decoding and cannot be set via UI.Let us know result of tests. If it works,Ā it would be useful to know some hardware details so we can investigate internally. Which is the client side computer model, the graphics adapter name and the driver version?
Hi, thanks for the logs, we’ll be checking soon.
In the meantime, could you disable Wayland and use Xorg instead? Does it make a difference?
Connection files are saved by default in the NoMachine folder under your Documents. You can just copy that folder (or a set of the files stored in it) to the same location on another host, and the client will load them.
Hi, this isĀ the expected behaviour. We will evaluate how to improve this behaviour, so that the status of numlock on server is not forcibly off. Just so we understand your use case correctly, are there two users involved in this scenario? One connecting and one already on the desktop locally?