Forum Replies Created
-
Posts
-
We need debug logs like before. I’ll paste the link to the instructions for convenience, https://kb.nomachine.com/DT07S00243. Enable debug, reproduce, zip up and send them to forum[at]nomachine[dot]com or attach them here.
I’m not sure what “it” there would be to try beyond connecting or if you meant connecting should automatically trigger a wake up (in which case I try every time).
Sorry I updated my post to be clearer 🙂 The “it” was referring to our wake-on-lan feature. It was not clear how you were “waking up” your mac and I had assumed, erroneously, that you were referring to wake-on-lan.
For reference with regard to the waking up the mac part, there was a time when I had to use [removed] first every time, and I thought that was a mentioned as a known issue to be fixed in the future on these forums, but this was quite a while back.
You posted https://forum.nomachine.com/topic/nomachine-quit-working-after-mac-sleep-disconnect-not-blank-screen-issue, but I believe we received no logs because you couldn’t reproduce the problem? But we can start a fresh investigation now that we know the macOS version. We’ll come back to you soon.
Hi, can you both update to the latest version, 8.14 and tell us if you are still encountering issues? We fixed the following TR https://kb.nomachine.com/TR03U10784 related to the the fallback capture method which fails. We would like to eliminate the possibility that this was affecting your NoMachine set-up. If you are still having issues after the update, new logs would be useful. You can extract them from the server machine using the instructions here: https://kb.nomachine.com/DT07S00243
Attach them here or send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!Our update dialog window should certainly not be blocking access. Can you tell us the macOS version, so we can start an investigation? Also, you mentioned waking your mac up. You can also do that with NoMachine if you are on the same LAN. Have you tried the Wake-on-Lan feature?
We have been unable to reproduce this behaviour. Our own tests show that NoMachine 8.13 works correctly on Ubuntu 24.04. We recently released 8.14 and this includes a fix for a different problem on specific systems with Wayland.
https://kb.nomachine.com/TR03U10784
What we suggest is to update your NoMachine installations first. Does this solve the issue?
If not, please run
sudo /usr/NX/bin/nxserver --eglcapture yesin a terminal, logout from the account on the server and login again, or reboot the system.If there is still no change, a new set of logs would be useful in that case.
Thanks for the feedback and we’ll take it on board to improve communications 🙂
So we’ve gone now from having to use a workaround each time we start NM to a workaround each time we start MacOS. Really hope also this last hurdle will be tackled in a future update.
About this, it seems we are not the only application affected. We are currently awaiting feedback from the Apple developers to understand better why this happens and how we can mitigate it. In the meantime, we made the decision to release the fix we have, with the additional workarounds.
We are not able to reproduce this error. Can we send you debug packages? This would be the current version with additional debug enabled in the logs.
Hi, I don’t see an email from you. Maybe the email is being caught up in our filters? If they are big attachments, they might even be prevented from getting through. Can you try again? Or alternatively, we can download them whichever external service you prefer. Send us the link privately.
Hi, can you submit the following:
i) Windows version on the PC
ii) logs from the client and server sides as well. Enable debug, reproduce then gather the logs and submit. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. There are 4 steps to follow.Submit here or send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Thanks for reporting. There is a bug that we are aware of related to point 5 in your post. There is a workaround there, so please try that: https://kb.nomachine.com/TR08V11198. For the other issues you are experiencing, we’re investigating.