Closed frank-lowney closed 9 years ago
I'm seeing the same issue. When trying to grant teleport.app
permissions, teleportd.app
is what gets added to the Accessibility list. Are these expected to be different?
Like frank-lowney, I am running on 10.10.2 also had an older teleport (1.1.3) previously installed.
I figured it out, at least for my machines. Delete the old pref pane, remove teleportd from the accessibility apps, then reboot. Then add the teleport app to the accessibility apps, then run teleport, and then it works.
Looks like an OS X bug. The steps to get this working are:
Why is this closed? It's not fixed. Regardless if it's an OSX bug, it's a horrible user experience. Teleport should be changed to work around this.
When I try to launch Teleport, I get an error dialog "Disabled access for assistive devices" and a panel with a button that takes me to Security & Privacy prefs. There, I supply an admin pw to unlock and make changes and set the checkmark for Teleport. I even lock the prefs back up. When I subsequently try to launch Teleport, I get the same error message and find that Teleport has been unchecked in Security & Privacy prefs. Did this several times with the same outcome. The old Teleport in System Prefs remains in place.