Forum Replies Created
-
Posts
-
Hi, the logs you sent us on July 22 were not complete. Please follow my instructions above for the logs and also try the suggestion I wrote. To get the logs, reproduce the problem, then go to server settings security panel and click Take logs.
The logs can be attached here and they will remain public, or you can send them to our email address forum[at]nomachine[dot]com. Logs may contain IP addresses, usernames and computer names of the affected user sessions. It is possible to blank out the sensitive information before submitting for analysis. Thanks
Hi, thanks for those. Logs confirm an already known issue: https://kb.nomachine.com/TR02X11706 which also includes a temporary workaround. The fix is going to be included in NoMachine 10, coming soon.
Are these rootless sessions? We aren’t aware of similar issues and it would need a thorough investigation, something that is probably best done through the traditional support channel. It would be wise to update to a more recent version of NoMachine 8 first, if updating to version 9 is not possible, and see if that helps.
Can you send us the full set of logs taken from the host you are connecting to? Go to Settings > Server Settings > Security, scroll down and Take logs. Send us the whole file. You can send it to forum[at]nomachine[dot]com or attach here. If you are sending it via email, please use the topic of this title as the subject of your email. Thanks!
Hi, we aren’t aware of issues with with ScreenCaptureKit on Tahoe.
Logs from the macOS server would also be useful. Go to Server settings > Security > scroll down and Take logs.You could also try adding the -nosckgrab parameter in the NoMachine node.cfg file on the server side. In /Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg, append
DisplayServerExtraOptions "-nosckgrab", save, then restart the nxserver (Server settings > Status > Restart). Does this make any difference?Hi, we are aware of this problem and have already opened a Trouble Report. Please use this link to track its status: https://kb.nomachine.com/TR07X11889.
Users encountering this issue, please take a look at the topic submitted here for a possible solution: https://forum.nomachine.com/topic/video-tearing-glitching-caused-by-nvidia-driver
Investigations that were done did not allow us to pinpoint specific system variables which are affecting the NoMachine UI. However, some improvements recently made could help, and we invite you to update to the latest version. If you are still encountering the same issue, please follow the instructions that were recently posted for a similar topic here: https://forum.nomachine.com/topic/nomachine-ui-stops-working-enabling-linux-for-windows#post-55834
And then reach out to us through the website, so we can continue through our traditional support channel. You can contact us using the following email address issues[at]nomachine[dot]com.
Investigations that were done did not allow us to pinpoint specific system variables which are affecting the NoMachine UI. However, some improvements recently made could help, and we invite you to update to the latest version. If you are still encountering the same issue, please follow the instructions that were recently posted for a similar topic here: https://forum.nomachine.com/topic/nomachine-ui-stops-working-enabling-linux-for-windows#post-55834
And then reach out to us through the website, so we can continue through our traditional support channel. You can contact us using the following email address issues[at]nomachine[dot]com.
Hi, NoMachine disconnects when the Mac goes into hibernation, and then reconnects when it wakes up. What you are seeing is the correct behaviour even though you didn’t physically disconnect and reconnect NoMachine.
Thanks for submitting the logs, they confirm what I wrote previously:
Info: Remote desktop resized to 3840×1200.
Info: Session window surface configured.
Info: Changing display mode to ‘viewport’.Upon reconnection, NoMachine tries to apply the previous resolution before it disconnected, but can’t because the macOS desktop (not NoMachine) decided the resolution should be 3840×1200. So it switches to ‘viewport’ because the client has a smaller available resolution.
Hi, we’ve reproduced this and opened a Trouble Report here: https://kb.nomachine.com/TR07X11880. For the time-being you should use a different key for switching the layout (or a combination). Please use the link to keep track of the TR’s status. Thanks for reporting 🙂