Security Update 2005-007 v1.1. (#5): Repairing startup disk while booted from Tiger DVD (or other Mac OS X volume); more

Repairing startup disk while booted from Tiger DVD (or other Mac OS X volume) can resolve issues We previously reported that a number of issues caused by Security Update 2005-007 v.1.1 can be avoided by repairing the normal startup disk while booted from another volume (such as your Mac OS X 10.4.x Tiger DVD or another volume with a valid Mac OS X installation) during the update process as follows:

1. 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, your Mac OS X 10.4.x Tiger DVD 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).
2. 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)

Now we've received reports from readers indicating that performing the same process after installing Security Update 2005-007 1.1 can have similar beneficial effects.

MacFixIt reader Mike writes:

"I had all sorts of problems last night immediately after installing the security update v1.1 Finder was inept, spinning pizza ball, couldn't do anything, even hard to restart as Finder wouldn't respond. Very, very frustrating !!!

"I started form the Tiger DVD, ran Disk Utility and repaired permissions and everything is wonderful again. The speed that the security update v1.0 gave was back. Very, very nice. You should pass this onto your reading as I see a lot of frustration from the postings on your site and others."

Permanently fixing Sherlock issues We previously reported on issues with Sherlock being unable to properly search after the update.

In some cases, the solution for this issue is to navigate to the directory ~/Library/Caches/Sherlock/WebFoundation and delete all folders therein.

Now some users are reporting that the problem resurfaces after restarting or, in some cases, re-launching Sherlock.

The solution in this case is to navigate to the same WebFoundation folder, delete all of its contents, then perform a Get Info on the folder (Command-I while the folder is selected, or "Get Info" from the File menu) and checking the "Locked" box. This may result in slower operation from Sherlock as it is no longer to cache information, but should eliminate search issues.

MacFixIt reader Bob Gallant offers a case example:

"I have a Beige G3 and an iBook G3 operating in Mac OS X 10.4.2. I downloaded Security Update 2005-007 and later v.1.1 when it was available. After v.1.1 was downloaded, I noted that Sherlock behaved weirdly on both computers in exactly the same way. I tried the fix suggested in MacFixIt 'Security Update 2005-007 v.1.1 (#4): Instructions etc.' which calls for trashing the contents of (user)/library/caches/Sherlock/WebFoundation. This worked the first time. On quitting Sherlock, WebFoundation was filled again with the Sherlock cache folders. On the second restart, the weirdness returned. I then emptied WebFoundation and then got the Info page on this folder and locked WebFoundation. That fixed the problem in that the folder stayed empty after numerous restarts. However, without proper cache files, Sherlock starts a bit slowly, but that is obviously better than return of the weirdness."

"Weirdness on both computers for me meant that the Channel icons in the toolbar appeared with the names in French, did not work when clicked and then disappeared entirely. The fix above immediately restores normal operation without reloading anything."

Continued problems with Bluetooth Users continue to report issues with loss of Bluetooth connectivity after applying Security Update 2005-007 1.1.

MacFixIt reader Emiliano writes:

"After installing Security Update 2005-007 1.1, the bluetooth icon on the menu bar disappears every time I reboot. To make it 'appear' again I have to ho to System Preferences/Bluetooth, deactivate bluetooth and then reactivate it again. Anyway, Bluetooth connection seems to work as always."

VLC crashing with certain ATI Radeon cards MacFixIt reader Keith Takayesu reports an issue where the shareware video playing software VLC (VideoLan Client) repeatedly crashes after a few minutes of video after Security Update 2005-007 is applied. The problem seems to be specific to the Radeon 9200 graphics card at this point:

"The biggest problem seems to be a video crash when playing a video via VLC. My Radeon 9200 on my Cube was acting up (hmm, come to think about it, since Security Update 2005 v1.0), so I had gone back to my Radeon 7000. I have them both set up so that the S-Video goes to the TV for movie playback.

"I tried playing some movies (from the hard drive) on VLC today, after the latest update 1.1. The movie would play fine for 5-6 minutes, then the video screen and Mac display totally freeze. The weird thing is that the audio kept going, as though everything was running fine. However, I was totally locked out, only a hard reset would get me out of it. I repeated it with several different movies, just to make sure it wasn't the movie crashing everything. Same thing, video locks up after 5-6 minutes or so.

"I then played the movie in fullscreen mode on the Mac screen, and it would play through without crashing anything. I'm going to re-install the Radeon 9200, and see if the same thing happens.

"Luckily, I keep a backup system on another drive, this one does not have any of the Security Updates on it yet. VLC runs fine on that system, using the Radeon 7000 S-Video out. No video crashes at all."

Feedback? Late-breakers@macfixit.com.

• Security Update 2005-007 v.1.1 (#4): Instructions for getting the update off your Mac; Safari, Mail.app issues; more
• Apple releases Security Update 2005-007 v1.1, fixes 64-bit bug
• Security Update 2005-007 (#2): Proper updating procedure; Problems with startup, reverting; 64-bit apps broken; more
• Apple releases Security Update 2005-007

Resources