Forum Replies Created
-
Posts
-
We’d still like to have new logs if that’s possible. From that last set, we see that you installed the library, but you didn’t reproduce the problem afterwards 🙂
Hi, you can send the logs to forum[at]nomachine[dot].com. Please use the title of this topic as the subject of your email. Thanks!
Hi, logs don’t show any new connection attempt after replacing the library. Please connect to the server again, reproduce the problem, then gather new logs.
Hello,
thanks for your patience. We analyzed the logs, but they don’t show any error, nor give an indication of where the error could be. To proceed further, we would like to see logs from both the working and the non-working case, so that we can compare them.
Hi,
is this a headless machine?
Are you connecting to the physical display?
When you connect, is the desktop you see in the NoMachine Player the same as the local Linux desktop?In the meantime, you could try disabling hardware decoding on the Windows (client) side – connect, open the NoMachine menu, go to Display > Change display > Advanced Option (Click Modify) > Tick the box for Disable client side hardware decoding.
Could it be that NoMachine is trying to connect to a session already running through another remote access tool? This could be interfering with the keyboard layout. You could try killing that session and then connect with NoMachine to connect to that headless machine. NoMachine will start its own virtual display.
Please refer to the following topic for tips about headless machines and running a virtual display on Wayland: https://forum.nomachine.com/topic/ubuntu-26-04-gnome-wayland
Virtual displays on Wayland will be supported in the upcoming version 10.
Hi, we reproduced the no keyboard/mouse problem on Arch in our labs after a system update. The problem is due to the system failing to load the uinput kernel module after the update. The errors in the logs match the ones in your logs. This issue has been reported also in the Arch Linux forum:
https://bbs.archlinux.org/viewtopic.php?id=212744
It’s not clear how the second GPU can affect your case. In our labs rebooting the system solved the problem. Please let us know if a reboot helps in your case and if you are available to install a debug library for us to investigate further.
You can set the IP address which has to be broadcast by uncommenting the following key:
#
# Specify the network interface where the NX service will be bound.
# Populate the field with an IP address or a domain name.
#
#NXdListenAddress “”Restart the nxserver after making the changes. This key accepts one network interface (IPv6 or IPv4). In the upcoming NoMachine 10, it will be possible to specify multiple network interfaces.
We’d like to send you a debug package which will allow us to extract more detailed logs. Can we send you the link to the package with further instructions?
Hi, we’ve reproduced and opened a Trouble Report. You can use this link to monitor its status.
Any HDMI dongle should do the trick, we have not had reports about specific dongles not working. We’re not aware of any “Virtual Display Driver” equivalent for Linux. As mentioned earlier, support for Wayland virtual desktops will be added in NoMachine 10.
Related references:
https://kb.nomachine.com/AR10W01330
https://kb.nomachine.com/AR02P00969
https://kb.nomachine.com/AR04R01083
https://kb.nomachine.com/AR03P00973Hi, we got the logs, but we need you to send fresh set. It’s important to revert the WaylandModes key to its default value, i.e. ‘egl,drm,compositor’ (or just comment out the key). Then restart the NoMachine server, reproduce, and send logs again. Apologies if this was not made clear. Thanks.
I forgot to add, send logs so we can check it’s not a different issue, https://kb.nomachine.com/DT08U00298#1.1. Submit here or send directly to forum[at]nomachine[dot]dom.