Forum Replies Created
-
Posts
-
Thank you all for your valuable feedback on applications manifesting the same behaviour.
We’ve been in contact with Apple since some time, as we’ve been tracking the beta release to prevent unexpected issues. When we noticed the problem reported on a tested beta version we were initially confident on a quick macOS fix, since we only use well documented, secure and public API to synthesize the events on the system. However when the bug was confirmed on the release candidate, which was extremely close to the official release, we knew we would disappoint our users. Unfortunately, sometimes dealing with OS vendors and new versions can be little bit hard.
The workaround we proposed, which is of course temporary, is activating an old and deprecated API for events (do you see the funny side?). It’s not perfect, we know. Rest assured we’re doing everything possible to close this issue quickly. Thank you for your patience.
Hi, we found a workaround, please try it and let us know.
Edit
/Applications/NoMachine.app/Contents/Frameworks/etc/node.cfgon your Tahoe machine and add:DisplayServerExtraOptions "-oldeventapi 1". Then restart NoMachine withsudo /etc/NX/nxserver --restart(from https://forum.nomachine.com/topic/unable-to-edit-system-settings-on-mac#post-54165)
Anyone in this thread can write to us and we will provide them with the download link of a 9.1.24 with the fix applied. The fix will be in the next maintenance release.
Er1c4rd
Let’s check first that it is the same issue. Please tell us what “nothing works” means. Is it just input (mouse and keyboard) does not work or are screen updates not working? Or is it something else? This specific issue described in this topic occurs on Linux Mint 21, what is your Linux distro and version on the NoMachine server? Can you also clarify what you mean when you write “logs me in through HyperV”
Hi, please update to v9.1.24. The corresponding TR is: https://kb.nomachine.com/TR06W11382.
Hi, you should update to the latest version both sides. It would be useful to know OS details both sides, and whether you are connecting to the physical display or a virtual display. Logs from both the player and the server would be useful. You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
https://kb.nomachine.com/DT08U00298#1.1 and #1.2.
No, it’s not officially released yet. Checking with the NoMachine Support team, I can see that you raised a Report Issue and recently received the fix in a private download. The fix will be the next upcoming release.
This was a feature we had inserted into a major new version, in this case targeting NoMachine 9, rather than as a minor. Implemented such important enterprise features in older versions is not an incentive for users to update 😉 More information about supported versions is available here: https://kb.nomachine.com/AR06P00985
We have opened a Trouble Report for this issue. You can monitor its status using the following link: https://kb.nomachine.com/TR08W11510.
Steve, if you contact us through the website at the following link, https://www.nomachine.com/support/report-an-issue, with all the details, our Support team will be able to help, including opening a ticket on your behalf if necessary. They will also be able to investigate the issue of not being able to login.
Hi Bunnicus,
sorry for the delay in coming back to you and thanks for the logs. We were able to reproduce the same problem. In the logs we found:
type=AVC msg=audit(1755101315.423:1525): avc: denied { read } for pid=1 comm="systemd" name="nxserver.service" dev="sda6" ino=5429691 scontext=system_u:system_r:init_t:s0 tcontext=unconfined_u:object_r:nx_unit_file_t:s0 tclass=file permissive=1It is reproducible when apparmor is disabled and SELinux enabled. A fix is already scheduled, not for the next release due in the next couple of weeks, but the one after that. In the meantime, the workaround is to enable AppArmour and keep SELinux disabled.