Forum Replies Created
-
Posts
-
Hi, it sounds very similar to this bug report.
Cannot login by NX protocol and private key when option ‘Import the private key to the connection file’ is checked
https://kb.nomachine.com/TR05S10271As a temporary workaround, do not check option ‘Import the private key to the connection file’ in the UI.
We have been unable to reproduce this same behaviour. Logs show an error similar to when the machine is not rebooted, but we know that you did reboot. Ideal would be to debug deeper with a debug package that we would create. If you are interested, let us know. In the meantime we will continue investigating.
Update 15/7/25 – NoMachine 9 was released in May, please update to that and let us know if you continue to have problems by opening a new topic. We can provide a debug package for version 9.
Hi, are you able to send us the server-side logs so we can check them? Please enable debug and reproduce the problem by connecting to that Linux Mint server. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com or post them here. Please use the title of this topic as the subject of your email.
The logs show a possible crash of the nxnode process, which is unusual, so it would also be useful to have the backtrace. Please see the following article for instructions on how to get any core files https://kb.nomachine.com/AR09L00810Thanks!
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.
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!
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.
The logs didn’t show any NoMachine errors or misbehaviour, so this could be an indication that there is a problem with the drivers.
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.
I forgot to add that we also need the ps.log file, so run the following in a terminal.
ps aux | grep X > ps.logand attach that as well. Thank you!
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,compositorin the NoMachine node.cfg file on the server.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 🙂
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.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.