bucu

[bucu]

Thanks for the logs, we were able to reproduce your issue and are currently working on a fix. Will you be interested in trying it out once we have it ready? It should be ready soon after the newest version is released.

[bucu]

Hi,

We can’t reproduce it in our labs. In order to narrow down the problem we would need to send you a debug version for the server side. Please let us know if you are interested in trying it out. If yes, we will contact you via email.

[bucu]

Hi,

the crash report you’ve attached indicate the problem is with physical session only. Can you clarify what did you mean by “virtual”? Did you mean headless or an actual virtual session?

[bucu]

Hi,

we would need some extra info to investigate further:

1. What is the client machine OS?

2. Keyboard type and layout (or anything that is special about it).

3. Can you clarify what does “restart client” mean? Do you have to restart the client machine, or NoMachine Player alone?

4. Is that stuck fn key on the server or client side? Screenshot suggests server, but you seem to imply that it happens on client side.

[bucu]

Hi Darek,

can you tell me more about your setup: what OS is on the affected machine and what NoMachine version are you using? Is the image being refreshed on those not blanked monitors when connected?

Logs from server side might be useful too. 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 wmacgreg,

we were able to reproduce your problem. We’ve opened a Trouble Report here: https://www.nomachine.com/TR01Q09112. The fix should be included in the next update.

[bucu]

Provided you’ve followed the instructions in the article correctly H.264 will work. The alternative is to use AVC pack which will do all the configuration and libs set up for you, out of the box.
Either way, the only way we can get an idea that you’ve set up everything correctly is with the full set of logs. Instructions were pasted above. Note that the statistics I have asked in the beggining are not the same as logs from server and client side. Please include the top.out file as well.

[bucu]

Hi again,

I don’t see you’ve had enabled H.264. Please follow this link. If you did so and still can’t use H.264 then we would need full set of logs when the slowdown is present in session. You can do it by following those instructions.
Can you confirm the statistics had been taken when the slowdowns occured? You’ve only sent the client side CPU usage. Can you do the same for server side? During a slowdown run top -b -n 1 > top.out and send us the top.out file.

• This reply was modified 5 years, 11 months ago by bucu.
• This reply was modified 5 years, 11 months ago by bucu.
• This reply was modified 5 years, 6 months ago by Britgirl.

[bucu]

In order to detect what is the cause of sluggishness: network or hardware resources, for a start I would:

– check CPU usage on both client and server side;

– gather NoMachine session statistics as shown in https://www.nomachine.com/DT10O00157&dn=session%20menu#9.

Please also make sure you are using H.264 encoding. More info in this article:

What do I need to do to allow NoMachine software to use H.264?
https://www.nomachine.com/AR10K00706

[bucu]

You are using a monitor switch and this is why you are seeing the behaviour. NoMachine is not responsible for that. You can’t have image on both hosts at the same time.

When you connect to the Debian with monitor switch set to Windows host you’ll see only the internal display. This would explain the lower resolution you get (max of the internal display).

[bucu]

Hi,
in order to investigate further we would need the output of xrandr -q when not connected via NoMachine. Can you please paste it here?

[bucu]

Hi,

how are you changing resolution of the remote host? Are you using NoMachine Player’s settings menu or the system settings of the Windows host?
Please note that by design NoMachine will not revert resolution changes made by using the system settings of the remote host. If you need  the initial resolution (the one you had at the moment of the connection) restored, you should use only the NoMachine Player’s UI to change the remote resolution (i.e. by using the Resolution slider in the ‘Display settings’ panel or by enabling the ‘Resize remote’ button).

[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

[Author]

Posts