Last night I installed the OS X 10.8.3 update on my laptop (updating from 10.8.2). This morning, upon plugging my laptop into the external Thunderbolt display as I always do, and it didn’t wake up when I opened the lid, nor when I started tapping on the external keyboard.
As I noted before, a retina MBP (or MacBook Air) that doesn’t immediately wake when you open the lid is annoying not only because it slows you down, but because Apple’s removed all the battery indicator buttons, and there’s absolutely no sign of life from a powered off (or hibernating) machine until you press the power button.
So I woke it up with the power button on the builtin keyboard, and watched it boot to the preboot login screen associated with an encrypted boot drive1, and was further annoyed that at this screen it was still ignoring the external keyboard plugged into the Thunderbolt display. Having to use the builtin keyboard for a docked laptop is suboptimal. Anyway.
When it finished booting, I fired up pmset to ask it what’s going on, first on AC power:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
And then again2 on battery:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
As posted before, I’d previously changed
to 43200 seconds on battery power, and disabled
standby entirely on AC power. Apparently the 10.8.3
upgrade reverted the former change to Apple’s new default of 4200 seconds, though it left the latter
Note that’s not quite consistent with my observation that my rMBP (bought in 2012 and shipped with
OS X 10.8) had
standby enabled by default, while my previous MBP (bought in 2010 and shipped with
OS X 10.6 and subsequently upgraded to 10.7 and then 10.8) never had
standby enabled at all.
The FileVault preboot login screen also annoys me because it’s got a pretty poor keyboard driver, and if I type my password at natural speed, it reproducibly detects one keystroke more than I intended to make. The same sequence of keystrokes is interpreted correctly by the real OS X keyboard stack. I reported this bug to Apple and they said they know and don’t care.↩
As an aside: anyone know how to get pmset to report the profile that’s not active?
pmset -greports all settings for battery when on batter, and all settings for charger/AC when plugged into AC, and I have found no way to get all settings for both profiles short of running pmset twice, and physically plugging or unplugging the power connector between runs. Note that the set mode of pmset takes an optional
-cargument to specify whether to change the values for battery, charger, or both profiles, but those aren’t honored in conjunction with