Forum Replies Created
December 19, 2018 at 16:26 in reply to: Resolution issue while connecting to Debian from Windows #20897
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.outand send us the top.out file.December 17, 2018 at 10:59 in reply to: Resolution issue while connecting to Debian from Windows #20851
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/AR10K00706December 14, 2018 at 15:17 in reply to: Resolution issue while connecting to Debian from Windows #20820
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).December 12, 2018 at 10:22 in reply to: Resolution issue while connecting to Debian from Windows #20774
in order to investigate further we would need the output of
xrandr -qwhen not connected via NoMachine. Can you please paste it here?October 12, 2018 at 07:40 in reply to: Screen resolution doesn’t return to initial resolution #19950
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).
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.cfgon 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.
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.
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
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.April 28, 2017 at 09:22 in reply to: Mouse cursor too big on shared screen / remote mouse pointer can’t be turned off #14597
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?
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.
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?
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
April 10, 2017 at 15:11 in reply to: Suddenly unable to control/interact with physical display #14332
- This reply was modified 6 years, 5 months ago by bucu.
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/DT07M00098March 17, 2017 at 07:58 in reply to: "Lock physical screen" doesn’t blank physical display #14074
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.