Consolation, Ulbow, Mints, T2M2, Cirrus and Taccy all updated to cope with increasing complexity and unreliability of the unified log.
Big Sur has recently introduced a bug which can change the format of log datestamps, which can break Ulbow, Mints and T2M2. Here’s how to fix it.
Diagnosing a problem on a Mac requires careful observation. In the case of kernel panics, this includes the Panic Log. Otherwise, invaluable information is in the log. If you don’t check the log, your conclusions are likely to be wrong.
It’s surprising that macOS can be slower to fully register the annual ‘spring forward’ change than you are walking round manually changing your clocks.
No longer do you need to fiddle around pre-installing preference files, and each app can now reset its preferences to the defaul
It would be much easier if the log contained entries detailing the loading of extensions. Instead, there are long gaps. This explores how you can use those in diagnosing problems.
Use the log show command, Ulbow or Consolation to browse your M1 Mac booting, and they can fail to show tens of thousands of log entries. How to work around this bug in 11.1.
Time has changed in M1 Macs, with the Mach clock ticking every 41.67 nanoseconds. This affects all log entries too, and works differently in Rosetta.
How you can write entries in the unified log which are informative, easily retrieved, and extremely simple.
What’s the difference between a crash and a panic? How can you tell what’s likely to have caused a panic?