bucu

[bucu]

Hi,

Indeed NoMachine is not setting that bit. We added it but it hasn’t change the behaviour for us – in both cases (with and without) VSCode was working as expected. Would you be interested in trying a debug package with that bit set and some logs enabled? If yes please contact us at forum[at]nomachine[dot]com

[bucu]

I was asking whether you had actually forwarded your mouse/keyboard via USB to the server machine. You can read about how to do it in this document (https://kb.nomachine.com/DT06S00218?s=usb#4.3)

However I have the impression that it’s not your case so if possible please send us server and client logs. Instructions on that can be found in my previous post.

[bucu]

We have never encoutered similiar problems. Is it possible that you have your mouse/keyboard fowarded to the sever machine? If this is the case then it is the expected behaviour. If not, we would need logs from both server and client side. Please follow instructions from https://knowledgebase.nomachine.com/DT11R00181 and send them to forum[at]nomachine[dot]com.

[bucu]

The old event API used when setting that key is deprecated and the problem is not on NoMachine’s side so there is little we can do about it.

We would like to hear more about the problem with dragging you have mentioned in the first post. Would you be intereseted in trying out a custom package with debug enabled (assuming we won’t be able to reproduce that dragging problem in our labs)?

As for missing modifiers – it sounds like https://kb.nomachine.com/TR09S10357 can you confirm that this is your problem?

[bucu]

Does the pulsing happen only when using local mouse/keyboard? If yes, then it is an expected behaviour that is meant to show that the machine is not “dead” to a user that is not aware that someone is connected.

[bucu]

Hi,

can you check if any gamma correcting application is running on the server side? It could be f.lux, lunar or something similiar. If they are running you will need to disable them for blanking to work properly.

If that’s not the case we would need server side logs to investigate your problem. Please follow instructions from https://knowledgebase.nomachine.com/DT11R00181 and send them to forum[at]nomachine[dot]com.

[bucu]

Hi,

please try to add the following key in the /Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg file on the server machine:

DisplayServerExtraOptions "-oldeventapi 1"

Restart NoMachine and see if anything changes.

[bucu]

Hi,

you can try using alternate event API. To do so: append DisplayServerExtraOptions "-alteventapi 1" to /usr/NX/etc/node.cfg on the server side. After that you will need to restart nxserver (sudo /etc/NX/nxserver --restart).

If that doesn’t help we would need server side logs to investigate your problem. Please follow instructions from https://knowledgebase.nomachine.com/DT11R00181 and send them to forum[at]nomachine[dot]com.

[bucu]

Unfortunately logs you have sent are from login window not from a session using Awesome WM.
To get proper logs:
1. before connecting with NoMachine make sure that the user is logged in and Awesome WM is running
2. on server side execute: sudo /etc/NX/nxserver --debug --enable all
3. connect with NoMachine to server machine and make sure that the problem is reproduced.
4. on server machine execute: sudo /etc/NX/nxserver --debug --collect

You mentioned you have nvidia GPU. Is the problem present when using nouveau drivers? One more thing we noticed is that the “primary” output is disabled. Can you please remove your randr script and see if with default configuration you still get black screen?

[bucu]

Topnotchprincess

is the black screen present also with different WM?

For further investigation we would need a new set of logs from server side. Please make sure that you are connecting to the user’s session (not the login window one). You can follow this link to be sure you get all the logs.

[bucu]

@Topnotchprincess

Hi,

can you provide us the output of the “xrandr -q” command on server side? Have you tried lowering the screen resolution before connecting with NoMachine? Lastly – does Awesome WM supports scaling like @chiao has described?

[bucu]

Can you please try pasting into the terminal with a combination of Ctrl+Shift+V? Some terminal apps use Ctrl+C/V as their inside commands and clipboard is handled by another one (usually by adding Shift key, but it might vary depending on the terminal you use). In addition have you tried pasting with the middle mouse button?

[bucu]

Hi,

the new problem you described is indeed the result of using that option – some applications use relative coordinates while dragging. We will try again to reproduce your problem and find a fix. If we do, we will let you know in this topic.

[bucu]

Hi,

yes – that option was added in 7.7.4. Please try it out and let us know if it made any change.

[bucu]

Hi,

we recently released a new version that has an option that might help you. May you please edit node.cfg file located in /Applications/NoMachine.app/Contents/Frameworks/etc/ on the server side and add this line to it:

DisplayServerExtraOptions "-relativecoords 0"

You will need to restart NoMachine server (sudo /etc/NX/nxserver --restart in terminal) after that, for the changes to take effect. Please let us know if that helped.

[Author]

Posts