Accessibility is not enabled when it is, and is when its not. #3301
Comments
|
Out of interest, is that a fresh Ventura install, or was it upgraded from an older release? I can't reproduce the issue you're seeing, but my install is several years old, so the accessibility permissions database was there before upgrading to Ventura. |
|
@cmsj Same issue here, fresh Ventura install. |
|
I wonder if it would be worth fully removing Hammerspoon from the Accessibility permissions settings? |
|
the issue persists after fully removing it and adding it again |
|
I'm reproing this as well. Was driving me absolutely batty for a bit (ala did ventura break the visual meaning of an 'on' toggle!??!"). macOS Ventura 13.1 upgraded from macOS 12 |
|
Ah-ha! Caught the messages below in the console. These occurred with the accessibility setting apparently toggled to "on". With the HS console open, I then toggled Privacy & Security > Accessibility setting for HS off and on a couple of times, reloading the config each time. After 1.5x or 2 rounds of this, the error cleared in the HS console – it started up normally. I then quit and restarted HS and everything seemed to be in the correct state: Accessibility setting "on", HS happy (both in its Preferences and in the HS console). Sorry for the "jiggle the switch until it works" workaround, but that's about all I'm going to get out of it now that it's working. |
|
I solved the issue using this guide but with Hammerspoon instead of Bartender. |
|
I am encountering this issue. Hammerspoon declares accessibility off when it's on, and visa-versa. hs.notify, hs.screen and hs.window do not work regardless of what the accessibility setting is I have tried the guide suggested by Omoeba, and a number of accessibility database resetting guides I found online to no avail. Hammerspoon is the only app using accessibility that is encountering this problem (I never had the issue with bartender) If it matters, I'm on an M1 MacBook Pro, which started out on Monterey, and was upgraded to Ventura. Right now, I'm on Ventura 13.2.1 (latest as of this comment), but the issue was present in 13.0.x as well
Additionally, I have a second mac using an intel chip that started out way back when using Catalina, and was upgraded each time a new OS came out, and it's on the latest Ventura right now. This mac is also reproducing the problem Finally, I'm on Hammerspoon 0.9.99 (latest version as of this comment, released hours ago in fact) If you guys have any requests for diagnostics, I am willing to provide |
|
I've enabled the Hammerspoon "Launch at login" option and sometimes experience this problem when restarting my computer. I'm not sure if this is source or effect, but everytime time this problem occurs, I will also get a crash report from Just in case it helps to narrow down the problem, here one of the crash reports: |
|
I just upgraded my M1 MBP from Ventura (don't recall exact version) to Sonoma (14.1.1) and all of my eventtaps stopped working. I can't recall where I saw this suggestion but I went into System Settings -> Privacy & Security -> Input Monitoring and Hammerspoon was not in the list of apps. I added it (click the I'm putting this note in this issue because whether I have Input Monitoring enabled for Hammerspoon or not, the Settings panel says "Accessibility is enabled. You're all set!", but eventtaps only work if Input Monitoring is additionally enabled. Should that panel either 1) include an additional check against |
|
(see https://openradar.appspot.com/7381305 for some context and for some perhaps-unaddressed bugginess in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When starting hammerspoon, I see the preferences and it says: WARNING! Accessibility is not enabled!. Click the button to enable it which takes you to settings. But it is already enabled. Disable it and the dialog says it is enabled. Re-enable in settings and hammerspoon updates to show it is not enabled. This is on macOS Ventura.
The text was updated successfully, but these errors were encountered: