Repairing Permissions in Leopard. What's Wrong?

Discussion in 'Mac Basics and Help' started by thewhitehart, Nov 2, 2007.

  1. thewhitehart macrumors 6502a

    thewhitehart

    Joined:
    Jul 9, 2005
    Location:
    The town without George Bailey
    #1
    I can't seem to repair permissions using Disk Utility in Leopard. It just hangs at the candy cane bar.

    The status box says:

    "Repairing Permissions for Macintosh HD"
    "Stopped by User" (After I purposely stopped it when it hung for so long)
    "Permissions repair complete"

    Does that just mean that there were no broken permissions? I replicated this problem on an iMac core duo with a clean install of leopard, and an ibook G4 with an upgrade install of Leopard.
     
  2. Hard-Hat-Mac macrumors regular

    Joined:
    May 18, 2007
    Location:
    Philly Burbs
    #2
    Mine took forever the first time. I just walked away and did some junk came back and it found two errors. I hit repair and again it took about 30 minutes to repair.
     
  3. zakatov macrumors 6502a

    zakatov

    Joined:
    Mar 8, 2005
    Location:
    South Florida
    #3
    Don't wanna sound rude, but what don't you get about "Stopped by User"?? It means it didn't finish because you stopped it. It didn't freeze, it was checking permissions, and it didn't find any before you stopped it.

    Let the damn thing finish
     
  4. psychofreak Retired

    psychofreak

    Joined:
    May 16, 2006
    Location:
    London
    #4
    In Leopard, Disk Utility takes ages to repair permissions, not going into the progress bar (just staying on the striped candybar)...you have to be patient and hope 10.5.1 brings a fix...
     
  5. thewhitehart thread starter macrumors 6502a

    thewhitehart

    Joined:
    Jul 9, 2005
    Location:
    The town without George Bailey
    #5
    Thanks. I naturally thought something was wrong because of the candy bar stripe hanging, when Tiger's progress was near instantaneous. I've already had Disk Utility become unresponsive in Leopard, so for the third poster I think it was reasonable for me to suppose the process would never proceed. That's why I stopped it.
     
  6. Plymouthbreezer macrumors 601

    Plymouthbreezer

    Joined:
    Feb 27, 2005
    Location:
    Massachusetts
    #6
    Uh, no.

    I got the same error too, and I stopped nothing. In fact, I left my MacBook Pro alone and came back to find this.

    Rude, yes.
     
  7. andy721 macrumors 6502a

    andy721

    Joined:
    Sep 29, 2007
    Location:
    FL
    #8
    haha

    I thought I was the only one with this problem.
    I hope the update 10.5.1 fixes this bug.:mad:
     
  8. itickings macrumors 6502a

    itickings

    Joined:
    Apr 14, 2007
    #9
    After reading the forums with this topic popping up regularly, I somethimes think I'm the only one without this problem. :p

    Granted, it's slower than in Tiger and consumes a lot of CPU and RAM, but both verifying and repairing works and finishes in a reasonable amount of time.
     
  9. andy721 macrumors 6502a

    andy721

    Joined:
    Sep 29, 2007
    Location:
    FL
    #10
    It used to take a few minutes but a week later it's been taking 10-30mins.
     

Share This Page