Forum Replies Created
-
Posts
-
Hi! I’m sorry for the delay, I was sure your post was handled but… can I say my brain is burning because it’s too hot? 😀
By the way, kidding aside, your problem seems to be caused by a Wacom driver, however I didn’t understand if you started reproducing it after updating to v9 or if also the previous installed version was affected. It should definitely be a Wacom problem so any NoMachine version should make no difference. Could you temporarily uninstall it and confirm that the NoMachine client starts correctly, please?
Hi. You don’t need to do anything when the IP changes, the server automatically reconfigures and notifies the new listening address. If you’ve physical access to the server you can start the NoMachine player, enter Settings > Server > Status and click the “Start the server” link. If you want to do it through a terminal, run the command
sudo /etc/NX/nxserver --startup.Hey, I’m sorry for not writing you back! I’ve received your stackdumps and devs are working on trying to reproduce your issue, so far without luck. I’ll update the thread as soon as they tell me how to proceed.
Thank you for sharing the logs, we’re analyzing them. We’d also like to verify if the blank screen and following disconnection was caused by a segmentation fault. Could you check the folders
~/Library/Logs/DiagnosticReports
/Library/Logs/DiagnosticReportsand send any stackdump file with prefix nxnode, please? No need to install again version 9, if the IPS files exist they’ll still be there.
It’s me again. Can you please save server side logs and send them to forum[at]nomachine[dot]com? You can do that by opening the NoMachine client > Settings > Server > Security > Take logs (below in the panel) and select where to save the file. We’d like to identify some operational parameters that are common in the issue I mentioned in my previous post.
Would you like to install a package implementing a potential fix for your problem? We’d just need to know what is the product you installed on the server machine (if you’re not sure about it, open NoMachine client > Settings > Server > Updates).
What type of Mac hardware do you’ve on server side (macbook, iMac, etc) and what processor does it use (Intel, Silicon)? We’ve already started some internal tests, but the more we know the better it is. I’ll keep you updated.
Hi. Can you please share a few details about your client and server OS version and working environment? We’re not aware of issues so we’d need to run some tests on your specific configuration.
Hey there. We’ve found the issue and documented also a workaround:
https://kb.nomachine.com/TR06W11407
The fix will be included in the next maintenance which is to be released shortly.
@thibaut the client mode being reverted could be caused by a client process overwriting your change, so if you want to test that, be sure to close all running nxplayer instances.
Additionally can you confirm if, like @wernermaes, you’re using the SSH protocol to connect and agent forwarding to authenticate?
We’re still in process of investigating the behaviour, but of course it is not expected so there is nothing wrong on your side.
Could you please export client side logs (Settings > Security > Take logs) and send them to forum[at]nomachine[dot]com? We’re like to address this issue quickly, any hints will be helpful.
Hi. We didn’t find issues with the greeting message. Could you please confirm name and version of your Linux distribution and Desktop Environment on the server?
If you press ESC while you’re viewing the remote desktop, you’re just sending the key to the remote active application so it won’t have any effect on the client (with or without keyboard grabbing).
Next time you use NoMachine you could get a couple of screenshots to show what you’re trying to do. If you don’t want to publish them here, you can send them at forum[at]nomachine[dot]com.