graywolf

[graywolf]

Hello.
Can you send the file nxdx.log located in the folder %PROGRAMDATA%\NoMachine\var\log\ ?
You can upload it here or send to forum (at) nomachine (dot) com.

[graywolf]

So the physical screen of the server would show the same problem. Is the server headless, with display manager turned off? In such a case NoMachine would ask you if you want to create a virtual display.

Enable verbose logging:

/etc/NX/nxserver --debug --enable node
/etc/NX/nxserver --debug --enable server

Disable log cleanup in /usr/NX/etc/node.cfg:

SessionLogClean 0

Then connect to the remote server and reproduce the problem.
What is the command set in node.cfg (search for DefaultDesktopCommand)? Search log file /usr/NX/var/log/nxserver.log for that command.

[graywolf]

Would you change scrolling options in System Preferences? Go to Accessibility -> Mouse & Trackpad -> Mouse Options. Try to change scrolling speed and turn “with inertia” into “without inertia”.

[graywolf]

As macOS hasn’t NumLock it is always considered in “off” state. When macOS client connects to the server the state of NumLock is synchronized with the client. There isn’t any configuration that can change such behavior.

[graywolf]

When I am using logitech M720 mouse, the extra buttons events don’t seem to be passed to Ubuntu.

As the sculpt mouse is working (see my question below) I suspect mac needs some drivers to make logitech work correctly.
How do the extra button work in local application on the mac computer?

However, when using my microsoft sculpt mouse backward button is working fine with Ubuntu.

What about the forward button, does it work too?

Please, test the button events with command xev -event button. What do you get?

[graywolf]

Press Ctrl+Alt+0 in the NoMachine client, while the remote session is connected. Menu shows up, then click on Connection. Read the session type there.

[graywolf]

Are you trying a Custom, Single application, Floating window session?

Could you try a different client host (Linux, if possible) and see if you get the same result?

[graywolf]

I’d try one of these:

1. Open “Control Panel\Hardware and Sound\Power Options\System Settings” and chose “Do nothing” fro the action “when the lid is closed”.

2. Open NoMachine server settings and uncheck “Use acceleration for display processing”.

[graywolf]

I cannot reproduce using VS code version 1.40.1-1573664190.

Did you get any error in NoMachine log?
Would you get the NoMachine stats from Connection menu?

[graywolf]

Maybe we have two different issue.

Is the host joined to a domain?

What account type is the desktop owner account when you try to change settings (local normal, local administrator, domain normal, domain administrator)?

What exactly happens when you try to change settings? Does a window show up, requiring Administrator credentials? If so, what type of Administrator account you try to use (local administrator, domain administrator)?

[graywolf]

Hello, would you tell me the version of VS Code and the GNU/Linux distro you are using?

Which is the version of NoMachine software?

[graywolf]

Would you try this patched library and tell me if it helps?
It can be deployed only into an existing installation of NoMachine 6.8.1.

https://download.nomachine.com/44bef5297fe9efb3430b9fd47ad18b01/downloads/temporary/forum/libnxdimi.so

Stop the server:
/etc/NX/nxserver --shutdown
Save the original:
cp -a /usr/NX/lib/libnxdimi.so /usr/NX/lib/libnxdimi.so.original
Place the patched library:
cp libnxdimi.so /usr/NX/lib/
Start:
/etc/NX/nxserver --startup

[graywolf]

The report is useful, but it looks generated two days ago and could be about a different problem. It is useful, but I’d like to be sure we got a fresh one. Do you mind deleting the existing file /var/crash/_usr_NX_bin_nxnode.bin.1000.crash, reproducing the crash, and processing the new *.crash file?

[graywolf]

Hello.
You should have the crash report: /var/crash/_usr_NX_bin_nxnode.bin.1000.crash.

Process the crash report with command apport-retrace:

apport-retrace -o nxnode-with-trace.crash /var/crash/_usr_NX_bin_nxnode.bin.1000.crash

If the command fails with “ERROR: report file does not contain one of the required fields: Package”, append the field to the report in this way:

echo Package: >> /var/crash/_usr_NX_bin_nxnode.bin.1000.crash

and retry.

Then let me see the output file: nxnode-with-trace.crash.

[graywolf]

Are you trying to share the existing desktop of the Ubuntu host?
Is the Ubuntu host a virtual machine?
Would you create an archive of folder /usr/NX/var/log and send it to forum (at) nomachine (dot) com ?

[Author]

Posts