Forum Replies Created
-
Posts
-
Logs point to a problem with Gnome, rather than NoMachine. Logs are showing this:
2919520 2919520 2025-08-25 11:02:12 205.757 NXNODE WARNING! Process '/bin/bash --norc -c exec -a - /bin/bash -c '/bin/dbus-launch --exit-with-session gnome-session --session=gnome'' with pid '2919612/2919612' finished with exit code 1 after 1,369 seconds.NoMachine correctly tries to start a virtual display because it detects that your Linux is headless. But Gnome fails to start. Looking in the journalctl file would identify what is happening with Gnome.
journalctl -b -0 > journal.txtHi, you could try disabling UDP. You do that in Edit connection (Right click the connection in Machines )-> Configuration -> Use UDP communication for multimedia data, and uncheck the box there. Then try to connect.
If that doesn’t help, we need to see the logs from both computers. You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298#1 and #1.2.
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Hi, thanks for the logs. The agent logs were missing, unfortunately. Can you send us the .nx directory from the user’s home on the Linux server side? Just zip up and send via email. Thanks!
Hi, we would need to see the NoMachine server logs from the host you are connecting to and the from the Player device you are connecting from. Are you using the latest version on both sides, 9.1.24? You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298#1. Attach here or send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Hi, we can reproduce a similar problem, clicking on buttons in the right-hand pane in Displays, for example, has no effect, and our developers are currently investigating further. Since Tahoe is in Preview/Beta, it’s possible there could be some further updates still from the Apple developers before they release the final stable version. Thanks for reporting in any case, we will continue our investigation. If we find a workaround, we’ll submit more information here.
It would have been useful to know the version of NoMachine both sides. Are you now using 9.1.24 on both sides? It’s possible that you were encountering this bug, https://kb.nomachine.com/TR06W11427, affecting macOS, which was fixed in the latest 9.1.24. If it comes back, take the logs and a screenshot. Thanks!
Hi, there is a Trouble Report open on this issue: https://kb.nomachine.com/TR08W11510.
A patch is already available, lined up for the next maintenance. If you would like to test it, please reach out to us (either through your User Area or here https://www.nomachine.com/support/report-an-issue) so we can send you the right package to install on your Linux server.
Hi, we need to ask a few questions first to understand your set-up better 🙂
– what NoMachine version is on your Windows client (and which version of Windows)?
– do you know what version is on the NoMachine server, your Linux machine where you are working?
– can you tell us if you are running a virtual desktop session?
– what is the desktop environment you are connecting to where Matlab is running (GNOME, KDE, something else)?
– are you starting the session from the NoMachine Player or are you connecting through the browser (perhaps to the landing pad server that you mention)?Hi, thanks for the follow-up. AR02U01190 does not mention Vulkan so I am not sure which article you are referring to. That article indicates amf-amdgpu-pro with the exact steps to follow.
1. If I install older AMDGPU-Pro drivers (e.g., 19.20 or 20.40) that don’t require vulkan-amdgpu-pro for AMF to initialize VCE, will the latest NoMachine version support hardware encoding (H.264) on my Radeon HD 8330E?
Please install only amf-amdgpu-pro (not vulkan-amdgpu-pro) and follow the steps in the article. I just updated it because AMD website’s link is now different.
2. If the latest NoMachine version is incompatible with these older drivers, what is the latest NoMachine version that supports HW encoding with AMDGPU-Pro 19.20 or 20.40 for my GPU?
It’s not a question of NoMachine version being incompatible. NoMachine v8 and v9 support GPU-accelerated H.264 encoding provided by AMD’s Video Coding Engine (VCE) that uses AMF (Advanced Media Framework) SDK API on the Linux machines having a graphics card that support it, using official drivers from the provider. There are so many system configurations that we’re not able to test, and with all different cards available. We are checking with the latest Ubuntu to see if we can reproduce your issue.
3. Are there specific configuration steps (e.g., in /usr/NX/etc/node.cfg) or workarounds (e.g., using VAAPI) to enable HW encoding with my setup?
No, there aren’t any specific configuration options.
Any guidance on compatible driver versions, NoMachine versions, or alternative approaches (e.g., VAAPI, software encoding) would be greatly appreciated.
There’s not much we can add. As I mentioned earlier, it’s not about which specific NoMachine build. HW encoding on Linux in general is like a lottery and more than often it’s about finding the Linux distro version which works with your video card and the specific driver version. We’re checking in our own set-ups as I said and will come back to you.
“When you say uninstall “plugins”, what exactly do you mean?”
I mean that you should revert what you did here:
sudo mkdir -p /opt/intel/mediasdk/plugins
sudo ln -s /usr/lib/x86_64-linux-gnu/dri /opt/intel/mediasdk/pluginsand start again following the instructions in our article.
Hi, all sessions with Connected status should still be showing, and we are not aware of issues with
--history. Are you able to send us the logs with debug enabled? You can extract from the server machine using the instructions here: https://kb.nomachine.com/DT08U00298#1.1.Hi, we are not able to reproduce this. Can you send us the full process list:
$ ps -efAlso the output of loginctl so we can see the parameters of systemd session with type ‘x11’ (or for all sessions). To do this, first list all systemd sessions:
$ loginctl list-sessionsThen, for each systemd session:
$ loginctl show-session <id>If you want to connect just over LAN, you can connect using the IP address of the target computer. You use the Machine Id of the target host if it doesn’t have a public IP address or is behind NAT. In the latter case, you will need to create a NoMachine account and login on the Player before starting your connection. When connecting with the IP address, you don’t need to.