bucu

[bucu]

Hi,

can you please tell us your OSX and NoMachine versions? Is the problem present also when NoMachine is not used?

As a possible workaround you can try to edit /Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg on server side and add this line:

DisplayServerExtraOptions  "-oldeventapi 1"

If the problem is still present we would need logs from the OSX side. To gather logs please follow these instructions: https://www.nomachine.com/DT07M00098 (if you are using v. 5) or https://www.nomachine.com/DT10O00163 (for v. 6)
You can send your logs to forum[at]nomachine[dot]com.

[bucu]

Hi,

we are actively working on Wayland support with the highest priority. Here is the relevant feature request: https://www.nomachine.com/FR10N03221.

As a workaround, you can disable Wayland as specified in that link.

[bucu]

Hi,
can you confirm that you are trying to run a custom session? If so, could you provide the command you are using to run the application as well as logs from both server and client sides? To gather logs please follow the following instructions: https://www.nomachine.com/DT07M00098

[bucu]

Hi,

by “screen lock not working” you mean that enabling an option in server preferences does not blank the screen when connected? Is the input (mouse and keyboard) locked then anyway?

If this is the case, we would need server side logs to investigate further. You can find instructions about debug and collecting logs here: https://www.nomachine.com/DT07M00098.

[bucu]

Hi,

the problem you described looks a lot like a situation when you have “grab mouse pointer” selected in the player settings. The big cursor may be caused by the difference between resolution and DPI of the server side and the client one. In order to investigate furter we would need some more info:

• What is the OSX version you are using on the server side?
• Is the server side by any chance a headless machine?
• What is the OS you use as client side?
• What are the resolutions and DPI used on both server and client side?
• Does disabling “grab mouse pointer” make the smaller cursor disappear?

[bucu]

Hi,

The problem you describe is likely to be a known issue involving the screen brightness setting. Could you check if the ‘Automatically adjust brightness’ option is enabled? If yes, please disable it and try to lock the screen again.

All know issues regarding screen blanking can be found here: https://www.nomachine.com/AR01O00915.

[bucu]

Can you confirm that you are using the newest (5.2.21) version on both sides? If no, please ugrade and then try to reproduce the problem.
If that won’t help, you can try and select the specific display you want to resize. You can do it with the “Change monitor” button in the Display menu, or with the keystroke Ctrl+Alt+<monitor id>.
If none of the above helps are you willing to use a debug package, so that we can gather more logs?

[bucu]

Hello,

to investigate further we would need you to reproduce the problem, collect logs from both sides and send them to forum[at]nomachine[dot]com.

You can find instructions about debug and collecting logs here: https://www.nomachine.com/DT07M00098

• This reply was modified 3 years, 10 months ago by bucu.

[bucu]

Hi,

to investigate further we would need you to reproduce the problem, collect logs and send them to forum[at]nomachine[dot]com.

You can find instructions about debug and collecting logs here: https://www.nomachine.com/DT07M00098

[bucu]

Hello,
it looks like you are connecting to Fedora with an old version of NoMachine (5.0.53). Could you try to upgrade  to the current version (5.2.11) and see if the result is different? If this is not the case, I would like you to answer two questions:
1. Can you tell if the input (mouse and keyboard) is locked on the server side? It should not be responsive while blanking is enabled.
2. Would you be willing to reproduce the problem with a debug package that would allow us to investigate the problem? If so, please contact us via email: forum[at]nomachine[dot]com.

[bucu]

Hi,

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.

[bucu]

Hi,

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?

[bucu]

Hi,

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.

[bucu]

Hello,

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.

[bucu]

Hi,

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.

 

[Author]

Posts