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

[Bug]: Triggers do not persist from session to session on Sonoma / M1 #2972

Open
3 tasks done
ThoughtNozzle opened this issue Oct 3, 2023 · 4 comments
Open
3 tasks done

Comments

@ThoughtNozzle
Copy link

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

  1. Create keyboard trigger
  2. Restart machine
  3. Try keyboard trigger

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.

@mmcnl
Copy link

mmcnl commented Dec 1, 2023

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! 🙏

@rhmillernj1
Copy link

rhmillernj1 commented Jan 23, 2024

Agree same issue. ON Sonoma 14.2.1. on M2 Mac Minii. They "forget" they are active. The fastest way to have them work again is to go to the Tiggers window, and with one of them selected (they are all already checked). use the keyboard to go up or down and "touch" each row of trigger items. Now they will all work.
Screenshot 2024-01-22 at 4 21 15 PM

@jfrench206
Copy link

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.

@ThoughtNozzle
Copy link
Author

ThoughtNozzle commented Jun 7, 2024

I finally gave up and moved to Keyboard Maestro. Sorry devs, and thanks for all your work, but I need to keep up.

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

4 participants