Since updating to the latest Sonoma 14.6, my shortcuts using the trigger control-option-command-b (for browsers: Safari, Vivaldi, Firefox, Arc) no longer open a command palette or work at all. In the meantime, I've added the shift key to the trigger. Awkward, but it works again.
I use that three-key jab to trigger most of my macros and all of the others work. For example, control-option-command-w triggers a palette for me to select a writing app.
Can anyone help me understand why a single keystroke trigger broke while all of the other similar ones continue to work?
Are your macros in a group? Does the group specify which apps the macros are valid in? I suspect that's the problem. Perhaps when you got Sonoma your paths to those apps changed. I recommend that you fix that by deleting the names of the apps for the group in KM and then re-issue them. This step is sometimes necessary when apps (or OS?) change.
This is my best guess. It's just a 50% chance that this will be the solution. If not, it may help if you post your macro.
It shouldn't be anything that comes "after" the KM trigger -- app paths changing or similar -- nor a Group activation/macro enablement problem because the same macros work when you add Shift to the trigger.
But you should still try KM's Interactive Help -- select one of those macros in the KM Editor, then use Help->Interactive Help -- if only for your own peace of mind.
But it's most likely the trigger isn't registering for some reason. Try deleting and re-adding (not just changing) the hot key trigger on one of those macros. Then have a look for any other utilities you've installed that might be swallowing the key combo before it gets to KM -- Better Touch Tool, Karabiner Elements, and the like -- and which may have been re-activated/changed because the OS update or their own, associated, updates.
Unfortunately, that didn't help. I deleted my shortcut for launching Safari with control-option-command-b, added a new shortcut from scratch, and it still doesn't work.
To be clear, hitting the control-option-command-b does nothing at all. No menu flash. Nothing blinks. Nothing (apparently) happens. It's just a broken trigger now.
Very confusing to me.
For the record, I've been using Macs since Mac OS 7.6 and a KM user since at least 2011. I'm not new here.
So something is stopping the key combo from getting as far as KM.
Perhaps someone else can do a before and after on the 14.6 update -- my test machine is on a MDM-enforced update delay so I can't for a few days. That'll clarify whether it's a general issue or something specific to your setup.
Also for the record, as far as I know, the only change on my system was upgrading to Sonoma 14.6. I wasn't messing with macros or installing new apps or anything like that except for installing rustscan via homebrew.
Well, my first advice was wrong, but I'm going to try a second time anyway. I recommend that you create a temporary new Group in KM to see if it could be a problem with the group. That's what I would do next. I know it's not highly likely to solve the problem, but sometimes getting confirmations about what the problem isn't ... is important too.
Get ShortcutDetective and run it. Press the offending shortcut, and the app will try to tell you which app is looking for the shortcut. This will either tell you the source of the issue, or confirm that it's within Keyboard Maestro. (It also may simply fail to work, which happens sometimes. But it's a good starting point.)
I forgot about Shortcut Detective and it did the trick! I pointed out that BusyCal was activated with that shortcut. Unfortunately for me, I had to disable its Menu in the Menu Bar. Oddly enough, the shortcut to toggle the menu is ββ₯-B, not ββ₯β-B I was using in KM. Simply clearing the shortcut wasn't enough. I had to completely disable the menu.
Thanks for the help everyone. With your aid, I found the culprit and will take that up with BusyMac.
With my new clue in hand, further investigation uncovered a new "feature" in BusyCal. After tracking that down and disabling, everything is back to normal for me.