Forum Replies Created
-
Posts
-
Hi, “virtual desktop sessions” which allow you to run multiple Linux desktops on the same host are available in Terminal Server products. Which product did you install? You should have one of the products from this page installed: https://www.nomachine.com/terminal-server-family. You can check what you have installed by going to ‘Settings > Server preferences > Updates’ on the server host.
You can find some helpful tips on how to configure the NoMachine terminal server product to delete sessions after a specific expiry in the following article in our knowledge base:
How to terminate NoMachine virtual desktops sessions automatically
https://kb.nomachine.com/AR08M00854Depending on the product you choose, there is also full configuration instructions in the product guides here in the Installation section: https://www.nomachine.com/documents
Users can login multiple times on the same server provided the number of virtual desktop sessions has not been exceeded (https://kb.nomachine.com/AR08M00858).
Hi, it’s not clear what NoMachine version you are running. Please confirm the following:
1) on your Mac mini running Sonoma you installed the latest version of NoMachine (now currently 8.10) and there are no problems.
2) on your iMac also running Sonoma you installed an older version of NoMachine and there are problems? What version of NoMachine is it? What error(s) are you seeing? What hardware is the iMac? Have you tried updating to the latest version which supports Sonoma?
You can use the system’s own SSH client. We have an article in the knowledge base which addresses this:
How to use the native SSH client on the end-user’s machine
https://kb.nomachine.com/AR09L00813In the upcoming version 9 this older SSH client will be removed from the Windows client completely.
It would have been useful to have mentioned that you were running Virtual Box 😉 We will never know what was the exact cause but it is likely not related to NoMachine.
Please provide us full details of the set-up including language settings on both sides, and Linux desktop environment. Is it a physical desktop session or are a virtual desktop session? Is the display server Wayland or X.org?
This is important to know. Are you connecting to Gnome, KDE, something else? Is the Debian machine running Xorg or Wayland. To know that open a terminal on the host and echo the
XDG_SESSION_TYPEvariable.echo $XDG_SESSION_TYPEIt will output ‘wayland’ or ‘x11’.
Please attach the screenshot, images cannot be pasted.
Please provide us full details of the set-up including language settings on both sides, and Linux desktop environment. Is it a physical desktop session or are a virtual desktop session? Is the display server Wayland or X.org?
Have I understood right in that if you connect the other way round, so from the Linux machine (with wireless keyboard plugged in to the Linux machines) TO the Windows host, the problem does not occur?
Logs would also be useful. Please follow the instructions here and send them to forum[at]nomachine[dot]com at your earlies convenience. Thanks.
If you send us the logs of the server side, we can check them to see if it is indeed the same problem. Check out this article to know what to do to get those:
https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com.
The MR is planned in the next couple of weeks.
“I installed various Linux distros on it but often the NoMachine display is utterly garbled and pixelated.”
This part is not clear.
We are not aware of NoMachine issues installing on Sierra, everything installs fine, and the NoMachine interface is not garbled. Or do you mean you get this “garbled” effect showing when you connect to a remote desktop? So in the session window? But you mention your File Manager, so could that possibly mean you have some nxs files there, but they are not showing correctly?
Can you send some screenshots (to our email address at forum@..) showing the garbled effect you are seeing? This will help us to understand better.
Hi, there is Trouble Report open for a problem that looks like yours.
NoMachine displays an inactive session as active on Wayland
https://kb.nomachine.com/TR07U10910It will be fixed in the next maintenance.
Hi,
take a look at our article for Jetson Nano
https://kb.nomachine.com/AR02R01074
As advised there:
“We suggest you to install an alternative Desktop Environment (Xfce or Xubuntu) to Unity, which is default on Jetson Nano Ubuntu. That’s because on Unity there can be some minor issues, such as the blinking of the system menu. Cinnamon is also one that we tested which works well.
Make sure you also check the instructions for headless Jetson, section “IMPORTANT – For headless system users”.
Hi ksuuk, this is definitely something we need to resolve. We’ve moved the people we could move onto this, even at the cost of delaying version 9 and Network.
Is there a way to configure the disconnect to do a lock only?
Not sure what you mean here. Lock the physical screen is a separate setting from blank the screen.
It sounds like Xorg could be crashing. We investigated a similar issue to what you’ve described and the results of the investigation were that this behaviour is not triggered by the NoMachine software, but affects all the situations in which the X server “goes offscreen” (not just with NoMachine). What does the stacktrace of Xorg print? Is there a line like this [ 94029.825] (II) AIGLX: Suspending AIGLX clients for VT switch? Cases were reported on Debian/Mint and in one case one of the users reported that switching from XFCE desktop to KDE stopped the crash.
It was also reported in the forums, the users there made some Xorg updates.
"Lock the physical screen when somebody connects" session disappears
If it’s not that, it could be related to this known TR https://kb.nomachine.com/TR08U10994. We reproduced it on Cinnamon desktop. You can follow the workaround described in that link and tell us if it the problem stops.
Hi, thanks for the update. Indeed it seems to be a Proxmox issue, not a NoMachine issue.
NoMachine (Free Edition, I’m assuming that’s what you are using) just connects to the physical session which is started already and we can use configurations which are available in that physical session. That’s why I asked to see was the resolutions are showing in the control panel.
On Linux you can get a virtual display with NoMachine. To do that you just make your Linux headless (
sudo init 3 and sudo /etc/NX/nxserver --restart) and you will be able to create a desktop with NoMachine’s own embedded X server. More details are here: https://kb.nomachine.com/AR03P00973.When you connect with native RDP to Windows you are getting a virtual display, not the physical one. With NoMachine you cannot connect to a Windows virtual display. However, in this link you can find out how to configure Proxmox with Windows 11, there are some instructions on how to get the resolution you prefer: https://devpress.csdn.net/linux/62ea2f1720df032da732ad91.html
This looks similar to a known issue
Sudden termination of Cinnamon desktop when the popup ‘desktop is viewed’ is present
https://kb.nomachine.com/TR08U10994The workaround (follow the link to see the complete description) is open the UI on the Mint machine -> Settings -> Server -> Security -> section ‘Desktop Notifications’ and uncheck option ‘Show that the desktop is viewed when somebody connects’.
Hi,
is NoMachine installed on the OS of the physical hardware or is it running in the virtual machines (which I understand to be Windows and Ubuntu)?
When you go into the control panel of the OS of each of the VM, what resolutions do you see?
If you go in to the control panel of the OS of the physical host, what resolutions do you see?
How are you using RDP to connect? Are you using it to connect to the VM or to the OS of the server?