Forum Replies Created
-
Posts
-
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.
We would need logs from both the client and server side. For server side logs, please follow the instructions here:
https://kb.nomachine.com/DT08U00298#1.1. For the client side player logs, please follow the instructions here: https://kb.nomachine.com/DT08U00298#1.2Can you tell us if input works after enabling ‘Grab the keyboard/mouse input’ in the session menu? (Ctrl-Alt-0, Input, tick the two boxes Grab the keyboard input and Grab the mouse input). Thanks.
Please attach a screenshot of what you are seeing (it is not advisable to paste images directly into the topic or your reply).
Logs would be useful as well. After reproducing the problem, on the server host you are connecting to, open the NoMachine Settings > Server > Security > scroll down and take the logs. You can attach them here or send directly to forum[at]nomachine[dot] if you prefer. In that case, please use the title of this topic as the subject of your email. Thanks!
Hi, what kind of “monitor combinations” have you been trying? 🙂
In any case, depending on the video card and drivers, it’s possible that the GPU is turned off on a headless system, so in that case, screen capture would also be impossible. On previous versions of Gnome that still support(ed) X11, NoMachine would be able to create a virtual display in these specific cases, but this won’t work with the version of Gnome that is present in Ubuntu 26.04. Running pure Wayland virtual desktops will be added in NoMachine 10, so watch out for that. For now you could consider using a different desktop environment or attach a dummy HDMI dongle.
Hi, these logs are not from the server and not the correct logs from the player. Let’s get a complete set:
For the correct player logs, the device you are connecting from, first we must make sure they are not deleted:
Step 1 – Open the UI on the device -> Player Settings -> Security
Step 2 – Enable the option ‘Don’t delete log files on exit’.
Step 3 – Connect and reproduce the problem.
Step 4 – Go to the Player settings again on the device you started the connection from, Player -> Security -> Take logs.
Then you can collect the server side logs, on the machine you are connecting to (https://kb.nomachine.com/DT08U00298#1.1):
Step 4 – Open the UI on that host -> Settings -> Server -> Security
Step 5 – Scroll down the Security panel till the end to find section ‘Server logs’ -> Take logs.
Attach everything here or send direct to forum[at]nomachine[dot]com. Thanks!
Also, can you describe exactly what happens if the “grab the keyboard” option is selected. Does Alt+Tab starts on Windows? Does the Alt+Tab key sequence work on the Mint host as it should?
Hi, we are not able to reproduce. Alt+Tab works when there is grab keyboard enabled from Win11 to Linux Mint 22 with Cinnamon desktop. Can you update to 9.7 and report back? If you are still encountering the issue, logs could be useful (from both sides) after having reproduced the behaviour. You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298
You can attach them 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, thanks for reporting. We have reproduced the problem and it will be fixed in the next update (post 9.7).
Hi, NoMachine turns on Mouse Keys when it detects that no mouse is attached to the server. We know that this is not ideal, but it’s the only way for NoMachine to be able to show the cursor. In fact, the OS sets an invisible cursor when there is no mouse attached, unless Mouse Keys is enabled. If you don’t have a mouse attached to the server, you could try attaching one.