3 ms·
It didn't happen again in the /next release/, it happened when upgrading from an older release to the current one.
by nikanj 9y ago
It didn't happen again in the /next release/, it happened when upgrading from an older release to the current one.
- givinguflac 9y agoSeriously. It’s shitty, but rebooting isn’t the end of the world. The problem is they don’t force a reboot with the fix. Now they just need to roll a new 10.13.1 with the fix and force a reboot with the standalone patch, problem solved.