Britgirl

[Britgirl]

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?

 

[Britgirl]

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?

[Britgirl]

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.

[Britgirl]

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?

[Britgirl]

Hi, can you attach the image to a reply here or send to forum[at]…and we can upload it. Do not paste the image into you reply 😉

[Britgirl]

You say “older mac”. Can you tell us the model?

“Blackening out” – do you mean that you see a blackscreen in the NoMachine session window when you connect from the new macbook model to the old mac?

[Britgirl]

Please update to the latest release.

Miltonvo, if you continue to have problems, we’ll need to see the logs. You can follow the instructions here and then submit them to forum[at]email.com

https://kb.nomachine.com/DT07S00243

Bluesmanuk, it could be a different issue. Confirm the distro and version and where you downloaded the NoMachine software from.

[Britgirl]

Connecting to the NX Server via SSH connection requires an Enterprise product installed there. If you have the free version installed on Google Cloud, you should connect using NX. Alternatively you can tunnel an SSH connection using the tips here:

Connecting by SSH to a NoMachine host in version 4 or later
https://kb.nomachine.com/AR10K00728

[Britgirl]

Update to the latest version please. If the issue continues, open a new topic with details of OS versions and clear steps on how to reproduce.

[Britgirl]

Hi, can you update to the latest version and tell us if you still encounter the problem? We’ve still not managed to reproduce the issue.

Submit logs from the player side and we’ll take another look.

Be sure that the Don’t delete log files on exit checkbox is selected in UI -> Settings -> Player -> Security panel before launching the client to reproduce the problem. Do not close the client once problem has been reproduced.

Then collect logs manually: create a compressed archive of the .nx directory in the user’s home. On Windows the .nx folder is hidden. To find it, write the following in the address bar or the file browser:

%USERPROFILE%\.nx

Otherwise navigate through the computer folder till the user’s home and digit .nx in the navigation toolbar to reach it. Path can be similar to: C:/Users/nomachine/.nx

[Britgirl]

Can you update to the latest version 8.7 and tell us if you have the same issue? A similar issue was reported on Debian and a fix was released in the maintenance update of today: https://kb.nomachine.com/TR07U10920

[Britgirl]

A similar topic was posted here with the same workaround: https://forum.nomachine.com/topic/windows-display-scaling-nomachine-makes-it-blurry

[Britgirl]

A portable package is planned and work was already started. We had other priorities in the meantime though and work was temporarily suspended.

[Britgirl]

We are not aware of a similar problem.
So that we can attempt to reproduce, please tell us:

1) macOS version on affected machine
2) NoMachine version on affected machine

[Britgirl]

You can try to see if that helps.

[Author]

Posts