MacOS Tahoe – System Settings

[philip2112]

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

[milika]

Second this

[Britgirl]

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)

[oxlabah]

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.

[milika]

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

Before it was really rare.

[milika]

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

[Britgirl]

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.

 

[bucu]

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!

[milika]

Very Happy!!!

[daedalus1115]

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?

[bucu]

@daedalus1115

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

[Pesky_UK]

For those of us with remote machines having to remove the fix will cause problems.

Can the fix removal be programmed into the next update or is there a way to check the version programatically and remove if required?

 

[Pesky_UK]

Here’s a bash script that will check the version of the installed NoMachine. If it is greater than 9.1.24 (current version that required the fix above) then it will remove the fix and restart nxserver.

As always, check unknown scripts.

# Check macOS version and remove fix if required
version=$(sudo /etc/NX/nxserver --version | sed 's/NoMachine - Version //')
if [ "$(printf '%s\n' "9.1.24" "$version" | sort -V | head -n1)" != "9.1.24" ]; then
    echo "Version $version is greater than 9.1.24. Updating configuration..."
    sudo sed -i '' '/DisplayServerExtraOptions "-oldeventapi 1"/d' "/Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg"
    echo "Restarting NoMachine..."
    if ! sudo /etc/NX/nxserver --restart; then
        echo "Failed to restart NoMachine."
        exit 1
    fi
else
    echo "Version $version is not greater than 9.1.24. No changes made."
fi

 

[1412]

Just want to inform that 9.1.24 still has this issue and still needs the workaround.

[Author]

Posts