Forum Replies Created
September 2, 2021 at 11:05 in reply to: NoMachine not using Nvidia GPU for encoding in Ubuntu 20.04 #35079
There is now a Trouble Report documenting this issue.
NoMachine does not work correctly after installing on Windows XP 64 bit
It will be released in the next software update.
Removing panels is easy. Just click on any panel, go to settings and there you should have a dropdown list.
However, your problem seems to be unrelated to NoMachine software. If those boxes are visible even when you are not using a NoMachine remote desktop session, you should really ask in the Xfce forums.
Or do those boxes visible only appear when you are in a NoMachine session?
Thanks for letting us know. If you have any other questions or issues, feel free to submit a new topic.
“I changed it on one server and it apparently changed it on all my servers. It has not made any difference.”
This is not clear. You shouldn’t be changing anything in Server Settings. Disabling HW decoding is generally done from within the NoMachine session.
If you start a connection in the regular way, you then open the connection menu (Ctrl-Alt-0) from within the session and select ‘Display’ and then ‘Change settings’.
Click modify and check the box “disable hardware decoding” (check this guide for an example https://knowledgebase.nomachine.com/DT10R00167#5.8).
Please provide clear steps of the problem related to NoMachine software (assuming this is a web-based session).
Hi, at first I thought it might be nested sessions which was causing the problem, but it works for us with VirtualBox 🙂 From Mac to Win VM, start a new session and connect to Mac, (we had to enable grab keyboard in the NoMachine player before starting the session from the Win VM).
With VMware it doesn’t work because basically VMware changes cmd to Ctrl , so it appears to be more of a problem with VMware? We tried with Fusion as well, cmd+N works, but cmd+C, cmd+V are transferred as ctrl+(C/V).
Not sure what the issue is with your installation or system configuration (cifs?), but we tested on-the-fly with Pardus and it works fine. What NoMachine errors are you seeing when trying to install or connect?
The NoMachine GUI is an integral part of every NoMachine server package, because it is not just a client but also an interface for server administration. Since a client is never automatically started unless the user does it, it has never been a problem. However if you need to configure an environment where users cannot start NoMachine connections from a machine working as a server, you could try to change the permissions of the ‘nxplayer’ binary to remove executable flags.
Try disabling hardware acceleration decoding. This is similar to another topic. Try the workaround there.
Select that icon and click ‘Edit’ and check what IP is being used. Check that this is the correct IP address just to make sure. Show me what you see.
If it’s correct, it could be a non-native firewall installed on the server perhaps? Disable it temporarily to test connecting without the firewall.August 4, 2021 at 08:46 in reply to: Player exits suddenly when connecting on Linux Mint 20.2 (Ubuntu 20.04 LTS) #34713
In a “normal” situation you would disable “Enable hardware accelerated decoding” during the connection, via the connection menu. So the user can already edit the settings like this for the player. But in your case this would not have had any effect because the crash seems to happen before the session is actually established.
You might want to take a look at the connection menu guide for explanations on what the various check boxes do. In your case, the guide for the menu panel on Linux is here https://www.nomachine.com/DT10R00167. Go to section 5.8.
Depending on your OS, they are all linked in the Configuration section here: https://www.nomachine.com/all-documents. You will find a lot of useful information there.
There is an article in our KB, linked from the Documents page, about the most common cfg settings.
The most frequently asked options for pre-configuring the client and the session behavior
https://knowledgebase.nomachine.com/DT11R00186August 3, 2021 at 16:15 in reply to: NoMachine time lag after remote computer inactivity/lock screen #34707
Can you give us more details of the problem you are/were experiencing? I’m not sure how lag can be affected the change of resolution.
– connecting client and server OS and version details
– what are you changing exactly and where/how?August 3, 2021 at 15:37 in reply to: ‘Session Manager’ idea – is this possible? Alternatives? #34706
OK let us know how you get on 🙂August 3, 2021 at 15:34 in reply to: Player exits suddenly when connecting on Linux Mint 20.2 (Ubuntu 20.04 LTS) #34705
From the logs it appears va-api is broken and is probably causing the crash of the player. Usually such problems are inner VA-API libs/drivers problems occurring with some specific system configuration, and are not related to NoMachine code.
Try changing this key in player.cfg:
“Enable hardware accelerated decoding”
“disabled” (not to “false”).
Does this help?