Britgirl

[Britgirl]

All NoMachine Linux Terminal Server products support VirtualGL, including the evaluation version. You need to enable VirtualGL first, so this is the first thing you should check. How to do that is explained in the following article:

How to enable VirtualGL support on Linux in NoMachine
https://kb.nomachine.com/AR05P00982

In short, the commands to use are sudo /etc/NX/nxserver --virtualglinstall and sudo /etc/NX/nxserver --virtualgl yes. But please consult the article for full steps.

Let us know if following those steps helps.

In your output of the client, we can see that HW encoding is working correctly. On the client side the session is using software decoding, and not hardware decoding. If this is not what you expected on the client side (we are not sure from what you wrote), you should send us logs from the device you are connecting from and we will check them. See this article (step 4) https://kb.nomachine.com/DT07S00243.

[Britgirl]

We could send you a package for you to install with higher debug enabled for mdns discovery which could allow us to investigate (given that we can’t reproduce it). Are you available to try that?

[Britgirl]

Your connection logs say that server uses resolution 3840×2160, and connecting client tries to change it to 1698×965 since the resize display mode is enabled. However the desktop turns it back again to 3840×2160 (this is up to the desktop environment) and the client is forced to enable the viewport mode, because the resolution is too big for the client display.

Can you confirm that, in this particular test, the reason why you see only part of the screen is not due to the client running in viewport mode? (i.e check whether the client is running or not running in viewport mode)

We also need to ask you for some additional information:

– Output of the command xrandr -q executed in a terminal window on the server

– We would like to try again to get server side logs. You don’t need to restart the
server after enabling the debug logging, just reproduce the issue and get a set
of logs:

1. sudo /etc/NX/nxserver --debug --enable all
2. Connect to the server, reproduce the issue and while the session is connected go to the next step
3. sudo /etc/NX/nxserver --debug --collect
4. sudo /etc/NX/nxserver --debug --disable all

Send everything as before 🙂

[Britgirl]

I don’t know what Wayland or Xorg are, but I did modify some setting to disable something related to Wayland

So please check that Wayland has been correctly disabled.

As sudo, edit GDM file with a text editor:

sudo vim /etc/gdm/custom.conf

Find the WaylandEnable line and modify it to this:

WaylandEnable=false

Remove the pre-prending # to force the login screen to use Xorg

If there is no such line, you can add it in [daemon] section.

Save, and then reboot.

[Britgirl]

You can change the shortcuts how you want using the panel here. There must be at least 2 keys for each shortcut.

See this guide, https://kb.nomachine.com/DT07S00236#2.1, and scroll to “Use keyboard shortcuts for quick actions”.

[Britgirl]

Thanks for those, they were useful, so we will continue to investigate this in our labs. In the meantime, if possible add NoMachine to your firewall exceptions (so as not to keep you FW completely turned off). If you encounter any more issues, let us know.

[Britgirl]

Hi, could you please update to the latest 8.14 release and if you still have issues. If so, I suggest to open a new topic.

[Britgirl]

Thanks for reporting back. Should any new crash reports be produced (now that you are using 8.14), feel free to send them to us. We’ll keep the topic open for a while so you can submit them here.

[Britgirl]

psantucc, we are preparing a new package with a possible fix for you to test. We’ll let you know when it’s ready.

[Britgirl]

And did that change anything?

[Britgirl]

Hi, please send us the output of xrandr command run in the remote desktop, and the logs from both sides. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243 (steps 1 through to 4). Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

 

[Britgirl]

Fajny, is it possible that you have installed a 64-bit package on a 32-bit system? This could explain why the library cannot be loaded.

[Britgirl]

Hi, please send them privately to our email address rather than here. IPs and usernames (not passwords) are present in nxserver.log, nxinstall.log, nxservice.log. If you wish to remove this information before sending, you should edit those in a text editor before sending.

[Britgirl]

We won’t send a debug package for the moment, at least not for the bad message issue.  However we would be interested in seeing that other crash report you mentioned. And the NoMachine logs from the Mac, zip up the entire .nx directory in the user’s home.

[Britgirl]

Hi,

we checked the logs. It looks like the macOS server ran out of available shared memory, and NoMachine needs to allocate shared memory to work. You can list allocated shared memory segment with the ‘ipcs -m’ command, and you can remove them one by one with the ‘ipcrm’ command, but it would be much easier (and safer) to just reboot the system.

Please also check if you have any crash report for the nxnode process in the ‘/Library/Logs/DiagnosticReports’ or ‘~/Library/Logs/DiagnosticReports’ dirs. If you find them, please send them by email as well. If they were produced by an older NoMachine version, it could still be interesting to have a look.

[Author]

Posts