• Explore the magic and the mystery!



  • The Mac OS 10.5.5 Update: Take Two Pills and Call Me in the Morning

    September 16th, 2008

    Around the world, millions of Mac users have seen Apple’s latest Leopard update appear in their Software Update preference panes. The vast majority of these folks will simply accept the installation, enter their passwords and click Restart at the appropriate time. They will then get back to work after their Mac has completed the restart process, go off for a meal, or go back to sleep, depending on when the update occurs.

    A smaller number of people are eager visitors to certain Mac troubleshooting sites, best unnamed, and will follow a silly set of voodoo procedures to make sure that the update doesn’t somehow bite them or, at worse, consume their Macs in flames.

    Well, maybe I’m exaggerating, but it seems to me that Apple has tested all of their downloadable updates to install in the standard fashion, without calling upon ancient deities or throwing tea leaves in a prescribed direction, and everything usually works properly. So you wonder why some people feel it’s necessary to be excessively paranoid about installing such things.

    Sure Apple has made its share of mistakes. Sometimes the process of fixing one bug only reveals another, one that has to be addressed in a subsequent update. At other times, people who have done a fair amount of system tweaks will encounter anomalies and need to probably do a clean reinstallation of their Mac OS to get things to behave properly. Or, at the very least, remove the tweaks.

    At one time, I was inclined to ask you to observe excessive caution and take such things far too seriously than necessary. Now I’m inclined to be far more casual about such matters, and, yes, I do depend heavily on my Macs to get my work done. I’d be in serious trouble without them.

    This rather lengthy introduction takes me to the latest Leopard update, predictably dubbed 10.5.5. According to Apple’s support document, this update contains 34 different fixes and enhancements, but each item may reflect a number of changes, perhaps in the hundreds. There are, for example, over two dozen security fixes addressing an unusually wide range of matters, including a further fix to the infamous DNS bug discovered a few months back. That’s the one, if exploited, would allow an Internet criminal to silently redirect your browser to a bogus site and then do all sorts of nasty things.

    A prior fix, part of a recent security update, supposedly resolved the issue with Mac OS X Server but not with the “client” version of Leopard. Now that’s evidently addressed too, though, to be fair about the whole thing, I don’t know of anyone, anywhere, who was actually affected by this particular issue.

    In fact, that takes us to the larger question. Throughout 2008, Apple has fixed dozens and dozens of security issues, any one of which may, in theory, be exploited at one time or another. As a practical matter, they are potentially serious, but I’ve yet to see a confirmed report that Mac users have succumbed. In large part, the issues involved affect the open source applications that Apple bundles with Mac OS X, so many of the fixes come from third parties, and it’s only a matter of building them into the OS.

    After all was said and done, I did run the 10.5.5 update, sans the voodoo, on three different early 2008 Macs, including a MacBook, a 17-inch MacBook Pro and a Mac Pro. In each case, the upgrades went flawlessly. After the restart, things settled down quite nicely.

    That doesn’t mean you should be cavalier about such things. There are a few minor cautionary notes I’d offer up for any update that impacts the operating system. First and foremost, keep current backups. Thousands of files are being updated or replaced, and if something goes wrong during this process, you would certainly want to be able to return to what you had previously.

    The other considerations are of lesser importance. While you don’t have to, I generally quit all running applications. It’s also rumored that the Mac OS X installer may not be able to replace some of the bundled applications, such as Mail and Safari, if they are moved from the standard Applications folder. In practice, the installer ought to be smart enough, by now, to figure that out and find them anyway. But just think twice before you switch things around.

    Some of you may prefer to go to Apple’s site and get the Combo updates, which are much larger, but cover everything that was changed since the original 10.5 release. If you’ve missed 10.5.4, that’s what you’ll get anyway. Otherwise, there’s no need unless you encounter troublesome issues after the update is applied.

    If you are still concerned, let a few days pass for things to settle down before you run the updates. That way, you can see if any genuine show-stoppers emerge in the online chatter, but don’t take scattered complaints that don’t have verification seriously. Regardless, nothing forces you to let Software Update do its thing the first time it prompts you. The updates will still be there next time you check.

    And one more thing: If you read about any especially unusual procedures about handling such updates at a Mac troubleshooting site, just ignore the advice. You’ll save yourself lots of aggravation.



    Share
    | Print This Post Print This Post

    29 Responses to “The Mac OS 10.5.5 Update: Take Two Pills and Call Me in the Morning”

    1. John Fallon says:

      With Leopard, Apple applies major updates that touch operating system files only during the shutdown process, when they can be sure no user action or process will be affecting system files. Seems to me reports of major problems after updates, even on that one site, have been greatly reduced since that change.

      At some point, the fact that there were firewire drive problems 5 years ago just doesn’t matter anymore.

    2. With Leopard, Apple applies major updates that touch operating system files only during the shutdown process, when they can be sure no user action or process will be affecting system files. Seems to me reports of major problems after updates, even on that one site, have been greatly reduced since that change.

      At some point, the fact that there were firewire drive problems 5 years ago just doesn’t matter anymore.

      As I said, I just added a note of caution. However, the troubleshooting sites will always find something, even if two people on the planet had the problem.

      Peace,
      Gene

    3. Adam says:

      I noticed that the site we all are thinking of actually did something more or less responsible in their coverage of 10.5.5 upgrade “issues”. They are including phrases such as “some users have experienced” “for one user” and “these problems have only been reported by one or two individuals”. Quite an improvement from the old “the update causes” language we have been reading. Having said that, they still recommend the voodoo, and the coverage is still somewhat suspect given the history, but it is not as alarming as it had been.

      Before it was bought (by CNET I think?) this site was an invaluable resource for troubleshooting. Hopefully it is now on the road to recovery. I would like to be able to recommend it again rather than providing as much free support to friends and family as I do. Time will tell, perhaps a lot of time.

      Adam

    4. Now that CNET has been acquired by CBS, you’d hope they would raise their standards. But even “for one user” is insignificant and shouldn’t even be mentioned, except to put it in proper perspective. It’s fine for most people, but one user’s hair fell out as soon as he hit the Restart button. 😀

      Peace,
      Gene

    5. John Fallon says:

      Of course, just after I post the comment above, I did the incremental 10.5.5 update process on my Intel Mini and it failed. It left my machine rebooting in 10.5.4 after telling me it had failed. Applying the combo update worked fine.

    6. Of course, just after I post the comment above, I did the incremental 10.5.5 update process on my Intel Mini and it failed. It left my machine rebooting in 10.5.4 after telling me it had failed. Applying the combo update worked fine.

      But it wasn’t a self-fulfilling prophecy. 🙂

      Peace,
      Gene

    7. auramac says:

      “Logic” works in mysterious ways. As a Mac tech support specialist in my local school district, I was walking in the hallway by a teacher’s classroon- at that particular moment, her hard drive failed. Although her eyes knew better, she was positive that I was responsible for her computer’s failing because I was the only one in the vicinity and these things just don’t happen by themselves.

      Needless to say, when I did actually enter the room and replace and restore the hard drive, I received the credit as well as the blame.

    8. Andrew says:

      No trouble here on three separate MacBooks.

    9. Dave says:

      I had huge problems shortly after my install of 10.5.5 on about 20 systems. (Yes, I was in a hurry to eradicate those many bugs too!) My local Internet service had a meltdown just after I finished the upgrades. Within an hour I had three systems lockup and go down. I “assumed” the issue where several computers showed blue screens on restart, and such were all related to 10.5.5. Most applications on other computers ran at a snails pace.

      For awhile I blamed FileMaker as a source for this issue. They helped me see that I was wrong on that assumption too. The loss of web services resulted in a leap of communications as computers tried to synch with one another… and my LAN became overloaded. After a several hours of getting pretty ticked about 10.5.5 and FileMaker I received a call from FM. They helped me discover the issue—my own local network traffic.

      Shutdown network. Restart network. All is well. Had I flamed the fix-it sites with my issues others would have assumed that 10.5.5 was dead on arrival. Sometimes we all need to learn to breathe.

      Thanks FileMaker for your excellent support staff.

    10. Jim says:

      Loved para. 3. You’re inspired. However, I was injected with 500cc of paranoia at birth and since it’s action is viral, all hope is lost. 😉
      All you little kiddies out there, pay very close attention to Gene; he’s a genius.

      As always, Gene, excellent stuff! Thanks.

    11. Roger Mercer says:

      As soon as I installed 10.5.5 and rebooted, I noticed that I began to get an outbreak of zits. I went and took a shower and my hair fell out.

      I went to get a cold drink, and my refrigerator was making strange, gulping noises.

      When I closed the door, the refrigerator burst into flames.

      After I put out the fire, I tried to go to buy a new one and my truck wouldn’t start.

      So I began walking and I stepped on a pop-top and blew out a flip-flop.

      I tried to call the hospital, but my iPhone had frozen.

      I’d say 10.5.5 is a disaster. I’m still trying to figure out how it bricked my phone.

    12. adrian says:

      Isn’t is supposed to be “Take two aspirin and call me in the morning?” 🙂

    13. Isn’t is supposed to be “Take two aspirin and call me in the morning?” 🙂

      Some prefer Tylenol. 🙂

      Peace,
      Gene

    14. Mark says:

      I noticed that the site we all are thinking of actually did something more or less responsible in their coverage of 10.5.5 upgrade “issues”. They are including phrases such as “some users have experienced” “for one user” and “these problems have only been reported by one or two individuals”. Quite an improvement from the old “the update causes” language we have been reading. Having said that, they still recommend the voodoo, and the coverage is still somewhat suspect given the history, but it is not as alarming as it had been.

      Before it was bought (by CNET I think?) this site was an invaluable resource for troubleshooting. Hopefully it is now on the road to recovery. I would like to be able to recommend it again rather than providing as much free support to friends and family as I do. Time will tell, perhaps a lot of time.

      Adam

      Yes, in theory an improvement. But read closely when they do this: Recently several of these reports have started with “Some users have experienced…”, but then only ONE user report is referenced. Bah.

      And as Gene has noted here numerous times, it seems clear that many of these system update “problems” are experienced by people who’ve messed around with their systems, moving applications to other folders after installation, using dubious 3rd-party hacks, and so on. This has been true for years: “…When I removed application X, or input manager Y, the problem disappeared.” But we almost never hear, subsequently, “My apologies, so the 10.x.x update isn’t the spawn of the devil after all; it was my fault, sorry I wasted your time with this problem report”, from either that user OR “that site”.

      Of course, there *are* users who might experience genuine problems in the updating process for other reasons. But as Dave’s experience (recounted in his message above) suggests, even then there might not be something inherent wrong *with the update itself*. Many users (including, btw, my [82 year old!] mom) update their Macs every time by letting Software update handle it. And then they go about their business with no issues.

      My thinking is that without these overly hysterical (however now more accurately qualified…) “reports”, that site wouldn’t have anything to say, little reason to exist. The site used to be so very helpful, but no longer. Apart from the ridiculous voodoo they recommend for system updates, when the answer to almost every problem is to repair permissions and/or trash a .plist file, there’s little “there” there anymore.

      mb

    15. auramac says:

      I had absolutely no problems with the 10.5.5 update, except for one little thing:

      Bill Gates and Jerry Seinfeld literally crashed through my monitor and went diving into my closet looking for shoes. Suddenly, the door to my apartment swung open, and in slid Michael Richards, heading in the same direction. He screamed the “N” (Nerd) word at Gates, and I’d had enough. I threw them all out, took two aspirins and went to sleep.

    16. Arnold Ziffel says:

      Have upgraded a Mac Pro and MacBook Pro, and everything is fine in my wallow.

    17. Annette says:

      Has anyone updated their MacBook to 10.5.5. and external display (attached via mini DVI) is still detected?

      My MacBook (and several others are repeating same issue) will not detect external displays (using mini DVI) after updating to 10.5.5.

    18. Adam says:

      Has anyone updated their MacBook to 10.5.5. and external display (attached via mini DVI) is still detected?

      My MacBook (and several others are repeating same issue) will not detect external displays (using mini DVI) after updating to 10.5.5.

      Yes, Annette, this is the exact set up I have at work. No trouble whatsoever.

    19. MichaelT says:

      Isn’t is supposed to be “Take two aspirin and call me in the morning?” 🙂

      Some prefer Tylenol. 🙂

      Peace,
      Gene

      I thought it was supposed to be “Take two chill pills…”

    20. DBL says:

      Listen, no voodoo is required. Just wait a few days before installing any major update from Apple. (Or any other manufacturer.) All of the truly serious problems that have occurred with Apple updates have all been fixed within days, so just *wait* days, and you’re fine.

      If you install a major update the day that it’s released, you are taking a huge risk with your workflow, and one day you will pay for it and the price will be steep enough that you will have wished you had employed different habits the entire time. The risk/reward ratio will seem quite different then, won’t it? It’s happened to people I know.

      If waiting a few days is so onerous to you and you have to be *that* bleeding edge about this, then you basically deserve what you get. (Not to remove any blame, however, from Apple.)

    21. Andrew says:

      Has anyone updated their MacBook to 10.5.5. and external display (attached via mini DVI) is still detected?

      My MacBook (and several others are repeating same issue) will not detect external displays (using mini DVI) after updating to 10.5.5.

      I’m doing the same on one of my MacBooks (connected to NEC 20″ WSXGA+) and no issues whatsoever. The MacBook was even driving the display in lid-closed mode when I installed the update, and it rebooted into 10.5.5 almost without issue.

      I say almost, because when the computer restarted it was dog-slow for about 20 minutes, and then magically sped itself up again. My guess is Spotlight re-indexing, though I cannot be sure as my other two MacBooks weren’t slow at all after the update. Those two have 80GB drives (60GB partitioned for OS X) while my main workhorse machine with the external monitor has a 320GB drive 100% of which is allocated to OS X.

      So far I’ve noticed no real differences in the new system, but I call that a good thing.

    22. Peter Trondsen says:

      Hi Gene,
      For some reason, with 10.5.5, I followed MacFixit’s advice about booting in to Safe Mode and then applying the update. I assume, they tell you to do this, because Safe Mode forces a directory check on startup. Anyway, I have an early 2008 Alum iMac, and after running the update (in Safe Mode) and rebooting, my computer seemed a bit sluggish and this weird digital artifact filled the screen. Gray colored with other colors in it. Just changing the monitor resolution or moving a window around got rid it. However, it would reappear after every restart. Even after, running Cocktail and repairing the permissions and clearing the caches. One article mentioned copying the old ATI Extensions from 10.5.4, that didn’t work, just prevented my machine from booting. So….I decided to back out of 10.5.5, and performed an Archive and Install and update to 10.5.4.

      I’m not sure that Safe Mode was directly related to this, but maybe I’ll try 10.5.5 again at some point, or 10.5.6.

      Thanks,
      Peter

    23. habeeb says:

      I used Software Update to update my MacBook Pro from 10.5.4 to 10.5.5. At the time, I had a burned disc in the drive. During the update, the disc was automatically ejected, the software installed, and the system restarted. Everything seems to be fine.

      However, now my SuperDrive won’t accept the burned disc that was working fine just prior to the update. I insert the disc, it spins for a while and makes some noises, then it spits it out. It won’t mount at all. I haven’t tested other discs yet, but regardless, this is complete BS.

    24. johnf says:

      Well… I don’t know if it’s a 10.5.5 issue, but it happened not long after updating. I moved a folder out of the System library to fix a sluggish internet (crazy slow on my machine but not on my wife’s, so it was me)… rebooted… and when that didn’t fix anything, I moved it back and booted again.

      Now my MB Pro can’t even see the Airport card… or bluetooth… or my TimeMachine backups… or my network preference pane, one of the tabs in the energy saver pane, or my local host name (says Applejack). And, though I don’t quite understand what it means, I’ve got the “custom access” note on permissions on a lot of my folders.

      I’m not sure if I have to suffer through a total Erase and Install or what..

      Anybody here found fixes not mentioned elsewhere?

    25. adam says:

      @ johnf

      As someone who used to get paid to fix such things, I strongly suspect that you had a “silent” problem before the update. What exactly exacerbated it, I do not know. At this point I would boot from your OS DVD and on the Installer “Options” section I would do an Archive and Install. This will replace your OS but not your data files. If you still have problems, then it is almost certainly bad data and/or preferences. Back up your data, wipe out the drive, start again. I know you have Time Machine, but this is an unusual problem and to be safe, back up again if you can.

      Removing a folder from the System Library is big BAD mojo the likes of which we never did at the Genius Bar. You can sometimes get away with removing files, but a folder? Not good. Frankly, if things were this bad, we would just reinstall. When you do this you are like a pre-med student pulling out organs. You know something’s wrong, you think you know where but you are messing around with the deep stuff and unless you can re-build it from scratch you may not get the repair finished in time to save the patient.

      Although it’s not likely, the system could have gotten sufficiently hosed when it tried to operate without that folder to cause some of your current issues. Unless you really really, really know what you are doing, DON’T muck with the folder structure of /Library, /System, or /System/Library!

      Good Luck

      Adam

    26. johnf says:

      Adam,

      Thanks… I’m actually happily typing this to you on my connected computer. I couldn’t wait for feedback (impatient!) So after noticing that a new account had all the same problems, I figured it had to be the core install of the system that I’d corrupted and I went ahead and did an Archive and Install of my own. So I was happy to see you offer the same advice in this, one of the first emails alerts/online posts I’ve been able to download in a week.

      I’m now about to commence with the Software Updates, since my Leopard disk is 10.5.1. But as a precaution, I’m only doing the combo update to 10.5.4. I’ve heard some bad things about 10.5.5. Or do you think that’s not necc. caution?

      Also, just for future reference, is there any value to an Erase and Install? And if so, is there any easy way to transfer installed programs back without dragging out a pile of DVDs and sitting there for hours? I’ve seen people suggest migrating from a disk image to the clean installation. But I would think that just means bringing back in all the preferences, etc. you were trying to get away from in the first place.

      Thanks again for the help.

      John

    27. johnf says:

      P.S. What’s the comment plugin used here? I love it.

    28. P.S. What’s the comment plugin used here? I love it.

      More than one. 🙂

      WP Ajax Edit Comments: Let’s you edit your comments in place, with instant/Ajax refresh.

      iF AJAX Comments For WordPress: This provides the instant display of your submitted comments using Ajax refresh, rather than forcing a reload of the page, and the interactive preview.

      I highly recommend both. Yes, having a fast multicore dedicated server and a PHP caching accelerator doesn’t hurt.

      Peace,
      Gene

    29. Adam says:

      I don’t know of any reason not to use the 10.5.5 update, but do as you please.

      There are 2 things I use Erase and Install for :
      1) when Archive fails
      2) for a major OS upgrade (10.4 to 10.5 for example) when I want to “clean house”.

      As for bringing things back from a clone, that is usually fine. Your preferences reside in the various Library directories. Copying the Apps back, and your documents, is usually just fine. When it comes to the Library, be selective. Copy over your Mail messages, but not the Prefs for example.

      Glad it worked out!

    Leave Your Comment