@Cheeseness @cmccullough Didn't happen on my system when upgrading from 148.0 to 148.0.2 - might be a legit bug happening under whatever circumstance instead of intention?