Security Update 2005-007 (#2): Proper updating procedure; Problems with startup, reverting; 64-bit apps broken; more
Security Update 2005-007 (#2): Proper updating procedure; Problems with startup, reverting; 64-bit apps broken; more
Proper updating procedure Many issues that users experience after installing a major system revision like Security Update 2005-007 (which affects various key components of the Mac OS X architecture) are resultant of pre-existing conditions including corrupt cache files, disk directory/permission errors and more.
That said, there are a few precautions you can observe while updating that will lessen your chances of experiencing the aforementioned issues.
First, as noted yesterday and generally stated for major Mac OS X updates, avoid performing any other operations (in Mac OS X or third-party applications) while the update process is occurring. In addition, before installing this security update, make sure all Apple-installed applications and utilities are in their original locations. Moving one of these applications to a different location on your hard drive can lead to an incomplete update. Also, disconnect any FireWire/USB devices before applying Mac OS X 10.4.2, then re-connect the devices one by one after the update process is complete and the system has restarted.
Also, repair permissions before and after applying the update (using Apple's Disk Utility, located in Applications/Utilities). If you'd like to go one step further, you can use the following process to more effectively repair permissions on your startup volume:
- First create a backup of your startup volume.
- Drag the folder com.apple.SoftwareUpdate located in /Library/Caches (the Library folder at the root level of your hard drive) to the trash.
- Download the standalone version of Security Update 2005-007 and save it for later.
- Startup (restart) your Mac using a drive other than your usual startup drive as the boot volume. This can include an eDrive created by TechTool Pro, or better, an external FireWire or USB 2.0 drive. Make sure that this drive includes a copy of Disk Utility (which can simply be copied from your normal startup volume).
- Launch Disk Utility from the temporary startup drive. Perform a "Repair Disk" operation on your normal startup drive (which should now appear as another mounted volume in the Finder)
- Again restart, this time booting from your normal startup volume, while holding the "Shift" key to boot in Safe Mode.
- Apply Security Update 2005-007 and restart when prompted, this time without holding the "Shift" key.
- Again, repair permissions using Disk Utility
Problems with startup after updating -- reverting to before the update A number of users report issues with startup after applying Security Update 2005-007, which can usually be avoided by using the aforementioned recommended upgrade process.
If you experience startup errors, first try starting in Safe mode (hold the "Shift" key while you startup). Failing that, you may need to startup from an alternative boot volume (such as your Mac OS X Panther or Tiger CD), then use the Mac OS X instructions contained in this tutorial to perform an Archive and Install and reversion process, bringing your startup volume to a state prior to application of the security update.
MacFixIt reader Monika Hickey writs:
"Updating my powermac G5 dual 1.8, OS 10.3.9 to this security update produced a gray screen at startup with just a cursor showing. Tried 3 times and the same result, however it seems to boot up because I can see it on my network from the G4. Apple wants $49 to 'fix' it."
Jerry Walz writes:
"After installing my desktop G4 starts up in the Open Firmware mode. I can't, don't know how, to get back to GUI mode."
64-bit application support broken Wolfram Research, makers of the Mathematica package, report that Security Update 2005-007 prevents any 64-bit-native application from running. The company says this means that Mathematica 5.2 will not run on any G5 system if it has been revised with the latest Security Update.
The issue has been confirmed by several readers.
Dale Brugh writes:
"Wolfram's Mathematica 5.2 does not work on a G5 with security update 2005-007 installed. The user interface will start, but no computations will run. I have confirmed this on two dual 2.0 GHz G5 machines."
A note from Wolfram reads:
"This problem was discovered by our testing procedures a few hours ago, and Apple has now assured us that they have stopped automatic distribution of Security Update 2005-007 at this time.
"If you did not install Security Update 2005-007, then you will not be affected. If your Mathematica 5.2 successfully launches and performs any computation (such as 2 2), then this also means that you have not been affected.
"If you have been affected, then Mathematica 5.2 will generate a MathLink error when you try to do any computation with it. (If you run MathKernel directly from the command line, it will crash at startup.)
"Apple has informed us that there is no workaround for this problem. Apple is investigating the problem at high priority, and intends to distribute a new Security Update in the very near future. This update will correct the problem and allow Mathematica to run successfully.
"To run Mathematica 5.2 today, you must temporarily disable its 64-bit capabilities. You can do this by running the following commands in the Terminal:
- cd /Applications/Mathematica 5.2.app/Contents/MacOS
- cp MathKernel MathKernel.bak
- lipo MathKernel.bak -remove ppc64 -output MathKernel
"Note that when Apple has made the corrected Security Update available, and you have installed it, you must reverse the procedure above by running the following commands:
- cd /Applications/Mathematica 5.2.app/Contents/MacOS
- mv MathKernel.bak MathKernel
"If you do not do run these commands, Mathematica will not operate in optimized native 64-bit mode.
"We regret the inconvenience caused by this problem, and hope that as soon as Apple has corrected the problem you will continue to enjoy the outstanding performance of Mathematica on 64-bit Macintosh systems."
If you are running into problems running 64-bit code after applying the update, please let us know.
Problems with Safari and Mail.app -- not launching, crashing A number of users report issues with launching, as well as frequent crashes, in both Mail.app and Safari after applying Security Update 2005-007.
MacFixIt reader Alex writes:
"I have had major OS problems since installing the Apple Security Update 2005-007. When I attempt to launch Safari and Mail I get the following message:
"You cannot open the application '(null)' because it may be damaged or incomplete.
"I have managed to send this e-mail from Apple Mail only by clicking on the e-mail link from the MacFixIt site. The Apple mail icon has reverted to an unknown application icon."
Martin Auclair adds:
"After I applied the Security Update for 10.3.9 Client, and did the usual permission fix right after, I found out that I cannot start Safari or Mail.app. I tried re-applying the previous Security Update patch, to no avail."
In some instances of these problems, font issues may be at play. A quick fix is to drag the com.apple.ATS, located in /Library/Caches/ to the trash, then re-attempt using either Safari or Mail.app.
Problems installing through Software Update A number of users report receiving the message "The Update 'Security Update 2005-007' can't be downloaded." when attempting to apply the revision through Software Update.
For these issues, you may want to try the suggestions listed in our tutorial: When Software Update won't work
Login items lost Several readers report that they lost their user-added login items after applying Security Update 2005-007. The only solution thus far is to manually re-add each item.
AppleTalk over Ethernet broken for some MacFixit reader Suryaprabha is one of a handful who report issues with AppleTalk after the update:
"I have just installed the update on one Mac, G5, and can no longer access my iBook over ethernet/Apple Talk. It's alias can be seen and on attempting to mount a Little Snitch dialogue appears saying afp_mount wants to connect to 192.168.100.21 on TCP port 548 (afpovertcp) which if I allow waits a minute before saying Connection Denied.
"Previously there was no interruption and I mounted the iBook without hassle. I can mount in reverse as I have not installed the security update on the iBook. So beware."
Feedback? Late-breakers@macfixit.com.
Resources