• On The Insider: Britney's Bikini-Clad Top 10
advertisement
November 1, 2005 8:00 AM PST

Mac OS X 10.4.3 (#2): First restart may be longer than usual; General purpose fixes (try these first); Mail 2.0.5 issues; more

by CNET staff
  • Font size
  • Print
  • 25 comments

First restart may be longer than usual Note that your first restart after installing Mac OS X 10.4.3 may be longer than usual -- up to 10 minutes or more on some system installations.

The stall is most likely to occur after the startup progress bar shows completion, but fails to proceed to user login.

In some of these cases, the startup process is only temporarily frozen, and will continue after several minutes of waiting. After the first, abnormally long restart process, future restarts may return to normal speed.

General purpose workarounds (try these first) Two workaround routines will solve many of the issues that are indirectly caused by Mac OS X 10.4.3 installation (i.e. not due to bugs or flaws in the update, but pre-existing system conditions that may be triggered by the updater process).

The routines are as follows:

Delete kernel extension caches, other caches for some issues A number of common issues that crop up after incremental Mac OS X updates can be resolved by deleting specific cache files -- specifically kernel extension caches -- and restarting.

This can most easily be accomplished with a shareware utility like Tiger Cache Cleaner, but also bears a manual process which involves dragging the following files to the trash:

  • com.apple.kernelcaches (a folder in /System/Library/Caches)
  • Extensions.kextcache (a file in /System/Library)
  • Extensions.mkext (a file in /System/Library/)
  • com.apple.ATS (a folder in /Library/Caches/)
  • Files that start with com.apple.LaunchServices (in /Library/Caches)

You will be prompted to enter your administrator password when dragging these files to the trash. You may need to restart after moving them to the trash.

Re-apply the Mac OS X 10.4.3 combo updater A workaround that has proved successful for various problems caused by previous incremental Mac OS X updaters is re-application of the current combination updater. Doing so overwrites potentially problem-causing files that were not replaced by the "Delta" (adjacent version-to-version) update available through Software Update or as a standalone download.

Mail.app 2.0.5 issues The new version of Mail.app, 2.0.5, included with Mac OS X 10.4.3 is exhibiting a variety of issues for upgraders.

MacFixIt reader Brian Burrow reports issues with Junk mail filtering after the update:

"After the Mac OS X 10.4.3 Update, the Junk mail filtering doesn't work properly.. While it does correctly mark all the right messages as junk, mine is set on automatic, which normally moves the junk mail to the junk folder.. Only about half of the messages actually get moved and the rest stay in the Inbox. I can't see anything in common with what stays and what does get moved."

Remove Mail.app plug-ins/add-ons Some issues apparent in Mail.app 2.0.5 are due to incompatibilities with third-party plug-ins or add-ons for the application. Try temporarily removing third-party files from the following folders:

  • ~/Library/Mail/Bundles
  • /Library/Mail/Bundles

and re-launch Mail.app to check for persistence of the issue.

For instance, MacFixIt reader Tom reports an issue with the MailTags add-on:

"(I had a number of problems with Mail.app 2.0.5) and it turned out to be an incompatibility with MailTags 1.0 I was still using -- removing it (and rebuilding the mailboxes) resolved the problem."

Increased fan activity A surprisingly high number of users are reporting dramatically increased fan activity after installing Mac OS X 10.4.3. In some cases, these increases in fan speed and audible volume are only temporary, and will diminish during subsequent operation.

MacFixIt reader Wayne Barber writes:

"Installed Mac OS X 10.4.3 tonight through Software Update. Fans went nuts following the update (Powermac G5 Dual 1.8Ghz with 2Mb memory). At first, I thought the fan activity was caused by Spotlight indexing the computer, which includes the boot drive and two external firewire drives. But no, the increased fan activity continued. Very high-speed fans when opening Firefox, surfing to certain web pages (no discernible pattern or reason). When I say "very high speed fans," I'm talking jet-engine stuff, howlingly fast."

Mark Oliver adds:

"With the 10.4.3 update it is back to the 10.3 days when my legacy G5 Tower dual 2GHz fan would rev up for a few seconds for no apparent reason. Did the usual steps to see if I could fix it with no luck."

Another reader reports the same issue with an iMac G5:

"Updated G5 iMac and now the fan runs at high speed constantly, great for cooling the processor, now approximately 31deg celsius. But extremely noisy. Did all the usual repair permissions before and after, no luck there."

Resetting the SMU In some cases, resetting your Mac's SMU -- system management unit (per Knowledge Base article #301733 for the iMac G5 or Knowledge Base article #300341 for the Power Mac G5) -- can return fans to normal operation.

MacFixIt reader Ian Williams writes:

"I have just applied the 10.4.3 combo update on my iMac G5. Repaired permissions before and after. The iMac is now starting normally but the fans are spinning very noisily and won't settle down. [...] Follow-up on my last report of fan noise and keychain problems after updating to 10.4.3. Resetting the SMU appears to have resolved both problems."

Failing an SMU reset, try starting up in Open Firmware mode (by restarting your Mac then immediately holding down the Command, Option, O and F keys simultaneously) then entering the following commands, pressing return after each:

  • reset-nvram
  • set-defaults
  • reset-all

Disk Utility changes: Now has live verification; Ignorable permissions alerts Mac OS X 10.4.3 includes a fairly significant update to Apple's Disk Utility (located in Applications/Utilities).

First, the new release can verify your computer's startup disk (volume) without requiring you to start up from another volume. This feature is called "Live Verification." However, if Disk Utility discovers any issues that require a repair, you will need to start up from your Mac OS X Tiger DVD or CD and use Disk Utility on that disc to make repairs.

Second, there are some new permissions alerts that will be generated by Disk Utility under normal circumstances, and can be safely ignored. These include any error messages that look like:

  • "Incorrect size for file temp(number) (It should be 000 instead of 999)"

and another alert concerning special permissions the Library/Widgets folder.

EyeHome Elgato Systems has confirmed that its EyeHome Mac-to-television streaming software is broken by Mac OS X 10.4.3.

Several MacFixIt reader also reported the issue.

One reader writes:

"After installing the 10.4.3 update, EyeHome 1.6 will no longer run. It starts but then crashes within a few seconds. The system is a dual G5 2.0 GHz (summer 2005 edition) with 2.5 GB memory and two internal hard drives. An EyeTV 200 is also attached and seems to work fine."

Another adds:

"Since upgrading my G5 imac to 10.4.3 Eyehome 1.6 crashes as soon as I try to launch it seems to run for a few seconds then it crashes (I get the this app has quit...report box form os x). Eyehome was working fine with 10.4.2."

The company is working on an update which should be available shortly.

Onyx broken One reader reports that the Onyx system maintenance utility is broken after the Mac OS X 10.4.3 update:

"After update the application ONYX (ver 1.6.5b1) seems to be broken Application runs but keeps coming up with the error message 'Applescript Error ?1762' Tried on two machines and different versions of Onyx ? same result."

M-Audio drivers broken, fix It appears that the M-Audio Delta drivers 2.04 are also broken by Mac OS X 10.4.3

MacFixIt reader Robert Hancock reports a fix:

"The fix discovered by a reader on the Apple Discussions is to roll back the drivers to 2.01 (found under the 10.3.8 OS X drivers at the M-Audio website). These date from May 2005 and have sleep issues but at least no kernel panics or endless audio loops."

PithHelmet broken, fix It appears that PithHelmet, the content filtering/add-on tool for Safari is once again broken under Mac OS X 10.4.3. Until the developer updates the software, a poster to VersionTracker's discussion boards has found a workaround:

  • Close Safari.
  • Navigate to /Library/Application Support/SIMBL/PithHelmet.bundle.
  • Open bundle and go to Contents.
  • Open info.plist - You can use either Property List Editor or TextEdit.
  • Locate BundleIdentifier for com.apple.Safari.
  • Change BOTH MaxBundleVersion AND MinBundleVersion to 416.12.
  • Save and relaunch Safari.

Feedback? Late-breakers@macfixit.com.

Previous coverage:

Resources

  • #301733
  • #300341
  • PithHelmet
  • poster
  • Late-breakers@macfixit.com
  • Apple releases Mac OS X 10...
  • More from Late-Breakers
  • Recent posts from MacFixIt
    Apple releases Aperture 3.0
    Manage iCal's automatic e-mail generation for invitations
    CNET TV Apple Byte: Apple faces critics
    Weekly Utilities Update: Net Monitor, MiniUsage, TimeMachineEditor, more...
    Odds and Ends: Essential video codec packs for OS X
    Address Book: Unable to add, view contacts
    Persistent 'Faster Browser Search' overtaking Safari's default search
    Quick tip: Faster Time Machine backups
    Add a Comment (Log in or register) Showing 1 of 2 pages (25 Comments)
    by James Collymore November 1, 2005 9:28 AM PST
    When I read about the new OS 10.4.3 release through versiontracker.com, I repaired my permissions with disk utility, then I went to Apple.com to download the Combo updater.

    Once downloaded I launched the installer and then did a restart when prompted. It took a while to come up to the desktop, but after about 5 minutes it finally did. The only problem was is that I got a kernel panic just after it filled up my menubar with icons. (The Dock had already come up.) It seemed to be having put the icon of the American flag (for controlling keyboard languages, etc.) up on the menu bar just before the kernel panic.

    I then tried a forced shutdown by holding down the power button on my 17" Apple studio display (2002 vintage). I waited about a minute and then booted up again. The same thing happened (a kernel panic) at about the same point. I am going to try booting up when I get home this evening.

    I should add that I am running on a PowerMac G4 MDD, with 1Gb of RAM, and OS version 10.4.2 prior to this upgrade. The only thing that makes me a little suspicios is that I just upgraded my VirusBarrier application last night and it now adds a pull-down menu to the menu bar (something that I wasn't too keen on when I saw it.) I wonder of that's having an effect.

    Jim Collymore
    Reply to this comment
    by erlong November 1, 2005 9:28 AM PST
    >
    This is a reply to a previous comment by James Collymore


    Jim,

    I am having a similar problem with my menubar icons not appearing. I had Timbuktu installed, which was the only menubar icon to show up. Figuring that might be causing a problem, I deleted it. Now nothing shows up. When I move my mouse over the general area of the menubar clock, I get the spinning ball. The "show clock in menubar" option in the preferences is unchecked, when I check it to enable it, still nothing. Nothing seems to show up (battery status, network status, modem, etc.).

    This is on a PowerBook G4, 768MB RAM, previously running 10.4.2. I've repaired permissions, ran disk utilities, etc. Nothing seems to be working thus far.
    Reply to this comment
    by MacsRus November 1, 2005 9:28 AM PST
    >
    This is a reply to a previous comment by James Collymore


    Run disk utilities from the tiger dvd be sure to do both repairs.
    Btw I did not experience a slow down at start-up.
    Reply to this comment
    by brianf November 1, 2005 9:28 AM PST
    >
    This is a reply to a previous comment by James Collymore


    I experienced the very slow start, but so far no kernal panics. knock on wood.

    I ran Cocktail first, cleared all caches, repaired permissions, etc.

    I could not boot from my Tiger DVD beforehand as I have a new 1.67 ghz
    Powerbook and I do not have my restore DVD with me. Apparently the original
    Tiger DVD is incapable of booting the new machines.

    Brian
    Reply to this comment
    by appleman--2008 November 1, 2005 9:52 AM PST
    i see waynes problem..."(Powermac G5 Dual 1.8Ghz with 2Mb memory)"
    upgrade your mrmory...LOL
    i know he meant 2GB
    Reply to this comment
    by ranchr November 1, 2005 11:00 AM PST
    Ever since updating 4 computers to 10.4.3 Internet Explorer that has msn.com as the start page hangs and has to be force quit as "Explorer not responding." It is some sort of java script error and my guess is this would be a world-wide problem. Most macusers don't use IE but some URL's only work in IE.
    Reply to this comment
    by Ken Lanxner November 1, 2005 11:00 AM PST
    >
    This is a reply to a previous comment by ranchr


    I am experiencing the same IE problem but with 10.4.2. I think the change was
    at msn.com and not related to the 10.4.3 update. My solution was to stop the
    page load before it hung and then change my prefs to delete msn.com as the
    startup page.
    Reply to this comment
    by ranchr November 1, 2005 11:00 AM PST
    >>
    This is a reply to a previous comment by Ken Lanxner


    I couldn't stop it before it hung. However you are right, it was MSN. Late yesterday, MSN fixed the problem and all is well BUT I changed the default to my own website.
    Reply to this comment
    by brianf November 1, 2005 11:00 AM PST
    >>>
    This is a reply to a previous comment by ranchr


    Yes, I agree it was not caused by the 10.4.3 update. I experienced this problem
    under 10.4.2.

    Brian
    Reply to this comment
    by Tee Jay November 1, 2005 11:00 AM PST
    >>>>
    This is a reply to a previous comment by brianf



    The same Internet Explorer hang occurs sometimes under Mac OS X v10.3.x as well. In fact, just yesterday I saw this issue on a Panther machine.

    If you have some special reason why you need to use IE, tell IE to Stop before MSN fully loads, then change your homepage to something else (http://www.google.com/ is safe).

    Reply to this comment
    by donrichardsoth November 1, 2005 11:00 AM PST
    >>>>>
    This is a reply to a previous comment by Tee Jay


    I have the same problem on two Macs, using 10.3 and 10.4 - started by
    hanging at start-up of msn.com - changed apps both to "blank" at start
    address and thought problem was solved . . . alas no -
    www.versiontracker.com/dyn/moreinfo/macosx/20070&vid=243600 now
    hangs . . .or it did, now seems OK again. When it hung it was downloading an
    image and mentioned something about java (cant get exact message cos its
    working again). Something flakey is going on . . . and it doesn't seem to be
    10.4
    Reply to this comment
    by xmrocks November 1, 2005 11:08 AM PST
    For those experiencing Keychain issues at login (i.e. asking for a password and
    no passwords work), click Cancel and open Keychain Access. Then repair the
    Keychain by running Keychain First Aid. Subsequent reboots will not not display
    the "Keychain wants to use login" for Airport dialog, or your password will work.

    -Ryan
    Reply to this comment
    by gresmi November 1, 2005 11:08 AM PST
    >
    This is a reply to a previous comment by xmrocks


    Thank you thank you thank you!
    Strangely enough I've been having this issue since I updated my clean install of Tiger 10.4 on a freshly formatted external drive on my Mac Mini 1.42;1GBram;combo drive; to 10.4.2 which came out a few months ago and I've had to deal with this issue all this time. hence I don't actually think its a 10.4.3 issue, but nonetheless, you just solved my problem!
    Reply to this comment
    by xmrocks November 1, 2005 11:08 AM PST
    >>
    This is a reply to a previous comment by gresmi


    Glad I can help, gresmi :)
    Reply to this comment
    by jelockwood November 1, 2005 11:08 AM PST
    >
    This is a reply to a previous comment by xmrocks


    Yep I had this issue after upgrading to 10.4.3 on my own laptop. It did not
    happen on the other three machines I have done.

    I resolved it by copying over a good System.keychain file from an already
    upgraded master disk image.
    Reply to this comment
    by Glenn Pillsbury November 1, 2005 11:08 AM PST
    >
    This is a reply to a previous comment by xmrocks


    Thanks also for passing that along. I was updating my PB while watching TV this evening and saw from across the room that I had the Keychain problem (though not on the first restart -- I did the post-update perms repair and then re-restarted, and that's when the Keychain problem appeared). I remembered your post from this morning and the First Aid function fixed it immediately. Thanks again.
    Reply to this comment
    by slboettcher November 1, 2005 4:38 PM PST
    OnyX has been fixed.
    The "live verification" needs a Journalized drive to run.

    SB
    Reply to this comment
    by asorum November 1, 2005 7:34 PM PST
    I updated to 10.4.3 and my external hard drive disappeared from the desktop. It was connected via firewire. Doesn't show up on disk utility. Plugged the drive into USB and it mounted. Have an old B&W G3, so it's USB1 and really slow this way. Any ideas?>>
    Reply to this comment
    by brianf November 1, 2005 7:35 PM PST
    >
    This is a reply to a previous comment by asorum


    Well, this is an after the fact...

    It has been well noted for the last couple of years that you should ALWAYS
    disconnect firewire drives before applying any of the OS updates. Issues from
    drives failing to mount to drives apparently killed have resulted. There are
    many, many threads on this issues here and other fix it sites.

    Try to repair the drive. Try to mount it on a different machine, etc.

    Best of luck

    Brian
    Reply to this comment
    by John Sawyer November 1, 2005 7:35 PM PST
    >
    This is a reply to a previous comment by asorum


    You don't mention if you tried this drive on another Mac's Firewire ports. Assuming you haven't, and also assuming the problem may be your Mac's Firewire ports instead of the Firewire drive, these steps sometimes revive newly nonfunctional Firewire ports:

    -- Reset the Mac's PRAM / NVRAM and Open Firmware:
    Shut down the Mac (don't perform these steps from a restart, or it won't clear the NVRAM chip), wait at least five seconds, then power up the Mac. Quickly, before the screen lights up, hold down Command-Option-P-R, and keep these keys held down until the Mac has chimed twice. Then quickly move your fingers so you're holding down Command-Option-O-F. This will bring up the Open Firmware screen. Here, enter:

    reset-nvram
    set-defaults
    reset-all

    The last command will restart the Mac.

    -- If that doesn't revive the Mac's Firewire ports, power off the Mac, unplug its AC power cord, then open up the Mac. Press the logic board's reset button. In the B&W G3, this button is located near the clock / PRAM battery; there are two such buttons in that general location, but they're marked, I believe (I'm not where my B&W G3 is located or else I could be more specific). It won't hurt to press the wrong one. Press the button for about five seconds, then close up the Mac, plug in the AC power cord, and power up the Mac and see if that's helped.
    Reply to this comment
    Showing 1 of 2 pages (25 Comments)
    advertisement

    About MacFixIt

    MacFixIt is CNET's troubleshooting resource for all things Mac. The information here helps you navigate the ins-and-outs of Mac ownership with how-tos, troubleshooting information, news, reviews, and more.

    Add this feed to your online news reader