Disabled access for assistive devices on macOS Sonoma

[steinmacher]

Bug report

Teleport 1.3.5 on macOS 14.1.1 Sonoma shows this error when starting:

Disabled access for assistive devices
The access for assistive devices has been disabled although teleport needs this to operate. Please allow teleport and launch it again.
[OK]

As well as this window:

Accessibility Access
"teleport.app" would like to control this computer using accessibility features.
Grant access to this application in Privacy & Security settings, located in System Settings.
[Open System Settings] [Deny]

But in System Settings -> Privacy & Security -> Accessibility -> teleport is active and allowed to control the computer.

So teleport is not working on macOS Sonoma.

What you were trying to do (and why)

I'm aware Apple introduced Universal Control with macOS Monterey: https://support.apple.com/en-gb/HT212757
But this is not working with older macOS or OSX versions.
I try to connect a macOS Sonoma MacBook Pro 10,1 with an OSX 10.11.6 Mac Pro 3,1.
On the old Mac Pro 3,1 teleport is running like expected.

Step-by-step reproduction instructions

1. Start teleport on macOS Sonoma.

Environment information

Server (Mac with keyboard and pointing device)

• Device: MacBook Pro 10,1
• macOS version: macOS 14.1.1 Sonoma (OpenCore Legacy Patcher 1.2.0)
• Teleport version: 1.3.5

Client (Mac being remotely controlled)

• Device: Mac Pro 3,1
• macOS version: OSX 10.11.6
• Teleport version: 1.3.5

And vice versa.

[X25guru]

I was running Sonoma with a 13,2 iMac and a 17,1 iMac with no problems. However I spent the day yesterday backing out Sonoma on the older box back to Catalina. Th eopencare patches for Sonoma are super buggy. I didn't have problems with teleport but there's something wrong with the GEForce GPU support. Chance are the problem is related to open core. Frankly I've been surprised by how few problems I've had with teleport between El Capitan and Sonoma.

And DO NOT install 14.2.1. It bricked my wifi. Running perfectly in 14.2 and I hoped 14.2.1 would fix some gpu problems and WiFi just stopped seeing networks.

The 17,1 system runs Sonoma OK but Im wary to install new releases. Opencore is a small group and there are a lot of devices for them to test before these things are stable.

[shivshankar3578]

stop working after updating Sonoma 15.2 after restart showing disconnected black client window. I created a new user and in host Sonoma and it started working again. strange!! ??

[X25guru]

Im running OK on Sequoia 15.1.1 on 1 system and Sonoma 14.2 on the other.. If you’re running multiple subnets make sure the systems are in sync. I had one system trying to connect on my Cox subnet and another stuck on my local subnet for some reason. and I couldn’t get the master system to see the slave at all. A black client indicates it can see the system but can’t connect. Check your /var/log/system.log for clues. Also try clearing your trusted hosts

It would be nice to be able to specify the peer address so you could force it to use the best path, but there really isn’t anyone actively supporting this currently.