So, I think I fixed Wacky Leopard Bug #2, or, at least, the symptoms of it. The fix turned out to be simpler than I expected, as I simply had to reset the Keychain according to Apple’s instructions. Honestly, I’m not sure what this did or why the old keychain wouldn’t work, but in this situation, it’s not a big deal: there were few to no passwords saved on the computer. However, it is pretty strange to me that this situation happened during the bog-simple upgrade of the powerbook, which was running a virtually clean install of 10.4.10 before the upgrade.
I updated my old Powerbook [previously running Tiger] to Leopard yesterday. Simple upgrade: backed the entire drive up to the backup partition, dropped Leopard in, ran the Upgrade Mac OS X install, and walked away for an hour and a half while it chugged. It booted up fine, I installed the available software upgrades — Apple, do we really have to download all of iTunes and Quicktime every damned time? — and rebooted again.
Launched Safari, and was presented with a dialog that told me that there was no Keychain file. I told Keychain Access to verify my Keychain, and it told me that the file was missing the extension. Turns out that Safari was right, and there was no keychain file at all. I rooted around in the backup, copied the old Keychain over, and re-ran Keychain first aid; it repaired the keychain, and all seems well now.
Edit on Nov 12: I guess all isn’t fine; the laptop requires the keychain to be unlocked the first time Safari is launched, and creating a new keychain and deleting the old one didn’t seem to fix it. I’ve seen various solutions for this posted on the Apple forums and around the net, and I’ve yet to find one that fixes my exact problem, but I haven’t spent more than 15 minutes or so looking into it.
Several times an external [USB] hard drive has accidentally become disconnected without ejecting it [wheelychair + loose cord == oops], and both times I end up with two instances of my main hard drive in the Finder [but not on my desktop.] Both of them function just fine, but they don’t go away if you force quit Finder … they stick around until you reboot.
Edit: This seems to be related to the backup/restore method I use [post detailing that coming soon…] — I had a disk image with the same name as my primary hard drive mounted, and that seems to be the cause of the problem. Remounting the drive and the disk image generally fixed things, however the problem didn’t show up consistently.
My MacBook Pro has an “alleged” deep sleep mode. I say alleged, because the sleeping part of it seems to be SO DEEP that it never ever wants to wake up. I like to sleep, too, so I empathize a little bit with Lord when he never wants to wake up, but eventually, I need him to work, and have to give him a hard shake on the shoulder — and even after that, he’s still really groggy. What to do?
So here’s the situation: The laptop goes into deep sleep for some reason [last night I left it running on battery power and I fell asleep without putting it to regular sleep]. When I need to wake it up from deep sleep, I tap the power button. It shows the “grey and blurred” version of what was last displayed, with the odd little progress bar at the bottom. The progress bar grows until it disappears, and the display returns to normal. However, nothing works — I can’t raise/lower the screen brightness, move the mouse cursor, type, or do anything. It just sits there.
Am I missing some sort of magic trick that must be done here in order to fully restore my session? Do I need to wait for longer than 5 minutes or so?
What I end up doing is hard-restarting the computer. It sits for ages on the grey screen with animated circle-thing — at least 3 minutes, an eternity in today’s computing world! — and then goes into the normal boot sequence. When it finishes booting, things are as normal, but all that extra booting time doesn’t seem to mean a thing, as it’s not restoring all the contents of my RAM; I just get a normal boot.
OSX 10.4.10 on a 2.2 Ghz Intel Core 2 Duo Mac Book Pro with 4GB of RAM.
[Edit: This is my first post to Talkin’ About using Red Sweater Software’s MarsEdit 2, and it’s pretty swish so far. Looking forward to exploring it a bit more!]