Forum Replies Created
-
Posts
-
I updated NoMachine on my Mac this morning, and after the update, when I connect to the remote, I can see the screen, but when I move the mouse inside the NoMachine remote window, I don’t see a mouse cursor.
What version of NoMachine was running before you updated?
Can you update to the latest (8.10) and check if the same issue occurs?Logs would be useful in that case.
We are aware of a white screen issue with Wayland. It’s related to KDE running on Ubuntu 22-based versions (also Kubuntu). You can indeed try KDE 5.27. The workaround is to disable Wayland and use X.Org.
Please use the following link to track its status:
White screen occurs when connecting to a KDE/Plasma Wayland desktop on Kubuntu
https://kb.nomachine.com/TR07U10921Hi, what you need is the Workstation product. It’s available in evaluation from the download section of the website here:
https://downloads.nomachine.com/download-enterprise/It lets you run up to 4 “virtual desktops” on the same machine which are also persistent.
Hi ziggy,
we weren’t able to reproduce with or without a KVM switch. So, we need logs from the server 🙂
Follow the instructions here and send them to forum[at]nomachine[dot]com.
How often we make a maintenance release generally depends on what tweaks and fixes have been added. It can be once a month or it can be every 2 or 3 months. If you take a look at the Software Updates section, you can see how often we release updates. We are still waiting for the RPi5 devices we ordered, so that’s why we have not officially “added support” yet (i.e we did not add it to the devices in the download section of the website, nor mention it in our latest release announcement). Adding “support for a distro or OS version, or a device” means that we have tried and tested it in our labs 🙂 In the case of RPi boards in general, there is the issue with Wayland, so please use X.org instead.
By design, and it’s an important security aspect of desktop sharing/screen sharing, NoMachine by default gives priority to keyboard and input events from the local user logged-in to the remote computer over input generated by a user connected remotely via NoMachine. So to lock input only would undermine this.
To answer your other question:
“Is there a way to blank the screen and lock input on the remote connection on-demand after connecting.”
Yes there is. You use the same checkbox that you use in the server settings to blank the screen upon connecting. During the NoMachine session just go to the !M icon of the desktop you are connected to and open the Server settings. Enable screen blanking on the fly. Once you’ve finished, you can disable it and then disconnect.
Hi, we will be adding support for Raspberry 5 in the next release. At the moment there is the following known issue, also reproducible on RPi5. It’s caused by Wayland indeed. The link to the TR is just below, with the workaround which is to disable Wayland.
Hi, if I understand correctly, when you connect with nx, the other users who connect with the [alternative tool) see a blank screen. Is that right? (Just so you understand why the name has been removed, we don’t publish other brands’ names as a policy of the forum 🙂 )
Screen blanking is not supported for VMs, you can read more about this in the following article
https://kb.nomachine.com/AR07M00851– For virtual hosts
Screen blanking is available for physical hosts, it is not supported on virtual machines since it has effect on the physical monitor.Please update to the latest version and check whether the behaviour continues.
If it does, please tell us the steps to reproduce the behaviour. I.e is there a specific activity (e.g move of cursor?) or using a specific application when it happens?What is the desktop you are connecting to? Gnome? Is Wayland running there?
Did you update to 8.10?
That TR we mentioned https://kb.nomachine.com/TR07U1091 was fixed in the latest release.
I forgot to mention that you can try attaching a dongle, this will trick the Mac Mini into thinking there is a monitor attached.
No it isn’t 🙂 Earlier versions had more than one resolution available in headless mode. On Sonoma this changed. Unless of course your Mac isn’t a headless. You didn’t make this clear.
We aren’t aware of random freezes neither in the GUI nor the session. When you say “freeze” are you actually referring to the session or the client window? That is, is it the remote desktop image that doesn’t update, so the image remains frozen? Or is it the NoMachine client that freezes, so you can’t even open the session menu nor click on anything?
A video would be useful to show the problem.
Are both server and client Mac machines?
Logs from both sides whilst you reproduce the problem would be useful. Follow the instructions here to gather logs from the client and the server.
https://kb.nomachine.com/DT07S00244
Send them to forum[at]nomachine[dot]com using the following in the subject “Randomly freezes on Mac M1 Max/Pro”.
Is your Mac headless? This is the reason why you can only see in your system settings one resolution: 1920 x 1080 . And that’s the resolution that NoMachine will display.
Another think that needs to be clarified: you mention “virtual display”. NoMachine for Mac products do not create a virtual display. What you are connecting to is the physical desktop of the operating system.
2000 259 2023-11-06 18:18:01 583.152 Features/Features: WARNING! Assuming 13.0 compatibility.
This is just a warning related to compatibility. In the next update, it will be fixed.