Forum Replies Created
March 8, 2017 at 11:29 in reply to: "Lock physical screen" doesn’t blank physical display #14006
to investigate further we would need you to reproduce the problem, collect logs and send them to forum[at]nomachine[dot]com.
Instructions about debug and collecting logs you can find here: https://www.nomachine.com/DT07M00098.
could you clarify what you mean by:
“But after disconnect, monitor is always on (no power save mode and so no login locking)”
Do you mean that NoMachine disabled the power saving options that were already configured on the system?
Or do you mean that you would expect NoMachine to lock the screen at disconnect (so you’d have to unlock it by username and password), independently from the power saving options set in the system?February 7, 2017 at 17:27 in reply to: Caps lock key is locked/unlocked with extra key with latest release #13722
unfortunately we weren’t able to reproduce your problem in our labs. You might however try enabling the new events handling and check if the problem is still present. To do so edit your node.cfg and add this line:
DisplayServerExtraOptions “-oldeventapi 0”
then restart nxserver. Hope this helps.
The “command+period” combination is a system action on OSX used to cancel tasks, and it cannot be intercepted and passed on from the client side. There is thus nothing NoMachine can do about this.
A workaround for your problem could be assigning some other key to simulate the ‘period’ key, if you really need the exact “command+period” combination to work in IntelliJ. You can do this using ‘xmodmap’ command (I assume you are using linux). Hope this helps.
There is unfortunately nothing we can do about your problem. NoMachine only allows setting resolutions supported by the graphic adapter. In other words, if a resolution is not listed in the Windows display settings menu, it will not be available for NoMachine either.
Let us know if there is anything else we can help you with.
Hi, sorry for the delay.
You mentioned you are using system images on different machines. We reproduced the issue in our labs and it seems to be caused by those system images. This is something that will affect blanking and unfortunately you will not be able to blank the server in that case. You would have to reinstall nomachine (assuming you have it installed on the system image that you use) on one side for it to start working properly.
Could you confirm that you are using !M free x64 version so that we can send you a possible fix for the blanking problem we have reproduced related to Leap42 and user switching?
Unfortunately the logs you have sent us indicate that you were connecting to local host (same machine used as server and client) and in that case blanking would not work by default. However we have found some problems with switching users on Leap42 that could affect blanking, although it is not related to desktop manager. We would like to ask you two things:
1. Could you please confirm that the logs you have sent us are from the reproduced issue?
2. Would you be willing to test a package with a possible fix?
we tried to reproduce your scenario in our labs, but with no luck. To investigate further we would need logs from server and client side. Please follow instructions about collecting logs from https://www.nomachine.com/DT04M00076. After editing server.cfg and node.cfg please restart nxserver on the server side, reproduce, gather logs and send them to forum[at]nomachine[dot]com.