Forum Replies Created
-
Posts
-
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?
What version are you using? This looks like the same bug as this report: https://kb.nomachine.com/TR10T10648, fixed in an earlier version. We are not able to reproduce it on 8.9.
Hi,
first thing to try is disabling hardware decoding on the computer you are connecting from.
Exit the Player and then go to $HOME/.nx/config/player.cfg on your machine, edit the “Enable hardware accelerated decoding” key and set the appropriate value as indicated to ‘disabled’. More about this is in following article: https://kb.nomachine.com/AR07U01202
If that doesn’t help, send us:
– nxplayer logs
– journalctl output (sudo journalctl -x |grep -i gdm)
– /var/log/Xorg.0.log.old (cat /var/log/Xorg.0.log)
– if there is a core file from nxplayer, extract the backtraceInstructions are how to extract player logs are available in section 2. How to Collect Client Logs from Users’ Devices of the following article: https://kb.nomachine.com/DT07S00244. That article also outlines how to extract the backtrace (section 4).
Send everything to forum[at]nomachine[dot]com using the title of this topic as the subject of your email. Thanks!The NoMachine icon represents the NoMachine service i.e that there is a daemon running and that the server is either running or temporarily stopped. If you “shut down” the server (from NoMachine settings) or “quit the service” from the !M icon, the !M icon will disappear, and you will have to open the program from the applications menu, go in to server settings and “start the server”.
Notifications appear from that icon. You will have noticed that when you connect, the message “User xyx is connected” pops up. And if someone is connected to your desktop in desktop sharing, a “desktop is viewed” message appears. More about the !M icon in the system tray can be found here in the dedicated document: https://kb.nomachine.com/DT07S00239.
If I access the Linux machine directly the NoMachine server GUI reports that the NM server is active, but the NM icon can take a few minutes to appear, if it appears at all.
This is what needs investigating. That icon should be visible/accessible permanently if the service is running. It should not be appearing/disappearing. If it is slow to appear, again, this is not normal. We’ll wait for the logs, they will shed some light on what is happening. Your other topic contains the link to the instructions on how to enable them.
Is the Ubuntu installation running Wayland? If you switch to X.org, do you see the same behaviour?
The screenshot is the expected dialog, so you followed the instructions correctly 🙂 It is using a key, and the client is asking for the passphrase of that private key. Is this not what you wanted?
Can I ask what version of NoMachine you were running before you updated it? You need to configure the server settings of the machine you want to connect to accept connection requests – without asking for desktop owner’s authorization. This was also configurable in v7 and it’s likely that you set it to not ask the owner, but there was a change in the name of the key. You should check that in your server.cfg there is the key “PhysicalDesktopAccessNoAcceptance”. Can you tell what its values are or attach the cfg file here?
Another thing you should can is the user name which you are logging in with. As the owner, the popup doesn’t show, but if you connect as a user which is not the owner, i.e another system user, the popup will show.
To disable requesting for the owner’s authorization before connecting to the desktop do the following on the server side:
– Open the NoMachine User Interface from Programs menu or Applications.
– Access the Server settings
– Open the Security panel.
– Go to User Acceptance and make sure that the box “Don’t require acceptance if the user logged in as a system user” is enabled.Does this help? 🙂
Try resetting Permissions for Accessibilty and Screen Recording. Remove NoMachine from both lists (click the ‘-‘ button) and then restart NoMachine (you can do it from terminal with
sudo /etc/NX/nxserver --restart) and follow the prompts that should direct you to enabling permissions again.This is strange behaviour and not one that we are aware. If you send us the logs that we requested in your other topic, we can check if there is anything that indicates why the nxserver is not starting.
We are not able to reproduce this behaviour connecting from Windows to Debian Buster, 8.9 both sides.
What desktop environment are you connecting to exactly?
What do you mean with “If I plug the keyboard directly into the client – it works correctly as it does when I plug it into the host. When I type into the client the keys are translated at the host.” Is this a laptop? So you are plugging in an external keyboard and it works, but when using the device’s own keyboard, you get alternating case text?
Does this happen in all applications?
Apologies for the incorrect link, now corrected and repasted here:
https://kb.nomachine.com/DT07S00243Please use the instructions in this document and not the document you found which is for an old version of NoMachine and does not apply to you. I have pasted the first step here for your convenience.
First Step: Enable Debug Level on the Problematic Server/Node Host
(macOS)Open a terminal on your mac machinee and run:
$ sudo /etc/NX/nxserver --debug --enable allthen continue with steps in the document. You can send everything to forum[at]nomachine[dot]com. Please use the title of the topic as the subject of your email. Thanks.