Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to run skhd directly after Sequoia upgrade #371

Open
nickcorin opened this issue Oct 4, 2024 · 4 comments
Open

Unable to run skhd directly after Sequoia upgrade #371

nickcorin opened this issue Oct 4, 2024 · 4 comments

Comments

@nickcorin
Copy link

After upgrading to macOS Sequoia, I was prompted to re-grant skhd access to accessibility features. It was already enabled, and flipping the toggle off and on did nothing. To rid the prompt appearing when running skhd --start-service or skhd --restart-service, I had to:

  1. Remove the skhd entry from the list of applications which have been granted accessibility access.
  2. Run skhd --restart-service.
  3. Grant access to the new entry through following the prompt once more.

However, I still cannot just run skhd directly in my terminal. I am constantly met with a prompt to grant accessibility access to eitherskhd, or alacritty. Both of these have been granted permissions, and all has worked fine until the upgrade.

All of this is to debug and test some broken features with Sequoia, specifically to interact with yabai, and more specifically, this, which seems to have broken every single keybind I have configured in skhd.

For clarity, even with skhd running as a service, none of my keybinds are working. Assumed due to the link above.

@maturk
Copy link

maturk commented Oct 14, 2024

Funny temporary fix, I found that typing skhd -V in the terminal, and leaving the output open in the terminal returns the hot keys back.

But I can replicate the above issue, currently skhd --restart-service is completely stuck

@enweg
Copy link

enweg commented Oct 18, 2024

I had a similar problem. Doing an install from source into another location than the standard homebrew location and starting the service from Terminal worked for me. I also had to allow Accessibility services for the Terminal app though. Some key bindings for yabai (those moving windows to other spaces) still don't work but this may well be due to yabai and not skhd.

@RedemptionC
Copy link

reinstalled using brew and it worked for me.

@Oltho
Copy link

Oltho commented Jan 5, 2025

Despite having skhd, iTerm2 and Terminal enabled under Privacy & Security > Accessibility, I noticed that

  • skhd -V can be launch from both ITerm2 and Terminal
  • when running via iTerm2, skhd is working as expected
  • when running via Terminal, skhd is running but not working

I would imagine that launchd is using Terminal in the background which might be linked to the issue ?

Can somebody else replicate ?

  • macOs: Sequoia 15.2
  • skhd: 0.3.9

Current workaround is to stop skhd service:

  • skhd --stop-service (for homebrew)
  • launchctl unload ~/Library/LaunchAgents/org.nixos.skhd.plist (for nix)

Then run skhd via iTerm2:

  • skhd &

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants