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

ThoughtNozzle commented 9 months ago

Before submitting your bug report, please confirm you have completed the following steps

[X] Searched the issue is not already listed in the Issue List (I've searched it)
[X] Searched in the Quicksilver Users' Group for questions relating to tech support.
[X] Downloaded the latest version of Quicksilver for your system and confirmed the issue still persists.

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

Create keyboard trigger
Restart machine
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 commented 7 months ago

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 commented 5 months ago

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.

jfrench206 commented 4 weeks ago

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 commented 4 weeks ago

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

quicksilver / Quicksilver