MacOS Tahoe – System Settings

Forum / NoMachine for Mac / MacOS Tahoe – System Settings

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #54369
    philip2112
    Participant

    Hello,
    I’ve updated a Mac to macOS Tahoe today. After connecting to the Mac running macOS Tahoe everything seems to be working fine, however mouse clicks in the macOS System Settings program don’t get fired. The click is even visually indicated but not fired, however in other programs the mouse clicks work. It seems to be isolated to the System Settings program.

    Using latest NoMachine software (9.1.24) on both Macs (caller and server) – both Macs running macOS Tahoe. Any ideas?

    Many thanks in advance,
    Philip

    #54381
    milika
    Participant

    Second this

    #54387
    Britgirl
    Keymaster

    Hi, we found a workaround, please try it and let us know.

    Edit /Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg on your Tahoe machine and add: DisplayServerExtraOptions "-oldeventapi 1". Then restart NoMachine with sudo /etc/NX/nxserver --restart

    (from https://forum.nomachine.com/topic/unable-to-edit-system-settings-on-mac#post-54165)

    #54388
    oxlabah
    Participant

    This may also be needed for other apps as I could not click on buttons to update to the latest XCode version as well.  Once I added the line specified above and restarted NoMachine it worked.

    #54392
    milika
    Participant

    Hm, shift, control alt command, now gets stuck very frequently.

    Before it was really rare.

    #54396
    milika
    Participant

    Hopefully next update fixes this, as now its borderline unusable ;(

    #54400
    Britgirl
    Keymaster

    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.

     

    #54421
    bucu
    Participant

    Hi everyone — good news! We’ve identified the cause of the issue and a fix will be included in the next NoMachine release.

    Thank you for your patience!

    #54425
    milika
    Participant

    Very Happy!!!

    #54488
    daedalus1115
    Participant

    Glad to hear this is going to be fixed in the next update.

    For those of us who followed the workaround (oldeventapi command), do we need to UNDO this workaround before updating?

    #54506
    bucu
    Participant

    @daedalus1115

    yes, if you are updating you will need to remove the workaround for the fix to work.

Viewing 11 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Please login .