-
Notifications
You must be signed in to change notification settings - Fork 286
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
[Bug]: Triggers do not persist from session to session on Sonoma / M1 #2972
Comments
I am also noticing this behavior of broken triggers after a system reboot. Currently on Sonoma 14.1.2 on M1. Toggling each keyboard shortcut off then back on from the triggers panel gets it working again, but I have many triggers so it's not ideal. Thanks to all who have made Quicksilver such a great app over the years! 🙏 |
I have the same problem after upgrading to Sonoma, with the same workaround: opening the Triggers pane and selecting my custom trigger (I only use one) will get it working again. I have to do this after every system reboot. |
I finally gave up and moved to Keyboard Maestro. Sorry devs, and thanks for all your work, but I need to keep up. |
Before submitting your bug report, please confirm you have completed the following steps
Bug description
Mac Studio M1 Ultra
128GB RAM
macOS Sonoma 14.0
QuickSilver 2.4.1
Keyboard triggers must be individually re-set after each restart or shutdown/startup.
Sadly, major Sonoma conflicts with Photoshop and Scrivener – among other apps – are forcing me to downgrade to Ventura.
I haven't had to wipe a boot drive and reinstall macOS in decades. What a mess.
Steps to reproduce
Expected behavior
Expected triggers to… well… trigger.
MacOS Version
Other
Quicksilver Version
2.4.1
Relevant Plugins
n/a
Crash Logs or Spindump
No response
Screenshots
No response
Additional info
Keyboard language: US.
The text was updated successfully, but these errors were encountered: