Forum Replies Created
-
Posts
-
Our initial tests show that it’s necessary to uncomment the “DefaultDesktopCommand” key in the node.cfg.
#For GNOME session:
DefaultDesktopCommand "env XDG_SESSION_TYPE=wayland dbus-run-session /etc/X11/Xsession gnome-session"#For XFCE:
DefaultDesktopCommand "dbus-run-session startxfce4"Maybe you could try these.
The logs show that screen sharing is disabled. This suggests either that “Desktop Shared” is not enabled. You can check this in the NoMachine Server settings on the Debian host.
Or that in Security -> Desktop Access, you have unticked “Don’t allow the owner of the desktop to connect if the desktop is not shared”. Are you always connecting from remote as the owner of the desktop? By “owner”, I mean the same user account that is actually logged on the Debian server.
The free version of NoMachine supports one incoming connection to the system. Have you always been using the free version? Maybe you installed the free version thinking you were installing one of the other products?
Hi, SSH sessions are possible when the server side has a product from the Enterprise suite installed. It’s definitely possible to run an NX session through an SSH tunnel. Check out this article for the instructions:
Hi Sven, thanks for coming back with your findings and the link. This is indeed a bug with the nvidia drivers and not something that we can fix in the NoMachine software.
Hi Jon,
The free edition of NoMachine is for access to the physical display, so it’s the correct behaviour. Maybe what you are looking for is NoMachine Workstation from the Terminal Server family for Linux? Check out the differences here: https://kb.nomachine.com/AR10K00702. The Workstation is available to download here: https://www.nomachine.com/product&p=NoMachine%20Workstation.
If no input is arriving on the Mac side, it could be a simple issue of permissions not set on the macOS system during installation of NoMachine. Go to System Settings > Privacy > Accessibility and then “+” and add NoMachine. If it’s already there, remove and add it again (see this article https://kb.nomachine.com/AR11Q01061). Then connect again from Windows.
The GDM issue could be this: https://www.nomachine.com/TR07S10316.
About the blurry screen connecting from Windows (your images may be too large for our upload tool, email is best):
– Right-click the NoMachine app shortcut on your desktop and select Properties
– Select the Compatibility tab
– Click “Change high DPI settings”
– Check the box “Override high DPI scaling behavior”
– Select “Application” from the combo under “Scaling performed by”Does that help?
Hi, can you submit the screenshot to forum[at]nomachine[dot]com?
Also, when you try to connect to GDM as your desktop environment, what is the NoMachine message that you see?
Hi, this is a similar issue to a couple of other topics (see below) and we have opened a Trouble Report which you can see here: https://www.nomachine.com/TR03V11111.
No sound forwarding (option to change settings is greyed out)
The fix is going to be released in 8.12.
Can you check whether the Command key (corresponding to the Windows key) actually gets pressed in Dragon? You can do this with Mac’s onscreen keyboard. Go to Apple menu > System Settings > Accessibility > Keyboard > Accessibility Keyboard.
Hi, which previous topic are you referring to? One you opened in 2020 is about macOS.
You say that from Windows you can connect to the Debian server without problems. We assume you are connecting to the same Debian server as when you connect from the Debian client. Right?
Can you submit a screenshot/screenshots of what you see when you try to connect from the Debian client? Are any error dialogs shown?
Logs from the two Debian machines would be useful. Please follow the instructions here to enable debug and then gather the logs.
https://kb.nomachine.com/DT07S00243. Send them directly to forum[at]nomachine[dot]com. Thanks.Biglia,
In safe mode nxplayer starts normally, after reboot it doesn’t work again.
You also said that NoMachine works well on the other Windows computer you tried it on. So it’s something specific on that affected PC which you will have to debug. This can be done by checking the services and software (not started in safe mode) and disabling/uninstalling them one by one, and trying to open nxplayer each time. Could it possibly be an antivirus creating a false positive? It’s worth checking. The other user in this thread said Bitdefender had been preventing nxplayer from opening.