Britgirl

[Britgirl]

Hi, we were able to reproduce the same issue and a fix is scheduled, not for the next release but the one after that. Here is the Trouble Report. Please use the link to monitor its status.

https://kb.nomachine.com/TR07W11476

[Britgirl]

Hi, is there a monitor attached to the Linux Mint machine you are connecting to?

Is the image of the desktop you see totally frozen? Or do you see some screen changes when you are connected?

Logs would be useful. On the Newby machine, enable debug and try to reproduce. Please follow the instructions here: https://kb.nomachine.com/DT07S00243

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

 

[Britgirl]

Hi, thanks for letting us know and good to know it’s now working again.

[Britgirl]

Thanks for the logs, they were helpful. We have reproduced the same behaviour in our labs and we are actively working to find a solution.

[Britgirl]

The logs didn’t show any NoMachine errors or misbehaviour, so this could be an indication that there is a problem with the drivers.

[Britgirl]

Hi, it is the expected behaviour. UDP is not used in floating window mode because in this mode NoMachine always uses X11 vector graphics. More about “The X11 vector graphics mode in X-Window virtual desktop” is available here if you are interested: https://kb.nomachine.com/AR02L00779.

[Britgirl]

I forgot to add that we also need the ps.log file, so run the following in a terminal.

ps aux | grep X > ps.log

and attach that as well. Thank you!

[Britgirl]

Hi, sorry for the delay in coming back to you. Logs confirmed that the issue is related to a Trouble Report already open https://www.nomachine.com/TR05V11141 and which will be fixed in the next software update. The workaround is to set
WaylandModes drm,egl,compositor in the NoMachine node.cfg file on the server.

[Britgirl]

The debug package needs to be prepared specifically. When it’s ready, you’ll receive an email with a download link. Thanks for your patience so far 🙂

[Britgirl]

Additional debug logs (https://kb.nomachine.com/DT07S00243) are required of the Wayland session to be able to proceed. Please follow these steps:

1. select Gnome Wayland on login window and login to desktop (on server)
2. wait until the server is screen locked so that the problematic situation is present to reproduce
3. try to connect to server while it’s screen locked
4. confirm that problem still exists (nxplayer screen should output error that connection failed)
5. login to server via ssh by command line from client machine and run this command:
gdbus call --session --dest org.gnome.Mutter.DisplayConfig --object-path /org/gnome/Mutter/DisplayConfig --method org.gnome.Mutter.DisplayConfig.GetCurrentState
6. provide the output from step 5 and server-side logs.

[Britgirl]

Thanks for your patience. We were able to reproduce your same issue eventually. There are improvements to be made to USB forwarding of android devices which have USB debugging enabled in general and developers are now working on that. It’s likely that future v9.x releases will include these improvements.

[Britgirl]

The logs show 9864 9864 2025-03-05 21:29:16 414.897 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec –node –user nomachine –priority realtime –mode 0 –pid 49’ with pid ‘10026/10026’ finished with exit code 1 after 0,009 seconds.

This means that the correct privileges are not set.

Did you already follow the instructions in our document for installing on Docker? https://kb.nomachine.com/DT07S00242. We recently updated it.

[Britgirl]

The logs you forwarded were not sufficient. Can you enable debug on the server-side, reproduce and 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]

We are unable to reproduce the problem you have with NX sessions. Note that the option we offer only hides the identity of an unknown server. If you connect to the same server but the identity changes, it is a mismatch that is shown to you for security reasons. It is the same for SSH sessions. So it is better to check the player logs from NX connection and then a set for the SSH connection. You can submit them here, thanks!

[Britgirl]

Hello, it would be useful to know (the same questions as the other topic):

In which way did you uninstall NoMachine:

1) moved NoMachine.app to trash bin?
2) removed /Applications/NoMachine.app dir from terminal?
3) removed /Applications/NoMachine.app dir from SSH session?

Did you see message boxes requesting password and administrative privileges for NoMachine Uninstall?

https://forum.nomachine.com/wp-content/uploads/2024/02/PasswordNoMachineUninstall.png
https://forum.nomachine.com/wp-content/uploads/2024/02/AllowNoMachineUninstall.png

Do you still have /Library/Application Support/NoMachine/var/log. If yes, could you pack the dir and send to forum[at]nomachine[dot]com?

Could you send also output from commands:

which bash

ls -l /bin/bash

id nx

Please check the correct way to uninstall NoMachine in the following article in our KB:

How to uninstall NoMachine on Mac
https://kb.nomachine.com/AR12K00767

[Author]

Posts