Older iMac slows then repairing disk permissions fixes - culprit?

Mom's older iMac 350 running Panther is fine and then every so often it slows down significantly (even closing windows is very slow).
Running Disk Utilities repair disk permissions always seems to solve the problem.
Just curious if anyone knows what's going on here. This doesn't occur frequently, I think we've only done this twice in the past 8 months. Just curious what the culprit is here & has anyone else experienced this.

Hi mjp29,
even the best quality machines need some regular maintenance (MacOS X 10.3/10.4: System maintenance). Just think of your car and what would happen if you never changed/added some oil...
If this answered your question please consider granting some stars: Why reward points?

Similar Messages

  • Slow.  iMac 10.5.8.  Verified Disk Permissions and then Repaired Disk Permissions.  Not much improvement in speed.  How do I empty internet files from safari?

    iMac 10.5.8 is slow.  Verified Disk Permissions and then repaired.  No big improvement in speed.
    What about internet files (safari and firefox) ; caches and cookies?
    Thank you.

    Applejack might help.
    Download:
    http://sourceforge.net/projects/applejack/
    Article on using:
    http://reviews.cnet.com/8301-13727_7-10334620-263.html?tag=mfiredir
    It runs in single user mode, where it runs more safely than other maintenance/cleaning programs because there is less chance of interference from the OS. After installing (you won't see it in the Applications Folder) hold CMD-S at startup. You will get a black screen with MS-DOS like text. Just follow the prompts: type in "applejack AUTO" and it will run through the following:
    Correct any Disk problems.
    Repair Permissions.
    Clear out Cache Files.
    Repair/check several plist files.
    Dump the VM files for a fresh start.
    Trash old Log files.
    You can also run tasks selectively and for specific users by typing in "applejack." After running in "AUTO,"  you can go back and run it again as "applejack," steps 3 & 4 only, for your user.
    The first reboot will take much longer than usual, as it rebuilds caches. It may take several restarts to see the benefits. Because of the deep cache cleaning in AUTO mode some applications may tell you they are being opened for the first time.
    NOT YET UPDATED FOR LION
    (Adapted from post by BDAqua)

  • "Repair disk permissions" fixed install problem for me.

    First time trying to install SL I got nothing. No windows opened, no error messages, no nothing. The system just looked at me like I was stupid.
    After a good nights sleep I ran "repair disk permissions." It repaired a bunch of files (how did THAT happen???) and ran installer for SL again.
    Worked perfectly!!! Gained a whopping 19.945 gig of HD space. YIKES!!!

    First time trying to install SL I got nothing. No windows opened, no error messages, no nothing. The system just looked at me like I was stupid.
    After a good nights sleep I ran "repair disk permissions." It repaired a bunch of files (how did THAT happen???) and ran installer for SL again.
    Worked perfectly!!! Gained a whopping 19.945 gig of HD space. YIKES!!!

  • Constantly having to repair disk permissions after hanging system

    From the time I purchased this I've had ongoing issues with the java, flash, OS updates causing the computer to hang forever. Sometimes I end up having to press the off button because Command Q and Command/Option/Escape won't allow a force quit even after a 20 minute wait. I don't know enough about what's going on behind the boot up to know what's wrong. Here is a copy of my console log and this is exactly what they look like each time after I have gone in and done a disk verify, (says it's okay) and then repair disk permissions. I've had to boot to safe mode 3 times today and repair permissions due to this issue. There is nothing plugged into the computer except the power cord. The OS is up to date per Software Update and the only 3rd party software installed is SKYPE ...
    1/25/11 5:45:58 PM SoftwareUpdateCheck[520] Checking for updates
    1/25/11 5:45:58 PM storeagent[524] port created
    1/25/11 5:46:27 PM com.apple.launchd[1] (com.apple.suhelperd[522]) Exited with exit code: 2
    1/25/11 5:46:27 PM com.apple.launchd.peruser.501[88] ([0x0-0x3d03d].SoftwareUpdateCheck[520]) Exited with exit code: 102
    1/25/11 8:21:42 PM [0x0-0x52052].com.skype.skype[613] Main starting with pid 613 parent pid 88
    1/25/11 8:21:43 PM Skype[613] SkypeApplication::init called
    1/25/11 10:56:56 PM com.apple.launchd[1] * launchd[1] has started up. *
    1/25/11 11:09:29 PM com.apple.fontd[70] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/25/11 11:09:31 PM com.apple.WindowServer[72] Tue Jan 25 23:09:31 Troy-Lindstroms-MacBook.local WindowServer[72] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/25/11 11:09:32 PM com.apple.fontd[70] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/25/11 11:09:40 PM com.apple.UserEventAgent-LoginWindow[79] ALF error: cannot find useragent 1102
    1/25/11 11:09:40 PM com.apple.UserEventAgent-LoginWindow[79] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/25/11 11:09:40 PM com.apple.launchd.peruser.501[90] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/25/11 11:09:42 PM fontd[100] Database content version mismatch (stored(15) != expected(14))
    1/25/11 11:09:47 PM com.apple.launchd.peruser.501[90] (com.apple.Kerberos.renew.plist[108]) Exited with exit code: 1
    1/25/11 11:10:09 PM com.apple.coreservicesd[44] ThrottleProcessIO: throttling disk i/o
    1/25/11 11:10:12 PM com.apple.coreservicesd[44] ThrottleProcessIO: throttling disk i/o
    1/25/11 11:10:13 PM com.apple.launchd.peruser.501[90] (com.apple.AirPortBaseStationAgent[110]) Exited: Killed
    1/25/11 11:10:14 PM com.apple.loginwindow[22] shutdown: / is busy updating; waiting for lock
    1/25/11 11:10:33 PM com.apple.launchd[1] * launchd[1] has started up. *
    1/25/11 11:11:24 PM com.apple.UserEventAgent-LoginWindow[81] ALF error: cannot find useragent 1102
    1/25/11 11:11:24 PM com.apple.UserEventAgent-LoginWindow[81] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/25/11 11:11:24 PM com.apple.launchd.peruser.501[90] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/25/11 11:11:28 PM fontd[101] Database content version mismatch (stored(15) != expected(14))
    1/25/11 11:11:28 PM fontd[101] Failed to open read-only database, regenerating DB
    1/25/11 11:11:34 PM com.apple.launchd.peruser.501[90] (com.apple.Kerberos.renew.plist[111]) Exited with exit code: 1
    1/25/11 11:11:40 PM com.apple.fontd[101] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/25/11 11:11:48 PM com.apple.fontd[101] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/25/11 11:11:49 PM [0x0-0x9009].com.skype.skype[116] Main starting with pid 116 parent pid 90
    1/25/11 11:11:51 PM Skype[116] SkypeApplication::init called
    1/25/11 11:38:12 PM com.apple.WindowServer[69] Tue Jan 25 23:38:12 Troy-Lindstroms-MacBook.local WindowServer[69] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/26/11 11:36:13 AM [0x0-0x6d06d].com.skype.skype[666] Main starting with pid 666 parent pid 90
    1/26/11 11:36:14 AM Skype[666] SkypeApplication::init called
    1/26/11 12:25:04 PM com.apple.launchd.peruser.501[90] ([0x0-0x6d06d].com.skype.skype[666]) Exited: Terminated
    1/26/11 5:45:58 PM SoftwareUpdateCheck[867] Checking for updates
    1/26/11 5:45:58 PM storeagent[870] port created
    1/26/11 5:47:17 PM com.apple.launchd[1] (com.apple.suhelperd[869]) Exited with exit code: 2
    1/26/11 5:47:17 PM com.apple.launchd.peruser.501[90] ([0x0-0x92092].SoftwareUpdateCheck[867]) Exited with exit code: 102
    1/26/11 8:32:58 PM [0x0-0x11011].com.apple.Safari[143] Wed Jan 26 20:32:58 Troy-Lindstroms-MacBook.local Safari[143] <Error>: unknown error code: invalid drawable
    1/26/11 8:32:58 PM [0x0-0x11011].com.apple.Safari[143] Wed Jan 26 20:32:58 Troy-Lindstroms-MacBook.local Safari[143] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/26/11 8:33:10 PM [0x0-0x11011].com.apple.Safari[143] Wed Jan 26 20:33:10 Troy-Lindstroms-MacBook.local Safari[143] <Error>: unknown error code: invalid drawable
    1/26/11 8:33:24 PM [0x0-0x11011].com.apple.Safari[143] Wed Jan 26 20:33:24 Troy-Lindstroms-MacBook.local Safari[143] <Error>: unknown error code: invalid drawable
    1/26/11 10:48:32 PM com.apple.launchd.peruser.501[90] ([0x0-0x11011].com.apple.Safari[143]) Exited: Terminated
    1/26/11 10:49:37 PM com.apple.launchd[1] (com.apple.suhelperd[1047]) Exited with exit code: 2
    1/26/11 10:49:44 PM com.apple.launchd.peruser.501[90] (com.apple.AirPortBaseStationAgent[113]) Exited: Killed
    1/27/11 11:39:52 PM com.apple.launchd[1] * launchd[1] has started up. *
    1/27/11 11:40:14 PM com.apple.launchd.peruser.501[84] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/27/11 11:40:15 PM com.apple.UserEventAgent-LoginWindow[77] ALF error: cannot find useragent 1102
    1/27/11 11:40:15 PM com.apple.UserEventAgent-LoginWindow[77] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/27/11 11:40:15 PM SoftwareUpdateCheck[98] Checking for updates
    1/27/11 11:40:15 PM com.apple.launchd.peruser.501[84] (com.apple.Kerberos.renew.plist[111]) Exited with exit code: 1
    1/27/11 11:40:17 PM storeagent[119] port created
    1/27/11 11:40:21 PM com.apple.WindowServer[65] Thu Jan 27 23:40:21 Troy-Lindstroms-MacBook.local WindowServer[65] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/27/11 11:40:27 PM [0x0-0xa00a].com.skype.skype[116] Main starting with pid 116 parent pid 84
    1/27/11 11:40:29 PM Skype[116] SkypeApplication::init called
    1/27/11 11:41:02 PM SoftwareUpdateCheck[98] Downloading "iTunes"
    1/27/11 11:42:35 PM SoftwareUpdateCheck[98] Auto-download of "iTunes" SUCCESSFUL.
    1/27/11 11:42:35 PM SoftwareUpdateCheck[98] Launching app
    1/27/11 11:43:20 PM com.apple.launchd.peruser.501[84] ([0x0-0x6006].SoftwareUpdateCheck[98]) Exited with exit code: 102
    1/28/11 9:51:59 AM com.apple.RemoteUI[589] CoreAnimation: rendering error 501
    1/28/11 9:52:15 AM com.apple.RemoteUI[589] HTTP2 Streaming Reads ON
    1/28/11 11:31:15 AM com.apple.launchd.peruser.501[84] ([0x0-0x10010].com.apple.Safari[134]) Exited: Terminated
    1/28/11 11:42:21 AM com.apple.launchd[1] (com.apple.suhelperd[104]) Exited with exit code: 2
    1/28/11 3:49:50 PM com.apple.launchd.peruser.501[84] (com.apple.AirPortBaseStationAgent[113]) Exited: Killed
    1/28/11 3:49:50 PM com.apple.launchd.peruser.501[84] ([0x0-0x80080].com.apple.iTunesHelper[764]) Exited: Killed
    1/28/11 3:50:10 PM com.apple.launchd.peruser.501[84] (com.apple.Dock.agent[88]) Exit timeout elapsed (20 seconds). Killing
    1/28/11 3:53:36 PM com.apple.launchd[1] * launchd[1] has started up. *
    1/28/11 3:55:16 PM com.apple.launchd.peruser.501[90] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/28/11 3:55:16 PM com.apple.UserEventAgent-LoginWindow[82] ALF error: cannot find useragent 1102
    1/28/11 3:55:16 PM com.apple.UserEventAgent-LoginWindow[82] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/28/11 3:55:25 PM com.apple.launchd.peruser.501[90] (com.apple.Kerberos.renew.plist[111]) Exited with exit code: 1
    1/28/11 3:55:27 PM com.apple.WindowServer[72] Fri Jan 28 15:55:27 Troy-Lindstroms-MacBook.local WindowServer[72] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/28/11 3:55:40 PM [0x0-0x8008].com.skype.skype[115] Main starting with pid 115 parent pid 90
    1/28/11 3:55:41 PM Skype[115] SkypeApplication::init called
    1/28/11 11:40:16 PM SoftwareUpdateCheck[419] Checking for updates
    1/28/11 11:40:16 PM storeagent[422] port created
    1/28/11 11:40:59 PM com.apple.launchd[1] (com.apple.suhelperd[421]) Exited with exit code: 2
    1/28/11 11:40:59 PM com.apple.launchd.peruser.501[90] ([0x0-0x56056].SoftwareUpdateCheck[419]) Exited with exit code: 102
    1/29/11 3:02:24 AM quicklookd[551] [QL] 'Creating thumbnail' timed out for '<QLThumbnailRequest /Users/troylindstrom/Downloads/images-30.jpeg>' (Start date: 2011-01-29 03:02:04 -0800)
    1/29/11 3:05:11 AM quicklookd[555] [QL] 'Creating thumbnail - cancelled' timed out for '<QLThumbnailRequest /Users/troylindstrom/Downloads/About Downloads.pdf>' (Start date: 2011-01-29 03:03:35 -0800)
    1/29/11 3:05:52 AM quicklookd[560] [QL] 'Creating thumbnail' timed out for '<QLThumbnailRequest /Users/troylindstrom/Downloads/About Downloads.pdf>' (Start date: 2011-01-29 03:05:32 -0800)
    1/29/11 3:06:44 AM quicklookd[563] [QL] 'Creating thumbnail' timed out for '<QLThumbnailRequest /Users/troylindstrom/Downloads/images-3.jpeg>' (Start date: 2011-01-29 03:06:22 -0800)
    1/29/11 6:37:03 AM com.apple.launchd.peruser.501[90] ([0x0-0x86086].com.apple.Preview[708]) Exited: Killed
    1/29/11 6:37:03 AM com.apple.launchd.peruser.501[90] ([0x0-0x8a08a].com.apple.systemevents[721]) Exited: Killed
    1/29/11 6:37:03 AM com.apple.launchd.peruser.501[90] (com.apple.AirPortBaseStationAgent[113]) Exited: Killed
    1/29/11 6:37:13 AM com.apple.launchd[1] * launchd[1] has started up. *
    1/29/11 6:37:42 AM com.apple.UserEventAgent-LoginWindow[81] ALF error: cannot find useragent 1102
    1/29/11 6:37:42 AM com.apple.UserEventAgent-LoginWindow[81] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/29/11 6:37:42 AM com.apple.launchd.peruser.501[89] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/29/11 6:37:50 AM com.apple.WindowServer[54] Sat Jan 29 06:37:50 Troy-Lindstroms-MacBook.local WindowServer[54] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/29/11 6:37:52 AM com.apple.launchd.peruser.501[89] (com.apple.Kerberos.renew.plist[109]) Exited with exit code: 1
    1/29/11 6:38:03 AM [0x0-0x8008].com.skype.skype[113] Main starting with pid 113 parent pid 89
    1/29/11 6:38:05 AM Skype[113] SkypeApplication::init called
    1/29/11 12:14:57 PM [0x0-0x36036].com.apple.CharacterPaletteIM[330] objc[330]: Class ThinDividerSplitView is implemented in both /System/Library/Input Methods/CharacterPalette.app/Contents/MacOS/CharacterPalette and /System/Library/Input Methods/CharacterPalette.app/Contents/PlugIns/RomanView.CharPalettePlugin/Conte nts/MacOS/RomanView. One of the two will be used. Which one is undefined.
    1/29/11 12:43:40 PM [0x0-0x39039].com.apple.CharacterPaletteIM[346] objc[346]: Class ThinDividerSplitView is implemented in both /System/Library/Input Methods/CharacterPalette.app/Contents/MacOS/CharacterPalette and /System/Library/Input Methods/CharacterPalette.app/Contents/PlugIns/RomanView.CharPalettePlugin/Conte nts/MacOS/RomanView. One of the two will be used. Which one is undefined.
    1/29/11 6:52:46 PM com.apple.launchd.peruser.501[89] ([0x0-0xf00f].com.apple.Safari[131]) Exited: Terminated
    1/29/11 6:52:59 PM com.apple.launchd.peruser.501[89] ([0x0-0x1e01e].com.apple.AddressBook[206]) Exited: Terminated
    1/29/11 6:52:59 PM loginwindow[29] * -[NSCFArray objectAtIndex:]: index (1) beyond bounds (1)
    1/29/11 6:52:59 PM com.apple.loginwindow[29] 2011-01-29 18:52:59.446 loginwindow[29:107] * -[NSCFArray objectAtIndex:]: index (1) beyond bounds (1)
    1/29/11 6:53:14 PM com.apple.launchd.peruser.501[89] (com.apple.AirPortBaseStationAgent[111]) Exited: Killed
    1/30/11 9:17:52 AM com.apple.launchd[1] * launchd[1] has started up. *
    1/30/11 9:19:51 AM com.apple.fontd[66] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/30/11 9:19:51 AM com.apple.WindowServer[68] Sun Jan 30 09:19:51 Troy-Lindstroms-MacBook.local WindowServer[68] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/30/11 9:19:54 AM com.apple.fontd[66] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/30/11 9:20:00 AM com.apple.UserEventAgent-LoginWindow[78] ALF error: cannot find useragent 1102
    1/30/11 9:20:00 AM com.apple.UserEventAgent-LoginWindow[78] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/30/11 9:20:00 AM com.apple.launchd.peruser.501[86] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/30/11 9:20:02 AM fontd[98] Database content version mismatch (stored(15) != expected(14))
    1/30/11 9:20:04 AM SoftwareUpdateCheck[94] Checking for updates
    1/30/11 9:20:05 AM storeagent[102] port created
    1/30/11 9:20:08 AM com.apple.launchd.peruser.501[86] (com.apple.Kerberos.renew.plist[109]) Exited with exit code: 1
    1/30/11 9:20:38 AM com.apple.launchd.peruser.501[86] (com.apple.AirPortBaseStationAgent[111]) Exited: Killed
    1/30/11 9:20:39 AM com.apple.loginwindow[22] shutdown: / is busy updating; waiting for lock
    1/30/11 9:20:44 AM com.apple.launchd[1] (com.apple.suhelperd[101]) Exited with exit code: 2
    1/30/11 9:20:45 AM com.apple.launchd.peruser.501[86] ([0x0-0x6006].SoftwareUpdateCheck[94]) Exited with exit code: 102
    1/30/11 9:20:49 AM com.apple.coreservicesd[44] ThrottleProcessIO: throttling disk i/o
    1/30/11 9:20:55 AM com.apple.coreservicesd[44] ThrottleProcessIO: throttling disk i/o
    1/30/11 9:21:16 AM com.apple.launchd[1] * launchd[1] has started up. *
    1/30/11 9:22:04 AM com.apple.UserEventAgent-LoginWindow[81] ALF error: cannot find useragent 1102
    1/30/11 9:22:04 AM com.apple.UserEventAgent-LoginWindow[81] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/30/11 9:22:04 AM com.apple.launchd.peruser.501[89] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/30/11 9:22:07 AM fontd[101] Database content version mismatch (stored(15) != expected(14))
    1/30/11 9:22:07 AM fontd[101] Failed to open read-only database, regenerating DB
    1/30/11 9:22:11 AM com.apple.fontd[101] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/30/11 9:22:13 AM com.apple.launchd.peruser.501[89] (com.apple.Kerberos.renew.plist[111]) Exited with exit code: 1
    1/30/11 9:22:19 AM com.apple.WindowServer[69] Sun Jan 30 09:22:19 Troy-Lindstroms-MacBook.local WindowServer[69] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/30/11 9:22:26 AM com.apple.fontd[101] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/30/11 9:22:26 AM [0x0-0x9009].com.skype.skype[116] Main starting with pid 116 parent pid 89
    1/30/11 9:22:28 AM Skype[116] SkypeApplication::init called
    1/30/11 10:33:53 AM com.apple.launchd.peruser.501[89] (com.apple.AirPortBaseStationAgent[113]) Exited: Killed
    1/30/11 10:34:02 AM com.apple.launchd[1] * launchd[1] has started up. *
    1/30/11 10:34:26 AM com.apple.launchd.peruser.501[86] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/30/11 10:34:26 AM com.apple.UserEventAgent-LoginWindow[79] ALF error: cannot find useragent 1102
    1/30/11 10:34:26 AM com.apple.UserEventAgent-LoginWindow[79] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/30/11 10:34:28 AM com.apple.launchd.peruser.501[86] (com.apple.Kerberos.renew.plist[107]) Exited with exit code: 1
    1/30/11 10:34:32 AM [0x0-0x8008].com.skype.skype[112] Main starting with pid 112 parent pid 86
    1/30/11 10:34:36 AM Skype[112] SkypeApplication::init called
    1/30/11 3:37:45 PM com.apple.launchd[1] * launchd[1] has started up. *
    1/30/11 3:50:19 PM com.apple.fontd[68] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/30/11 3:50:19 PM com.apple.WindowServer[69] Sun Jan 30 15:50:19 Troy-Lindstroms-MacBook.local WindowServer[69] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/30/11 3:50:21 PM com.apple.fontd[68] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/30/11 3:50:52 PM com.apple.coreservicesd[45] ThrottleProcessIO: throttling disk i/o
    1/30/11 3:53:14 PM com.apple.UserEventAgent-LoginWindow[80] ALF error: cannot find useragent 1102
    1/30/11 3:53:14 PM com.apple.UserEventAgent-LoginWindow[80] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/30/11 3:53:14 PM com.apple.launchd.peruser.501[90] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/30/11 3:53:15 PM fontd[101] Database content version mismatch (stored(15) != expected(14))
    1/30/11 3:53:18 PM com.apple.coreservicesd[45] ThrottleProcessIO: throttling disk i/o
    1/30/11 3:53:20 PM com.apple.launchd.peruser.501[90] (com.apple.Kerberos.renew.plist[109]) Exited with exit code: 1
    1/30/11 4:00:53 PM com.apple.launchd.peruser.501[90] (com.apple.AirPortBaseStationAgent[111]) Exited: Killed
    1/30/11 4:12:07 PM com.apple.launchd[1] * launchd[1] has started up. *
    1/30/11 4:12:56 PM com.apple.UserEventAgent-LoginWindow[81] ALF error: cannot find useragent 1102
    1/30/11 4:12:56 PM com.apple.UserEventAgent-LoginWindow[81] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/30/11 4:12:56 PM com.apple.launchd.peruser.501[89] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/30/11 4:12:59 PM fontd[101] Database content version mismatch (stored(15) != expected(14))
    1/30/11 4:12:59 PM fontd[101] Failed to open read-only database, regenerating DB
    1/30/11 4:13:06 PM com.apple.launchd.peruser.501[89] (com.apple.Kerberos.renew.plist[111]) Exited with exit code: 1
    1/30/11 4:13:15 PM com.apple.fontd[101] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/30/11 4:13:21 PM com.apple.fontd[101] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/30/11 4:13:21 PM [0x0-0x9009].com.skype.skype[116] Main starting with pid 116 parent pid 89
    1/30/11 4:13:23 PM Skype[116] SkypeApplication::init called
    1/30/11 5:12:33 PM com.apple.WindowServer[69] Sun Jan 30 17:12:33 Troy-Lindstroms-MacBook.local WindowServer[69] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/30/11 5:12:34 PM com.apple.RemoteUI[169] CoreAnimation: rendering error 501
    1/30/11 5:12:46 PM com.apple.launchd.peruser.501[89] ([0x0-0x9009].com.skype.skype[116]) Exited: Terminated
    1/30/11 5:12:49 PM com.apple.RemoteUI[169] HTTP2 Streaming Reads ON
    1/30/11 5:13:12 PM System Preferences[175] .scriptSuite warning for result type of command 'timedLoad' in suite 'SystemPreferences': the type NSNumber ('long') doesn't match the result Apple event code ('doub').
    1/31/11 12:17:59 AM com.apple.launchd[1] (com.apple.aslmanager) Throttling respawn: Will start in 5 seconds
    1/31/11 12:54:05 AM com.apple.launchd.peruser.501[89] ([0x0-0x18018].com.apple.Safari[180]) Exited: Terminated
    1/31/11 1:31:00 AM com.apple.launchd.peruser.501[89] (com.apple.AirPortBaseStationAgent[113]) Exited: Killed
    1/31/11 1:31:24 AM com.apple.launchd[1] * launchd[1] has started up. *
    1/31/11 1:33:28 AM com.apple.fontd[66] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/31/11 1:33:29 AM com.apple.WindowServer[67] Mon Jan 31 01:33:29 Troy-Lindstroms-MacBook.local WindowServer[67] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/31/11 1:33:31 AM com.apple.fontd[66] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/31/11 1:33:48 AM com.apple.UserEventAgent-LoginWindow[76] ALF error: cannot find useragent 1102
    1/31/11 1:33:48 AM com.apple.UserEventAgent-LoginWindow[76] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/31/11 1:33:48 AM com.apple.launchd.peruser.501[86] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/31/11 1:33:50 AM fontd[96] Database content version mismatch (stored(15) != expected(14))
    1/31/11 1:33:54 AM com.apple.launchd.peruser.501[86] (com.apple.Kerberos.renew.plist[105]) Exited with exit code: 1
    1/31/11 1:34:13 AM com.apple.coreservicesd[44] ThrottleProcessIO: throttling disk i/o
    1/31/11 1:34:13 AM com.apple.coreservicesd[44] ThrottleProcessIO: throttling disk i/o
    1/31/11 1:44:00 AM com.apple.launchd.peruser.501[86] (com.apple.AirPortBaseStationAgent[107]) Exited: Killed
    1/31/11 1:44:10 AM com.apple.launchd[1] * launchd[1] has started up. *
    1/31/11 1:44:43 AM com.apple.launchd.peruser.501[86] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/31/11 1:44:43 AM fontd[95] Database content version mismatch (stored(15) != expected(14))
    1/31/11 1:44:43 AM fontd[95] Failed to open read-only database, regenerating DB
    1/31/11 1:44:44 AM com.apple.UserEventAgent-LoginWindow[79] ALF error: cannot find useragent 1102
    1/31/11 1:44:44 AM com.apple.UserEventAgent-LoginWindow[79] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/31/11 1:44:45 AM com.apple.launchd.peruser.501[86] (com.apple.Kerberos.renew.plist[108]) Exited with exit code: 1
    1/31/11 1:44:45 AM com.apple.fontd[95] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/31/11 1:44:57 AM com.apple.fontd[95] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/31/11 1:44:58 AM [0x0-0x8008].com.skype.skype[112] Main starting with pid 112 parent pid 86
    1/31/11 1:45:00 AM Skype[112] SkypeApplication::init called
    1/31/11 2:00:28 AM com.apple.launchd[1] (com.apple.suhelperd[141]) Exited with exit code: 2
    Can anyone see the issue or tell me what I need to do to fix this thing???

    Which MacBook model? Did it come with OSX 10.6 or did you upgrade it?

  • You May Want to Repair Disk Permissions After Printer Updates Today

    It's been pretty automatic for quite a while--install printer updates and then repair disk permissions.  Most of the time, the permissions errors aren't critical and everything still works; however, many people like to keep their boot disk permissions fixed.
    After installing "HewlettPackardPrinterDrivers2.7.2" and "BrotherPrinterDrivers2.7" today I again repaired permissions.  The errors weren't critical, but I can't remember seeing more of them than I did today.  Make sure and scroll the list of errors because if you don't have scroll bars showing all the time, it doesn't look like there is much in the way of errors.  When I didn't see a scroll bar, I assumed there were only a few errors--wrong.
      My installation was on a Lion system.  And, Disk Utility did fix them all.  None were there when I repaired permissions a second time.
    Just an FYI.

    Which MacBook model? Did it come with OSX 10.6 or did you upgrade it?

  • Oddity when attempting to repair disk permissions...

    I upgraded to Leopard recently and have been encountering some bizarre issues as of late. For one, it doesn't start up anywhere near as fast as it did when I first installed Leopard. And as far as the reason I'm posting this right now, all the Disk Utility processes seem to take a really long time, longer than usual. I'm running 10.5.2.
    Per example, I verify my disk permissions, and it sits for at least 3-5 minutes with the progress bar locked at about 1/8th complete and the time remaining is indicated as less than one minute. Then it moves forward and completes the process in anywhere between another 3-5 minutes. The same occurs when I repair disk permissions or even verify the disk entirely.
    Also, I'm getting the following log message. It's particularly weird because the exact same message shows up in the log after verifying and then repairing disk permissions, as if the repair process isn't actually repairing anything.
    *Permissions differ on "private/var/log/secure.log", should be -rw-------, they are -rw-r-----.*
    *ACL found but not expected on "Library".*
    Again, this log message is displayed after completing each process. Quite odd... any thoughts? Please advise! Thanks in advance.

    In a nutshell, repairing permissions w/Leopard takes anywhere from 10-40 minutes, depending on what's installed and what's contained in /Library/Receipts/bom/. The repair permissions operation has changed in Leopard. The stalled progress bar is an unresolved bug (they haven't figured out how to make it work whilst it's checking or rebuilding the a.receiptdb, in /Library/Receipts/db/. To see what's really going on, open that folder in a Finder window, select list view, launch Disk Utility, select your boot volume, and click on repair permissions. Watch the Finder window flash files that are being read and checked against the current a.receiptdb file. That's what's taking all the time and freezing the progress bar. Once that's finished, the progress bar starts moving and the permissions are being checked and repaired. Also note, that you won't get any *they were repaired message* back for any that are noted to be incorrect.

  • Running the latest OS Mavericks.  8 gigs of RAM.  150 gigs free space on computer.  Problem: since upgrading to Maverick almost all applications are slow to open, and frequently many 'spinning ball' interruptions.  Repaired disk permissions - no help.

    I'm running the latest OS 10.9.1 Mavericks (late 2009 iMac).  8 gigs of RAM.  150 gigs free space on computer.  Since upgrading to Mavericks, apps are slow to open, with frequent "spinning ball" interruptions.  Repaired Disk Permissions - no help.  Repaired disk - no problems indicated.  Did notice in going to Utilities/Console that there are 4000 messages over a 3 day period.  Any suggesstions how to correct this sudden slow down, other than psychiatric help?

    Yes.  Many messages show up when I try to use Office for Mac 08.  Here's a sample (and one that repeats over and over again):
    2/11/14 1:01:16.577 PM Microsoft Word[1912]: OTAtomicAdd32 is deprecated and will be removed soon.  Please stop using it.
    Also getting many msgs when I use Chrome.

  • New macbook pro, safari won't open and repair disk permissions did nothing to help

    Safari starts, blue bar moves about an inch in search bar, then stops. Then nothing. Tried repairing disk permissions to no avail. Safari still doesn't open. Whatever os x that is installed on new macbook pro's, since just bought on Sunday 10-14-12, is the operating software. The apple store there is no user manual. Strange. So here we are on another, older macbook pro, able to go on internet and see what answers or diagnoses others have tried and trued.

    3 days old?, just pack the machine up and tell them you want another one, that this one is a lemon.
    They will likely take your word for it and just give you another rather than you demand your money back instead.
    If you wait too long then they say you should have brought it back sooner, now have to wait until it's fixed, only to give you more problems later.

  • Repair Disk Permissions Issues

    I'm not sure I am posting this in the correct community but here goes . . .
    I have a 17" Macbook Pro running the latest version of Snow Leopard. It is almost 2 years old and I have 4 gb RAM.
    Recently, it seems to be slowing down and I have to run repair disk permissions 2-3 times a week to recoup a little speed. I also delete my Firefox cache regularly to try to gain a little there. I do make a few videos in iMovie and initially I thought that was the problem but this week I have not really worked in iMovie much and it is still slow. There seems to be some issues in the log of the repair permissions. I hope they show in this image. I don't know what these mean or how to fix them. It is the "permissions differ" entries I am confused about.

    You can ignore those permissions per support article
    http://support.apple.com/kb/TA21090
    Since you brought up iMove, I suspect your storage is nearly full as this most certainly causes the computer to slow down. video files are the biggest culprit.
    Look in your Activity Monitor and reduce the drive space by copying to a external, Disk Utility HFS+ formatted external powered drive of unnecessary files so your boot drive is ideally below 50% filled (yea I know but the computer slows down after that) and not more than 75% filled.
    Once you have done that. Get another newer external powered HFS drive and download the free Carbon Copy Cloner and clone the internal drive to the external.
    Hold option and boot off the external clone, test it out then use Disk Utility to erase the internal and then reverse clone the external onto the internal, this will defragment and optimize your drive so the OS and programs are on the fast part of the drive, not the slow parts.
    Reboot into the internal and run off of the free OnyX's maintainence and cleaning aspects and reboot.
    http://www.titanium.free.fr/
    Sir speedy machine here we come!
    Now of course you may have other issues that could be causing your slow down, like not enough RAM or some sort of failed process or leftover program, tweaks or simply a slow Internet.
    You can opt to simply reinstall OS X 10.6 ( by holding c and booting off the installer disk ) over your installed version (doesn't touch files or programs) then immediatly Software Updating until clear, that will clean anything hanging out in OS X.
    If you still have slowdowns, then it's in what geeks call "User land" basically something installed outside of root, like a program or only runs in user, not in OS X.
    For that you need to create a new user, transfer your files via the Shared Drop and wean yourself off the old user and finally delete it. Also install all new versions of your third party programs removing the originals first.
    That should do it.

  • Repair Disk Permissions utility stalled - I have read the knowledge base

    I have researched the knowledge base and search for posts on this and cannot find answer: Running 10.4 at the latest version. used the original install 1 disc I received with Tiger to repair disc permissions (like Apple support has told me to do in the past, but my current research said I do not need to do this unless certain parameters are met, and none of the parameters applied, but oh well, I am here anyway). Cold Boot from the original install disc 1 and slected the start up disk I use (I only have one start up disc/drive). Did a repair disc permissions and got a long running routine that reporting a lot of fixes, then the utility has stalled -- no progress on the progress bar. I "stopped" the process using the "stop repair" button (three times). The log reflected the utility stopped, but the progress bar still is blue and not moving (for a couple of hours). When I go to quity File >Disk Utility, it warns me that Disk Utility is running and this may make my system unstable/unsuable.
    QUESTION: CAN I JUST QUIT DISK UTILITY AND NOT HAVE ANY ADVERSE AFFECT ON MY IMAC DRIVE?

    Thanks for your advice, I still have an issue:
    -after the first repair disk permission "stalled" process, I exited Disk Utility and cold booted the machine after I had disconnected all external devices other than the original iMac keyboard
    -obtained the combo patch for 10.4.7 from the Apple download site (it had already been installed but I reinstalled per your advice)
    -re-applied the combo patch and then did another cold boot
    -ran Disk Utility from the original Tiger install #1 disk, and then selected "repair disk permissions" for my start up disk (I only have one)
    - process ran for 10 minutes or so then gave the following error message: "Disk Utility Error: Disk Utility has lost its connection with disk utility management tool and cannot continue. Please quit disk utility and re-launch disk utility"
    - I pushed the "stop disk permission repair" button, then quit disk utility, then cold booted the machine again.
    -re-applied combo patch as above, then cold booted the machine
    -ran disk utility from the original iMac install #1 disk, ran "repair disk permissions", and then received the same error message as above.
    - I then just quit Disk Utility and cold booted the machine again and went about my business. There does not seem to be any problem with the machine (was not before, but I ran repair permissions thinkging this was a routine maintenance taks that should be run)
    - in my prior search of the knowledge base, I found the following information about repair disk permissions:
    Location: http://discussions.apple.com/thread.jspa?messageID=607495&#607495
    How often should I Repair Permissions?
    You do not need to Repair Permissions on a regular basis.
    There are only three occasions you need to do this:
    1. When you have just installed something that required you to run an Installer, rather than just copying some software to a folder. This should be done for both Apple and non-Apple software.
    2. When you have been working on your OS X files or folders while booted from OS 9, or remotely connected via a non-OS X machine, since OS 9 and other systems do not handle OS X's permissions correctly.
    3. The other case is if your system is behaving strangely, when you should run Disk Repair from your CD followed by Repair Permissions. This is just to eliminate these things before going on to further trouble-shooting.
    Otherwise you can happily forget about Permissions!"
    So, it would appear I do not need to do anything else; the machine seems to be working properly. Is there anything else I need to do? thanks for the help! Bob

  • When run repair disk permissions?

    I am going to upgrade from Snow Leopard to Mountain Lion.
    I have heard/read that you're supposed to run repair disk permissions beforehand. 
    1.  Should I run repair disk permissions on my brand new backup disk (am planning to backup Snow Leopard and all apps and docs before upgrading to Mountain Lion - - so can restore Snow Leopard etc. if want/need to)?  If so, do I run repair disk permissions on the new backup disk before or after I partition the backup disk [am planning to have two sections, one with all the Snow Leopard stuff, and one for iMac backups that will be made after have upgraded to Mountain Lion])
    2.  When's the best time to run repair disk permissions on my iMac - - before I download Mountain Lion or right before I do the installation of Mountain Lion?
    Thanks.

    It's not a requirement, but it may help especially if you don't attend to the state of your running OS. I recommend doing this:
    Repair the Hard Drive and Permissions
    Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    Then you can proceed to click on the Install button after the upgrade finishes downloading. I also suggest you make a bootable backup of your current Snow Leopard system on an external drive just in case things go badly.

  • Mini kernel panic after repairing disk permissions

    Repaired disk permissions per others' advice on here and other forums because my mini was running unacceptably slow. This didn't cure the problem so I used the tech tools disk that came with apple care- now, I get a kernel panic upon startup. I'm asked to restart the computer, I do it- and then I'm asked again!
    I called apple and they were defensive and rude. Frankly they didn't seem to care about whether or not I'd have to wipe my hard drive. Needless to say this is not something I want to do.
    It seems important to mention that I had an external hard drive connected to my computer- would this matter?
    Would repairing disk permissions CAUSE problems with my computer?
    When the disk repair program ran it said that there was a volume error- it fixed this error and then told me that the volume was error free.
    What can I do? I'm so frustrated! I love my computer and I really don't want to wipe the hard drive!

    We have all been there and we have all done the same thing, so you are part of the club.
    Apple uses a three number versioning system so you are almost there, but not quite.
    MacOS officially does not exist anymore. However, it wouldn't go over well with the then user base to call their next operating system for their computers NeXTstep as they felt the entire identy of a Mac was its OS or more specifically its look and feel.
    So they called it Mac OS 10 instead, opting for the roman numeral X.
    Mac OS X is pronounced Mac OS Ten, or simply OS Ten
    Now that 10 is out of the way.
    The second numeric position represents significant
    pause
    um yeah, some might argue with Tiger not as much so but significant changes to the OS.
    10.4
    There.. Each significant change was associate with a moniker representing a cat. 10.4 is associated with the Tiger, 10.3 with the Panther, 10.2 with the Jaguar, etc.
    So Tiger is Mac OS 10.4 or simply OS Ten dot Four
    Within each release is a bugfix release which also may contain usability enhancements and security patches.
    10.4.0 - the initial product release, also called a `Dot-Oh` release
    10.4.1 - the first round of bugfixes
    10.4.2 - the second round of bugfixes
    This continues on sequentially until theoretically the bugs are all fixed in the product but in reality means until the next significant release comes out; Leopard, OS 10.5.
    You should always be prepared for the possibility that a bugfix release may contain a security patch that significantly modifies and aspect of the file system that may break a disk utility application. In other words you always have to be vigilant with regards to that class of application.
    Jan J.

  • Disk Utility & Repair Disk Permissions & Unknown User on External Seagate

    I have a new iMac running Leopard and don't do stupid things to my mac. I have a couple external Seagate Freeagent drives but 1 of them is giving me a little trouble. So I figure, I'll try to repair disk permissions on it but the problem is when I go into Disk Utility, the Repair Disk Permissions option is NOT available. It's there, I just can't select it; it's grayed out. Why? I'm an admin! The other externals have this option available but not this one, so I'm not really sure what to do. I've about 300gb of family movies on it that I'd rather not wipe out just to be able to do a disk permission repair.
    Whenever I do a command+i on the drive I do see an UNKNOWN user but this article, http://www.pcworld.com/article/145425-1/quickand_easy_folder_sharing_in105.html, leads me to believe that Apple hasn't done jack squat to allow us to fix the problem.
    Thoughts? Suggestions? Thanks in advance!

    mrpeepers wrote:
    I don't think that statement is true.
    I have 3 externals and can repair disk permission on all but 2. All my externals are for storage purposes and non have OSX installed, so that fact that I can repair disk permissions on them sort of contradicts what you say, however, the effectiveness of running a repair disk permission on a drive that doesn't have OSX may be nothing.
    I don't know how you manage to repair permissions on externals without system files on them but what I said is quite true. Repair permissions ONLY checks permissions of system files against the database of correct permissions. It wouldn't know what to do with any other files and never touches them. It should also not be possible on non OS X drives. I've never seen it enabled on any of my external or secondary drives. I really wonder why and how it was enabled on your external drives.
    I did have Tiger installed for 3 months before I got Leopard, but my externals have known nothing but Leopard.
    That doesn't matter. the ownership of files on your external were set in Tiger and it remains in leopard. that's what causes the "unknown" user to show up.
    The problem I'm having with one of the drives is that starting yesterday it's having difficulties mounting. Sometimes I restart the computer and the drive doesn't show. So in order to get it to show, I have to power down the external (which is and appears to be running) and then power it back up, and if that doesn't work, usually reseating the USB works.
    Then again... My problems started happening after I installed CandyBar and applied some folder changes. I have since dumped it.
    whatever problems you have with that external they have absolutely nothing to do with Candy bar. all candy bar does is change a few icon files on your main hard drive. that can have no effect on mountability of anything.
    This sounds to me like a hardware problem with your external. the drive could be failing. the USB bus could be failing either on the drive or on the computer. One thing you could do is check to see if there are any firmware upgrades for that drive. Look at the manufacturer's website. also try testing the drive with another computer if you can.
    On another note... Anyone use CandyBar and NOT have any problems or really like it? Maybe it was just a coincidence.
    yes, I use it and REALLY like it. no problems whatsoever.

  • Repair disk permissions help

    Hello all,
    im fairly new to the macbook and have been reading up on repairing disk permissions as the mac has started to slow down in time
    the problem i have is i opened disk utility
    and ran verrify disk permisions, it found problems, so i restarted and held comand and r and booted into the recovery console
    from there, i chose disk utilities and ran verify disk again, again it found problems, so i ran repair disk permisons, that came  back and repaired succefull,
    so just to check i then vefried the permisons again, and once again it found the same problems, so i then re - repaired the permisions, and again it cam back succefull
    again i double checked and once again it found the same problems , so im going round in a loop here the problems arnt actually properly fixing?
    how can i sort this out?
    any help would be appreciated!
    regards

    Those messages are in fact quite similar to the ones Apple mention in the KB.
    All the examples you posted are instances of the same symptom: the BOM states a given path is supposed to be a directory but it actually is a symlink to a directory.
    A possible cause of this is when something was installed that did not foresee upgrades that would leave multiple versions installed at the same time, then the development team eventually decided that a new version would be needed to co-exist with the old one and such a new version has been installed. The old BOM file still report the directories (or files) as not being symlinks but the new installation actually moved the old data to a directory specific for the old version, installed a new version and then changed the old directory (aka the "unversioned" or "current" path) to a symlink to the latest installation.
    You can safely ignore these differences.
    While in the past running permission repair used to be a very important periodic maintenance routine, nowadays it's rarely needed and even more rarely useful. It still is a good idea to run it right before and after an important operating system patch update, but it's not really necessary.
    It's very common (and has been for a long time) for the tool to report differences, say they have been repaired, and then, if run again, to report the same differences. In those cases you can generally ignore those differences. Only if the repair tool says it failed to repair something you should be concerned.

  • Anyone clean their mac using the disk utility using the repair disk permissions??

    anyone clean their mac using the disk utility using the repair disk permissions??

    No. Threads don't hurt anything. If your computer is not functioning properly perhaps you need to try some basic maintenance. Let's start by having you do this:
    Repair the Hard Drive and Permissions
    Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    Next, try booting into Safe Mode then immediately restart normally. Safe mode is going to take a while so be patient. It's slow.
    Next, create a new user account. Log out of your account then log into the new account. Try using iPhoto and the publishing button. Do they work now?
    If you still have a problem, then do the following. If you don't want to go through the above then just start with the following and forget the others above.
    Reinstall OS X without erasing the drive
    1. Repair the Hard Drive and Permissions
    Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    2. Reinstall Snow Leopard
    If the drive is OK then quit DU and return to the installer.  Proceed with reinstalling OS X.  Note that the Snow Leopard installer will not erase your drive or disturb your files.  After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
    Download and install Mac OS X 10.6.8 Update Combo v1.1.

Maybe you are looking for

  • Master Detail Report for PDF Printing

    Dear All,        While trying to create a master detail report using Oracle APEX 4.2 and BI Publisher. I tried creating report queries and report layout following the below mentioned steps. CREATE TYPE emp_row AS OBJECT (   EMPNO NUMBER(4),   ENAME V

  • How to I go from 3.1 to 2.1

    Having major issues with new update

  • How do i upgrade my 3gs to IOS6?

    I do not see the option to upgrade to IOS 6.  Where is the link?

  • Hi I have apple power mac c4 OSX 10.4.11 and no password

    Hi after purchasing my first ever Apple Mac and feeling totally delighted,  within mins of returning home and setting up it quickly became crushed. The computer requires updates as vulnerable and unsupported with the use of Firefox. Located how to up

  • Frustrated with iTunes app download

    FOr the past week I've been unable to download new apps. Be it free or purchased. I tried changing my cc info n it won't let me because I don't have a none button. I called apple help support and they were unable to help me there too. They said iTune