- This topic has 24 replies, 7 voices, and was last updated 9 months ago by
.
-
Posts
-
Yeah, kind of have to go in with Britgirl on this one: with all due respect to the frustrations of daclint01; the objective is to get this thing fixed so we can be on the most current release and that it just works! We will get there, even if it takes sending a dozen logs. I realize that we are the debugging universe, compensated via a free product that is essentially fully functional, which of course assists to perfect the commercial product as well. I don’t mind being the testing ground given the supreme responsiveness of the NM support team.
Brian
@BerndG When I find that restart via CLI doesn’t help, I also find that connecting via [removed] and logging into the desktop does help. IOW, instead of using Finder to terminate and restart NoMachine (stopping and restarting the service from the NoMachine UI also previously worked for me), you may simply need to connect to NoMachine while (or just before) the desktop is unlocked using [removed].
@britgirl: I did as requested and sent the log.
@brian, nxmac : can you reproduce the strange behavior that happened when I switched the log level as described below? :1. I switched to log level 9 and hit “restart server” in the GUI.
– I tried to reproduce, but was not able to anymore. Killing the connection and connect again was possible without any issue.
2. I switched back to log level 6 and hit “restart server”.
– Voila – the problem was back again.
3. I switched to level 9 the second and restarted the server
– Reconnecting was possible 2-3 time without problem, then the problem appeared but in difference to log level 6, the white screen got away after 20-30 seconds and I saw my remote screen. There was no “connection was reset ” message anymore.
Best
Bernd
.. sorry. got an answer an few minutes later
The problem does not exist as long as I connect via [removed] at the same time! It will appear again once I am not connected with a [removed] Server additionally…
Well, I hope the logs will help.
Therefore, workaround is still using [removed]-Connection to help NX-connection 😉
Thanks to everyone’s comments and the logs that have come in (BerndG, nxmac, Brian). We’ll be taking a look and will come back to you if we need anything else. We’ve also reproduced the issue since I last wrote and will compare our findings with what info and log information you have all submitted, so that a fix can be found and released as soon as possible, and we can eliminate the need for …. ehem 🙂
Here is the Trouble Report documenting the issue: https://kb.nomachine.com/TR01W11266
The temporary workaround is to prevent the monitor from entering the sleep mode: open System Settings -> Lock Screen and set: ‘Turn display off when inactive’ to ‘never’. We have a patch already lined up for release and we’ve scheduled a release for this week.
This works! Please note a reboot of the computer hosting the server is required though!
Thanks!!
Brian
And an additional note relating to an earlier post: attempting to work around this bug by downloading an earlier version of NM did not help at all. I downloaded and reinstalled the previous build (8.13.1 – 7/29/2024) to see if it would solve the problem and it did not. More than anything else I’m just curious what caused this to all of a sudden break. If it’s not a NM-internal proprietary secret my curiousity is killing me to know!
This topic was marked as solved, you can't post.