I had a miserable time updating to Seq these last couple weeks. Had an SEP kernel panic (never even heard of it till I saw the panic log). Ended up going to the Apple store and getting a DFU restore for Seq (which is all they have access to, apparently).
The issues were minor (to most I’d guess) but not for me.
Seq kept corrupting QuickSilver launcher and having a difficult time connecting to my Magic TrackPad 2. I do run Pro Tools 2024 and 2018 3.2 GHz 6-Core Intel Core i7 mini w/64G. QS is a right hand and I figured if that and the MT2 were both unhappy, it would be a drag if PT got ill too … if I want to have income.
Have made a bootable Seq ext for the few financial types that I’d like security updates for, which ended for Monty and probably have 2 years for Seq.
While the 2018 intel is “vintage”, I’m not ready to say buh bye.
Interesting. I did run into some problems with QS a while ago (mostly UI problems where colors wouldn’t display correctly and some buttons didn’t work), but recent QS releases have been fine.
Sorry for the basic questions, but are you using the current version of QS? Have you tried deleting/resetting the QS preferences?
If all else fails, Alfred is a reasonable replacement, though it can be a pain to reproduce QS prefs in Alfred.
yup. 2.5.2. the devs were following along as I was trying to find the issue.
dumped prefs, redid custom triggers from scratch.
but it would always corrupt under Seq.
I tried Alfred. Nowhere near as useful and fast as QS.
For now, I’m staying with QS under Monty on my intel.
Perhaps in a couple when I update to an M…
I am a little late replying, but think I should for completeness.
Paranoia is fully warranted.
The update to 15.5 introduced a bug which prevents validation of “external” HFS+ disks, resulting in such disks being mounted as read-only. In this case “external” means not part of the startup disk. This includes HFS+ disks mounted on the internal PCIe bus such as the Promise Pegasus R4i RAID array, as well as disks attached via USB ports.
What happens is on startup the disk fails examination by the Secure Enclave implemented on the T2 chip. The disk mounts, but is marked read-only. The only way I have found to remove this read-only designation is to rebuild and replace the directory structure using Disk Warrior.
The workaround is to restart in Recovery mode, then use Startup Security Utility to set Secure Boot to No Security. After restarting your Mac, use Disk Warrior to rebuild and replace the directory of HFS±formatted disks which have been marked read-only. This will restore the disks to full function. Unfortunately, it is necessary to leave Secure Boot set to No Security. If it is set otherwise, on restart the HFS+ disks will again become marked as read-only, necessitating repeat of the Disk Warrior rebuilds.
This bug remains in macOS 15.7.1 Build 24G231 (Intel) EFI 2092.0.0.0.0 iBridge 23.16.10350.0.0.0.