Forum Replies Created
-
Posts
-
Thanks for this detailed information. The patch helps with the display sleep issue but not with when the computer actually goes into stand-by. We’ll continue with our investigation.
Sounds like this Trouble Report here. It seems to be affecting Big Sur only.
That FR has not been implemented yet.
Feature Requests that are released in a software update have the label “implemented” label and the version it was released in.
Hi, can you show me exactly where NoMachine is showing the wrong hostname? Attach the screenshots to your reply.
Hi, I will contact you privately with a link to download a patched package for a similar issue. After installing, if the problem is still there, logs would be useful. Check your inbox.
Which 2f method you have configured?
If you used Google Authenticator, just comment (insert a # symbol) or delete following line from the pam.d/nx file:
auth required pam_google_authenticator.so
More about 2f you can find there:
https://knowledgebase.nomachine.com/AR12L00828Can you submit your image to forum[at]nomachine[dot]com? The forums administrator can then add it here for you 🙂
Right now NoMachine doesn’t support H.265 and doesn’t support higher bit depth than 8. Adding support for HEVC decoding and encoding is currently in progress though 🙂
We tested on the fly connecting from Windows to M1 Mac (Big Sur) with the latest Thunderbird program downloaded from the Thunderbird website. There are no issues with dragging emails from one folder to another within the email program during a NoMachine session. Is it possible for you to try with another email application? Is it possible for you to try with a more recent version of Thunderbird?
Aaron, your emails with logs attached don’t appear to be reaching our server. Those messages that you sent us are coming from your email server. Please ask your admin to check in the email server logs. In any case, we no longer need the logs because we finally reproduced the black screen issue you described 😉
The link is definitely the best way to track the resolution, when the fix has been officially released to the public. Its status will change to ‘closed’.
We might be able to send out a patched version to users before it gets released to the public. If we have any news, we will update this topic 🙂
It shows that kexts were loaded, but there is no indication that the crash was nx-related. If it happens again, the NoMachine logs and stacktrace would be useful. Check our article for steps on how to gather those: https://knowledgebase.nomachine.com/DT11R00181
Windows’ native RDP can run with virtual display drivers, so it can create virtual displays mirroring the client displays and switch the user’s remote desktop session onto those virtual displays. NoMachine cannot create virtual Windows (or Mac) displays. Linux is the exception. The free version can connect you to a remote physical Linux display or a virtual one. Additionally, it’s possible to run multiple virtual displays on Linux. This is achievable when using NoMachine’s Terminal Server for Linux products.
Similar topics:
https://forums.nomachine.com/topic/are-multiple-monitors-supported-when-remote-server-has-no-monitors
https://forums.nomachine.com/topic/multiple-monitor-support-for-vms
https://forums.nomachine.com/topic/windows-multiple-displaysFurther references:
https://knowledgebase.nomachine.com/AR06S01131aaron, we won’t need the logs now, we’ve reproduced the black screen and updated an initial Trouble Report we inserted regarding Big Sur on M1