Forum Replies Created
-
Posts
-
“Make a grab pointer option” has just been added to the roadmap 🙂
Adding the ‘Grab the mouse input’ option to the NoMachine menu panel inside the session
https://www.nomachine.com/FR11K02793Hi hansd,
we’ve inserted a new Feature Request into the development roadmap which you can track using the following link:
Starting the session by passing options to the client from command line
https://www.nomachine.com/FR11K02794A very basic rule of security is that people contact the software vendors before posting in a public forum, so that others can’t exploit the security fault until the fault is fixed by the vendor.
Regardless this problem is a security fault or not, we hope in the future all posters play nice and follow the rules.
Hi mt, can you post a new topic if you are having problems with resuming sessions on your 3.5.0 server? This way we don’t embed too many issues into one topic.
Thanks!
Hello Michal, please check this article: https://www.nomachine.com/AR11K00740
You can try putting the following in the .profile of the user, to force the setting, or find a way to let Yast automatically apply your setting when you login.
setxkbmap -rules evdev -layout fr
Note that this appears to be a Yast bug. I don’t see any reason why it should “forget” about your setting once you have set the keyboard in Yast,
I should note that NIS (aka yp) is in play
Yes, indeed the auth method used can be a useful detail when having to investigate a login failure.
Our test team is re-checking NIS auth and will let you know.
Hi Plop38746, check the lastest update.
Details of all fixes are here:
https://www.nomachine.com/SU11K00104Please also attach the logs files:
# tar zcf logs1.tar.gz /usr/NX/var/log
# tar zcf logs2.tar.gz /home//.nx Be sure you include all the information listed here:
– NoMachine product and version on local and remote machine (free version, Workstation, etc).
– Whether the problem arises connecting to a physical or a virtual display.
– If on Linux, desktop version (GNOME. KDE, whatever) on client and on server.You can send the files to issues[a]nomachine.com making sure you use the title of your forum post as the subject.
Hi csteelatgburg,
Are there any crash reports of nxnode in: /Library/Logs/DiagnosticReports/ ?
Can you send us the log files? (issues[at]nomachine.com)
# tar zcf logs1.tar.gz /Library/Application\ Support/NoMachine/var/log/
# tar zcf logs2.tar.gz /Users//.nx We also need some additional information:
– NoMachine product and version on local computer
– local Windows/Mac/Linux version (Windows XP/7/8, OS X 10.x, Ubuntu xyz, Mint x.y, etc.)
This might help:
https://www.nomachine.com/FR09I02610
This will be coming in one of the next updates.
Users can refer to the following Trouble Report which we have opened for this issue:
It could be a problem with permissions. Can you send us the output of the following command?
ls -laR /etc/NX
You can fix permissions of files in the directory /etc/NX/server/localhost by executing:
sudo chmod 644 /etc/NX/server/localhost/*
If this doesn’t work, then send us what’s in /usr/NX/var. You can send it to issues[at]nomachine.com.
Igor, I have opened a new topic for your question about disabling physical desktops.
https://www.nomachine.com/forums/forums/topic/access-to-physical-desktop-on-terminal-server
tsiganenok, we have opened a Trouble Report on the microphone issue. Use this link to track the problem.
Enabling microphone by default in the client configuration file may not work
https://www.nomachine.com/TR11K04007A Trouble Report has been opened for this topic:
https://www.nomachine.com/TR10K03927
Fixed in version 4.0.367