Forum Replies Created
-
Posts
-
This thread will now be closed. You can sign up to receive notification about when the patch is available.
You will need NoMachine or Enterprise Client installed on the computer you are connecting from, and then to get to the server, yes, you will need to install a NoMachine server. See here for more details: https://www.nomachine.com/getting-started-with-nomachine
Choices of server are: the free version or one of the products from the enterprise-oriented range. Note that installing NoMachine on your Dell server will get you access to the physical desktop. If you would like to be able to run multiple Linux desktops (in your case, CentOS), then you will need a NoMachine server with the terminal server functionality: Workstation, Terminal Server, Enterprise Server or Cloud Server. What you download and try depends on your specific needs.
Hi, we’re able to reproduce this and have opened a Trouble Report so that you can track it. Check the Notify me box, https://www.nomachine.com/TR03N06589, so you can receive an alert when a fix is available.
Once this has been implemented: https://www.nomachine.com/FR03M02896.
Right now it’s in its final stages of development, and then the testing phase will commence, so I can’t indicate a specific version. You can sign up to be notified when it’s released.
This topic will be closed. The remaining issue can be tracked using the link https://www.nomachine.com/forums/topic/error-is-22-invalid-argument-2 and the Trouble Report https://www.nomachine.com/TR03N06559.
Hi,
this is a bug and we have opened a Trouble Report which you can see here: https://www.nomachine.com/TR03N06561
Use the ‘notify me’ tool to know when we’ve released a patch for it.
What you need is the Workstation for Linux. This will allow users to each run their own Linux desktop. Workstation allows up to 4 individual virtual Linux desktops.
Yes, we opened it yesterday after reproducing. You can use the ‘notify me’ box on the Trouble Report page to receive an email alert when the patch has been released.
Hi, this is a bug which has just been fixed in today’s release https://www.nomachine.com/SU07N00100
The TR is https://www.nomachine.com/TR03N06563.
We’ve tried with the same kernel version, we can’t reproduce it. What I suggest is that when you’ve moved over to Arch and if you come up against the same problem, you submit the logs.
Looking at the script, there’s an error.
#!/bin/sh
setxkbmap fr
exit 0It should look like:
#!/bin/sh
XAUTHORITY=/home/$2/.Xauthority /usr/bin/setxkbmap fr -display :0setxkmbap needs to know which display has to be used and where the cookie is available, so every custom script you prepare with setxkbmap will require XAUTHORITY and -display.
It might be a good idea to also enable the error logs from scripts and setxkbmap just in case:
Add this to the beginning of the scripts ‘exec >> /usr/NX/var/log/custom.log 2>&1’