Britgirl

[Britgirl]

Please try with official NoMachine packages from our own website. We don’t officially support Arch, so to install you need to run:

wget https://www.nomachine.com/free/linux -O nomachine_current.tar.gz

sudo tar zxf nomachine_current.tar.gz -C /usr

sudo /usr/NX/nxserver --install redhat

 

If the problem still persists, please show us your connection and options log files. You can find them in .nx/R-<session_id>/ on the machine you are connecting from.

Your logs from the connection would help us a lot (both client and server sides).  You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243

Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

 

[Britgirl]

Hi, how strange. Can you tell us the exact version of macOS you’re connecting to? Do you have any applications open or running in the background on the macOS when you try to connect?

I take it this is the latest version of NoMachine on both sides, client and server? Logs from both sides could be useful, taken when you can reproduce the problem. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243

Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

[Britgirl]

The forums are currently separate from the Customer Area. So you have two logins: one for the public Forums where anyone can answer, and one for the Support Center for those with valid subscriptions which is a direct line to the NoMachine Support Team. This is going to change in the future when users will only have to register once. In any case, we would still recommend users with subscriptions submit their questions through their customer area rather than the forums.

The steps are:

1) In the Menu, select Get Support

2) insert your Customer ID and password

3) select Support Enquiries in the navigation bar

4) Click Open a Support Enquiry

More info is available here: https://kb.nomachine.com/AR08C00243

If you are not in possession of your Customer ID, please write to us via the website (Contact us) and include the License Id from the license file you are using.

[Britgirl]

Hello,

as an enterprise user you also have the option to open a support enquiry from your customer area.

Take a look at the tips here for headless Linux hosts:

https://kb.nomachine.com/AR03P00973

If the tips there don’t help, then we’ll need logs from the Linux side. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243

Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email.

Also the output of
sudo grep -E "DefaultDesktopCommand|CommandStartGnome" /usr/NX/etc/node.cfg

In our environment CentOS 7 default settings show:

DefaultDesktopCommand "/bin/dbus-launch --exit-with-session gnome-session --session=gnome"
CommandStartGnome "/bin/dbus-launch --exit-with-session gnome-session --session=gnome"

 

[Britgirl]

So you can print regular letter size sheets. The problem is printing labels only on Catalina, correct? On Sonoma, printing pauses.

We need to see the logs from both sides (OS host you are connecting from and the macOS you are connecting to when you reproduce the two separate issues. See the following document for full instructions and send everything to forum[at]nomachine[dot]com. https://kb.nomachine.com/DT07S00243

Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

[Britgirl]

Hi, you didn’t mention what OS your connecting from and what distribution and desktop environment on Linux side you’re connecting to.  Knowing why mouse and keyboard are not working when you connect over Wifi, but do work when you connect over a hotspot is difficult to say. We need to see the logs from both sides (the Linux server side but also on the player device you are connecting from). See the following document for full instructions and send everything to forum[at]nomachine[dot]com. https://kb.nomachine.com/DT07S00243

Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

[Britgirl]

Logs show that Wayland is enabled. Please make sure that Wayland is disabled, reproduce the problem and submit brand new logs.

[Britgirl]

Hi, the screenshot didn’t attach, can you submit it to forum[at]nomachine[dot]com and we will upload it to your topic. Thanks.

[Britgirl]

Ok, we’re now checking the logs.

[Britgirl]

It looks related to this Trouble Report:

White screen occurs when connecting to a KDE/Plasma Wayland desktop on Kubuntu
https://kb.nomachine.com/TR07U10921

Try disabling Wayland and using X.org instead. Does that help?

[Britgirl]

We are producing a similar behaviour and it seems to be caused by a recent nvidia drivers update. You have version 545 (libnvidia-encode.so.545.29.06). Can you downgrade to 535 and tell us if the problem disappears?

Before you downgrade to try, please send us the logs from the NoMachine server. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. Send them directly to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email. Thanks!

[Britgirl]

So you could try the Enterprise Desktop product – it’s available as evaluation software.

[Britgirl]

We have checked MX Linux and have not been able to reproduce any similar behaviour. It would have been useful to know the desktop envirionment on the MX Linux system. It could well be x.org crashing. What’s not clear is your setup. Are you are using MX Linux on the Raspberry or are you using a MX Linux NoMachine client to connect to the Raspberry? If the latter, what is the OS and desktop env is on the Raspberry? If you wish for us to investigate further, please provide us with the full set of NoMachine logs as requested from client and server sides? (link in previous reply).

edit: in your case, using Wayland instead of X.org could help.

[Britgirl]

Hi, do you have a second monitor attached to the M1 laptop? We can reproduce this behaviour if another monitor is attached to the laptop. If this is not your case, please describe precise steps to reproduce.

[Britgirl]

Hi, we will be adding a timeout parameter to the scripts. This will allow you to set a timeout that fits your custom script setup.

so for example, UserScriptAfterLogin "/usr/script/afterLogin.sh --timeout 180.

This will be implemented for version 9.

[Author]

Posts