Forum Replies Created
-
AuthorPosts
-
Britgirl
KeymasterHi,
are you referring to the actual real monitor (server-side) which remains asleep or do you mean that in the session window it stays blank?
A possible workaround is to change the DisplayServerExtraOptions key which changes the screen grabbing method. It’s in the node.cfg file on the Mac server host. Look for the DisplayServerExtraOptions “” , remove the prepending # and change it to this: DisplayServerExtraOptions “-nosckgrab”. Restart the NoMachine server. Then try to reproduce the issue again.
August 29, 2025 at 11:31 in reply to: Can connect, see desktop, mouse and keyboard don’t work #54213Britgirl
KeymasterWhich problem exactly does it fix?
This: “-alteventapi 1” -> No input.
August 28, 2025 at 15:00 in reply to: Can connect, see desktop, mouse and keyboard don’t work #54202Britgirl
KeymasterHi, we have a patch which fixes the problem, let us know if you’d like to try it. We can send you a download link to a free edition package. The patch is scheduled for release in the next update.
August 27, 2025 at 16:26 in reply to: M2 Mac Mini Server – always software encoded, cpu up to 40% #54196Britgirl
KeymasterHi, in some cases software encoding is used if the resolution is higher than full HD. This could be what is happening. But to be sure, are you able to send us the server-side logs so we can check them? Reproduce the problem, then extract them using the instructions here: https://kb.nomachine.com/DT08U00298#1. Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Britgirl
KeymasterIt’s strange you didn’t get a notification. We’ll investigate this internally. Thanks for letting us know anyway.
Britgirl
KeymasterHi, I was about to reply to your other post which is in https://forum.nomachine.com/topic/mic-forward-from-win11-to-mint.
We looked at the attachment you submitted, but we need to see NoMachine server logs from the Ubuntu host and Player logs from the Windows 11 machine. You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298
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!
August 26, 2025 at 15:43 in reply to: Cannot connect from Mac client to Linux server, “Protocol Error” #54185Britgirl
KeymasterLogs point to a problem with Gnome, rather than NoMachine. Logs are showing this:
2919520 2919520 2025-08-25 11:02:12 205.757 NXNODE WARNING! Process '/bin/bash --norc -c exec -a - /bin/bash -c '/bin/dbus-launch --exit-with-session gnome-session --session=gnome'' with pid '2919612/2919612' finished with exit code 1 after 1,369 seconds.
NoMachine correctly tries to start a virtual display because it detects that your Linux is headless. But Gnome fails to start. Looking in the journalctl file would identify what is happening with Gnome.
journalctl -b -0 > journal.txt
Britgirl
KeymasterYou can also attach them here, yes. Bear in mind that they will be in the public domain.
Britgirl
KeymasterHi, you could try disabling UDP. You do that in Edit connection (Right click the connection in Machines )-> Configuration -> Use UDP communication for multimedia data, and uncheck the box there. Then try to connect.
If that doesn’t help, we need to see the logs from both computers. You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298#1 and #1.2.
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
August 25, 2025 at 17:18 in reply to: Cannot connect from Mac client to Linux server, “Protocol Error” #54173Britgirl
KeymasterNot received anything so far.
August 25, 2025 at 12:15 in reply to: Cannot connect from Mac client to Linux server, “Protocol Error” #54166Britgirl
KeymasterHi, thanks for the logs. The agent logs were missing, unfortunately. Can you send us the .nx directory from the user’s home on the Linux server side? Just zip up and send via email. Thanks!
August 22, 2025 at 17:41 in reply to: Cannot connect from Mac client to Linux server, “Protocol Error” #54161Britgirl
KeymasterHi, we would need to see the NoMachine server logs from the host you are connecting to and the from the Player device you are connecting from. Are you using the latest version on both sides, 9.1.24? You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298#1. Attach here or send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Britgirl
KeymasterHi, we can reproduce a similar problem, clicking on buttons in the right-hand pane in Displays, for example, has no effect, and our developers are currently investigating further. Since Tahoe is currently available as a Preview/Beta, it’s possible there could be some further updates still from the Apple developers before they release the final stable version. Thanks for reporting in any case, we will continue our investigation. If we find a workaround, we’ll submit more information here.
Britgirl
KeymasterIt would have been useful to know the version of NoMachine both sides. Are you now using 9.1.24 on both sides? It’s possible that you were encountering this bug, https://kb.nomachine.com/TR06W11427, affecting macOS, which was fixed in the latest 9.1.24. If it comes back, take the logs and a screenshot. Thanks!
Britgirl
KeymasterHi, there is a Trouble Report open on this issue: https://kb.nomachine.com/TR08W11510.
A patch is already available, lined up for the next maintenance. If you would like to test it, please reach out to us (either through your User Area or here https://www.nomachine.com/support/report-an-issue) so we can send you the right package to install on your Linux server.
-
AuthorPosts