Forum Replies Created
-
Posts
-
Hi timo, this is the same issue as Ubuntu 25.10 and using the default desktop environment Gnome 49 with Xorg removed. We are actively working on a permanent solution for users wanting to connect to the virtual display on Gnome 49.
We have an article about this here:
Ubuntu 25.10 Questing Quokka drops Xorg/X11 support, what this means for NoMachine users.
https://kb.nomachine.com/AR10W01330.The same tips written there for Ubuntu 25 users can apply to your case with Fedora.
If you still need to run virtual sessions, alternative temporary solutions are:
1. Install another desktop environment compatible with X11, such as MATE, KDE Plasma or XFCE.
2. Use an earlier version of GNOME, prior to version 49, which still supports Xorg.
3. Use an earlier version of Fedora.
I am pasting what you have written above
sudo /usr/NX/scripts/setup/nxserver –-uninstalland now I’m pasting what the command is in our guide
sudo /usr/NX/scripts/setup/nxserver --uninstallI see a slight difference in the ‘-‘ you are using. I don’t know if that is an error in the paste and how it shows in our forum or if you copied from your terminal. But please check this. If you don’t use the right command, the output you show is expected.
Sorry I pasted the command to use for non-default locations. Here are the commands, again, from the guide I previously linked.
UNINSTALL
sudo /usr/NX/scripts/setup/nxserver --uninstallthen, remove the installation directory:
sudo rm -rf /usr/NXThe stack dump says that libnx fails to read or create the user NoMachine folder, and because of that, it aborts and causes the process to close. Can you send the
%USERPROFILE%\.nx\R-*logs? In there we might find more details about what’s happening.Hi, when you say “update” do you mean an update of NoMachine or a Windows update? Can you tell us the specific build version of the Win 11 host?
PopOS is based on Ubuntu, so it should not be that different. The only issue we are aware of is on the latest Ubuntu 25, virtual display sessions are not possible because Ubuntu has removed support for Xorg. See this article for reference: http://www.nomachine.com/AR10W01330.
Screenshots or images which show the problem would be useful.For uninstall instructions, take a look at the installation guide: https://kb.nomachine.com/DT07S00245#2.7
sudo /opt/NX/scripts/setup/nxserver –uninstall
Then, remove the installation dir:
sudo rm -rf /opt/NX
PopOS is based on Ubuntu, so it should not be that different. The only issue we are aware of is on the latest Ubuntu 25, virtual display sessions are not possible because Ubuntu has removed support for Xorg. See this article for reference: http://www.nomachine.com/AR10W01330.
I only have access to one of two monitors from client machines
NoMachine does not echo input from either a Linux or Windows clientPlease explain exactly what you mean. Screenshots or images which show the problem would be useful.
For uninstall instructions, take a look at the installation guide: https://kb.nomachine.com/DT04U00269#2.7
sudo /opt/NX/scripts/setup/nxserver --uninstallthen, remove the installation directory:
sudo rm -rf /opt/NXHi Lucas.B, we have registered your interest in a NoMachine for Windows ARM 🙂 Did you already see our recent reply to this topic https://forum.nomachine.com/topic/can-we-please-have-an-windows-arm64-version? We’ll post any updated information about available native packages for ARM on these forums. Work has already started 😉
Hi, thanks for the logs. We can see a crash of nxnode:
3245 3245 2025-10-21 08:48:00 759.364 NXSERVER WARNING! Process '/usr/NX/bin/nxexec --node --nopam --user agt --priority realtime --mode 0 --pid 53' with pid '5816/5816' finished with exit code 11 after 735,372 seconds.The logs, though, were missing the agent/node components, which would tell us why the nxnode is crashing. Are you able to send us the full logs? You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298. Please follow the steps for extracting through the UI.
Also look for a core file or a crash report from nxnode and send the backtrace to us. Instructions on how to do that are here: https://kb.nomachine.com/AR09L00810. You can attach everything here or send them to forum[at]nomachine[dot]com. Thanks!
Hello,
adding an option to swap Control and Command modifiers on the remote desktop was implemented in 9.0.188. Are you using v9 on both client and server sides?
The new option is added in connection menu -> Input. You can see a screenshot in “Guide to the Functionality in the Menu Panel on Windows”. The label is “Map Ctrl to Cmd and Win to Ctrl”. When this option is not enabled, instead, the user has to use the remote modifier for applying keyboard shortcuts inside the NoMachine session.
Hi, thanks for the logs provided. We found an issue (not the same one as TR06W11409 mentioned above) that could cause a crash of the nxserver daemon process and we are already working on fix. You can use this link to monitor its status: https://kb.nomachine.com/TR10W11608.
The output seems ok. The monitors are extended so all should work. You can use Ctrl+Alt+A shortcut to see all monitors, or Ctrl+Alt+1 (or 2) to switch between them. Check this guide out for more details: https://www.nomachine.com/support/documents/switching-the-view-between-multi-monitors-during-a-remote-desktop-session. Are you not able to switch between them?
Please submit the output of ‘ps -ef’ and new server logs. You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298 using the UI. Set the level to Debug, restart the server, reproduce the problem, then “Take logs”.
You can attach everything here or send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
It seems you have enabled a v3 compatibility option in the server.
# dialog=1 display the disconnect/terminate dialogwhich is in the #ConnectPolicy key of the server.cfg.Try setting dialog=0
#ConnectPolicy autocreate=1,autoconnect=1,automigrate=1,desktop=0,dialog=0,xsessions=0,udp=1Now, the terminate button is in Connection info panel. When you close the client window, it just disconnects.
Hi, we have this planned. It was put aside in previous versions to allow us to focus on other priorities, namely NoMachine Network. Development will start soon. About using the x64 package, you can use it, our tests were ok except for functionality that requires device drivers. Installing through chocolatey also worked.