Skip navigation
This discussion is archived

Repairing permissions after 10.5.8 update extreme oops maybe???

45522 Views 106 Replies Latest reply: Oct 6, 2009 7:54 PM by mascotca RSS
  • Sean Coon Calculating status...
    I don't know if this fixes the problem, but it did for me. I used the combo update and got the same permission issues. I tried using the delta and had the same thing.

    I restarted the computer with the shift key down (safe boot), reinstalled the Combo update. After that was finished, I ran disk utility again to repair disk permissions. It listed the permissions issues. I ran Repair disk permissions again I got this:

    *Repairing permissions for “Macintosh HD”*
    * Reading permissions database.*
    * Reading the permissions database can take several minutes.*


    *Permissions repair complete*


    So far it good for me.
    Macbook Pro, Mac OS X (10.5.7)
  • V.K. Level 9 Level 9 (56,120 points)
    mert wrote:
    mert wrote:
    Idea: has anyone tried doing the 10.5.8 Combo update again (after getting this issue). Does it fix these files up? If yes, then I just won't run Repair Perms after repeating the Combo update.


    I tried re-applying 10.5.8 Combo and it does fix the files.
    If I run "find -x / -perm 000" on the Terminal, nothing comes up.
    Now I just have to remember not to run Repair Permissions until this gets resolved... in 10.5.9??

    you might have to have a long wait for that one. In all likelihood 10.5.8 is the last leopard point update. Snow leopard comes out in September and AFAIK, Apple always freezes the development of older OSes when a new ones comes out. only security updates are issued after that.

    I would suggest you use the method suggested by lobitz above

    http://discussions.apple.com/message.jspa?messageID=9945828#9945828
    Mac Pro 3.2 GHz, Mac OS X (10.5.7), Mac Pro 2.66GHz, powerbook G4 1.5GHz
  • mert Calculating status...
    Thanks Sean. Although, I hope that doesn't mean Disk Utility made all the problem files 000, and is now happy with them that way.

    Could you double check in Terminal...
    You could look over your whole disk: sudo find -x / -perm 000
    (Takes a minute or so to run. If anything shows up, there's still a problem)

    or just check a couple files (here's one):
    ls -l /System/Library/CoreServices/CCacheServer.app/Contents/_CodeSignature/CodeResou rces
    (If the first part of the line is "----------", there's still a problem).

    EDIT: oops, forgot sudo on find command
  • V.K. Level 9 Level 9 (56,120 points)
    Sean Coon wrote:
    I don't know if this fixes the problem, but it did for me. I used the combo update and got the same permission issues. I tried using the delta and had the same thing.

    I restarted the computer with the shift key down (safe boot), reinstalled the Combo update. After that was finished, I ran disk utility again to repair disk permissions. It listed the permissions issues. I ran Repair disk permissions again I got this:

    *Repairing permissions for “Macintosh HD”*
    * Reading permissions database.*
    * Reading the permissions database can take several minutes.*


    *Permissions repair complete*


    So far it good for me.

    before you start celebrating I suggest you run the following terminal command

    sudo find -x / -perm 000

    you'll have to enter your admin password (which you won't see). that's normal. the command will run a long time and list all (if any exist) files on your startup drive with permissions 000. if it returns any output at all you still have problems and the fact that repair permissions returns no errors is actually misleading.

    Message was edited by: V.K.
    Mac Pro 3.2 GHz, Mac OS X (10.5.7), Mac Pro 2.66GHz, powerbook G4 1.5GHz
  • mert Level 3 Level 3 (880 points)
    V.K. wrote:
    lobitz wrote:
    I too experienced this problem after applying the combo update. I then applied the delta update and was left with fewer such anomalies. After also scripting a 'chmod 644' fix to the remaining files I went on to script the following which was executed as root:

    pkgutil --edit-pkg com.apple.pkg.update.os.10.5.8 --volume / --learn "offendingfile_fullpath"

    A subsequent Disk Utility repair permissions showed no remaining problems.


    Thanks. without a fix from Apple this is probably the cleanest way to deal with this. Note that if you used the combo update then in the above command put com.apple.pkg.update.os.10.5.8.combo


    I'm a little nervous about using pkgutil, so, before I use it, could you review for correctness an exact line I should execute? I currently have a fresh Combo-updated 10.5.8 system with nothing reported by "sudo find -x / -perm 000". I did not run Repair Perms yet. I saved the complete list of 000 files from my first update (Combo, followed by Repair Perms). Would I run the following line (all on one line) for each file from my original list of 000 files?

    sudo pkgutil --edit-pkg com.apple.pkg.update.os.10.5.8.combo --volume / --learn "/System/Library/CoreServices/CCacheServer.app/Contents/_CodeSignature/CodeResources"
  • RonL Level 1 Level 1 (45 points)
    This began for me with 10.5.7 and persists with 10.5.8.

    I was hoping that it would be corrected in this new update but it hasn't been.

    Stat... as you show... I also have a very long list each time I repair permissions.

    I have been using Macs for over a decade and professionally and am certain I have done nothing to cause this.

    Fortunately it does not appear to cause any problems.

    I remember many versions back when lots of people had long lists of 'corrected' permissions after each repair but I don't recall it involving core services.
    G5 Tower, Mac OS X (10.5.8), 2 GB RAM; Apple Bluetooth keyboard
  • V.K. Level 9 Level 9 (56,120 points)
    Would I run the following line (all on one line) for each file from my original list of 000 files?

    sudo pkgutil --edit-pkg com.apple.pkg.update.os.10.5.8.combo --volume / --learn "/System/Library/CoreServices/CCacheServer.app/Contents/_CodeSignature/CodeResources"

    yes, that's exactly the command to run. you can get the full list of files you need to run it on by running "verify permissions" instead of repair permissions". verify permissions" only report permissions errors but does not fix any of them so it is safe to run at any time.

    Message was edited by: V.K.
    Mac Pro 3.2 GHz, Mac OS X (10.5.7), Mac Pro 2.66GHz, powerbook G4 1.5GHz
  • mert Level 3 Level 3 (880 points)
    Yes. Agreed, I have seen numerous permission problems from time to time across OS X updates, however, I don't recall one so egregious as to set permissions to 000 (no access, well, except by root).

    EDIT: and in this case, Repair Permissions actually breaks the files. Re-Repair doesn't help either.

    Message was edited by: mert
  • Richard Outerbridge Calculating status...
    The method lobitz suggested (namely, sudo pkgutil --edit-pkg com.apple.pkg.update.os.10.5.8 --volume / --learn "offendingfile_fullpath") works fine, but you must apply it to each and every affected file (remembering to change the name of the package to "com.apple.pkg.update.os.10.5.8.combo" if you need to as pointed out by V.K.). Since there may be package "tainting" happening here (if you have applied the Delta over the Combo or vice-versa) it's hard to know what is going on in the install database, but the --learn method should fix things. You may want to keep the finished script around in case you ever need to use it again.

    That having been said, I don't know if there is actually any harm in running these files with 000 permissions apart from the "?----------" blemishes kicked out by Repair Permissions, even though they seem to have been installed (and thus perhaps intended to be run) "-rw-r--r--".
    PB G4 15 5,8, Mac OS X (10.5.8)
  • Sean Coon Level 1 Level 1 (0 points)
    I typed in sudo find -x / -perm 000 in the terminal and got this:


    Last login: Thu Aug 6 13:29:39 on ttys000
    macpro1:~ macpro$ sudo find -x / -perm 000

    WARNING: Improper use of the sudo command could lead to data loss
    or the deletion of important system files. Please double-check your
    typing when using sudo. Type "man sudo" for more information.

    To proceed, enter your password, or type Ctrl-C to abort.

    Password:
    macpro1:~ macpro$


    It didn't take too long. That's all I got from the terminal command.
    Macbook Pro, Mac OS X (10.5.8)
  • V.K. Level 9 Level 9 (56,120 points)

    That having been said, I don't know if there is actually any harm in running these files with 000 permissions apart from the "?----------" blemishes kicked out by Repair Permissions, even though they seem to have been installed (and thus perhaps intended to be run) "-rw-r--r--".

    I don't know for sure either but it is mighty suspicious. and I'd as soon not take any chances particularly because on my other computer (that I updated just using the delta update) all these files have 644 permissions and repair permissions reports no errors there. as I said, this can't be right. the same system files should have the same permissions on any system after you run repair permissions.
    Mac Pro 3.2 GHz, Mac OS X (10.5.7), Mac Pro 2.66GHz, powerbook G4 1.5GHz
  • mert Level 3 Level 3 (880 points)
  • stylr Level 3 Level 3 (630 points)
    Has anyone had any issues with this situation? Or all we all worried about something that hasn't and may not affect us in any way?
    Macbook Pro Late 2008 and 30 Cinema Display, Mac OS X (10.5.8)
  • mert Level 3 Level 3 (880 points)
    stylr wrote:
    Has anyone had any issues with this situation? Or all we all worried about something that hasn't and may not affect us in any way?

    I can't say I have yet. But, some of the system files in the list seem pretty important. I need to apply this update to 50-some machines, so hopefully, by making sure Apple is aware of it (via the bug report), they can release a definitive statement (KB article) one way or the other.
  • William Steinberg Calculating status...
    Same thing happened to me. MacPro updating from 10.5.7 to 10.5.8 using the manually downloaded combo updater.

    Had to manually shut down when the update was done, after waiting 10 minutes to no avail. Then the usual dual restart after a combo update. Then my usual run of Disk Utility to fix permissions, and like others are reporting, besides the slew of linked files (-l) that show up as permission errors (and don't get fixed, which is OK because they shouldn't be fixed), another slew of files that had normal permissions, but Disk Utility thought "should" have had 000 permissions, according to the receipt files. Unfortunately, due to habit, I had selected repair not verify, so Disk Utility "fixed" all the permissions to 000 (which is wrong).

    Running "sudo find -x / -perm 000" as root turned up this huge list, *+ALL HAVING TO DO WITH _CodeSignatures+*:
    /System/Library/CoreServices/CCacheServer.app/Contents/_CodeSignature/CodeResour ces
    /System/Library/CoreServices/Kerberos.app/Contents/_CodeSignature/CodeResources
    /System/Library/CoreServices/KerberosAgent.app/Contents/_CodeSignature/CodeResou rces
    /System/Library/CoreServices/Screen Sharing.app/Contents/_CodeSignature/CodeResources
    /System/Library/Extensions/IOUSBFamily.kext/Contents/_CodeSignature/CodeDirector y
    /System/Library/Extensions/IOUSBFamily.kext/Contents/_CodeSignature/CodeResource s
    /System/Library/Extensions/IOUSBFamily.kext/Contents/_CodeSignature/CodeSignatur e
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBEHCI.kext/C ontents/_CodeSignature/CodeDirectory
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBEHCI.kext/C ontents/_CodeSignature/CodeResources
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBEHCI.kext/C ontents/_CodeSignature/CodeSignature
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBHub.kext/Co ntents/_CodeSignature/CodeDirectory
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBHub.kext/Co ntents/_CodeSignature/CodeResources
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBHub.kext/Co ntents/_CodeSignature/CodeSignature
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBMergeNub.ke xt/Contents/_CodeSignature/CodeDirectory
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBMergeNub.ke xt/Contents/_CodeSignature/CodeResources
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBMergeNub.ke xt/Contents/_CodeSignature/CodeSignature
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBOHCI.kext/C ontents/_CodeSignature/CodeDirectory
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBOHCI.kext/C ontents/_CodeSignature/CodeResources
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBOHCI.kext/C ontents/_CodeSignature/CodeSignature
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBOpticalMous e.kext/Contents/_CodeSignature/CodeDirectory
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBOpticalMous e.kext/Contents/_CodeSignature/CodeResources
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBOpticalMous e.kext/Contents/_CodeSignature/CodeSignature
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBUHCI.kext/C ontents/_CodeSignature/CodeDirectory
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBUHCI.kext/C ontents/_CodeSignature/CodeResources
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBUHCI.kext/C ontents/_CodeSignature/CodeSignature
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBCompositeDrive r.kext/Contents/_CodeSignature/CodeDirectory
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBCompositeDrive r.kext/Contents/_CodeSignature/CodeResources
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBCompositeDrive r.kext/Contents/_CodeSignature/CodeSignature
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBHIDDriver.kext /Contents/_CodeSignature/CodeDirectory
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBHIDDriver.kext /Contents/_CodeSignature/CodeResources
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBHIDDriver.kext /Contents/_CodeSignature/CodeSignature
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBLib.bundle/Con tents/_CodeSignature/CodeResources
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBUserClient.kex t/Contents/_CodeSignature/CodeDirectory
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBUserClient.kex t/Contents/_CodeSignature/CodeResources
    /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBUserClient.kex t/Contents/_CodeSignature/CodeSignature
    /System/Library/Extensions/IOUSBMassStorageClass.kext/Contents/_CodeSignature/Co deDirectory
    /System/Library/Extensions/IOUSBMassStorageClass.kext/Contents/_CodeSignature/Co deResources
    /System/Library/Extensions/IOUSBMassStorageClass.kext/Contents/_CodeSignature/Co deSignature
    /System/Library/Frameworks/AppKit.framework/Versions/C/_CodeSignature/CodeResour ces
    /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/C oreGraphics.framework/Versions/A/_CodeSignature/CodeResources
    /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCo re.framework/Versions/A/_CodeSignature/CodeResources
    /System/Library/Frameworks/Kerberos.framework/Versions/A/_CodeSignature/CodeReso urces
    /System/Library/KerberosPlugins/KerberosDatabasePlugins/db2.bundle/Contents/_Cod eSignature/CodeResources
    /System/Library/KerberosPlugins/KerberosDatabasePlugins/kldap.bundle/Contents/_C odeSignature/CodeResources
    /System/Library/PrivateFrameworks/DotMacLegacy.framework/Versions/A/_CodeSignatu re/CodeResources
    /System/Library/PrivateFrameworks/DotMacSyncManager.framework/Versions/A/_CodeSi gnature/CodeResources
    /System/Library/PrivateFrameworks/DotMacSyncManager.framework/Versions/A/Resourc es/DotMacSyncHelper.app/Contents/_CodeSignature/CodeResources
    /System/Library/PrivateFrameworks/DotMacSyncManager.framework/Versions/A/Resourc es/dotmacsyncui.app/Contents/_CodeSignature/CodeResources
    /System/Library/PrivateFrameworks/ScreenSharing.framework/Versions/A/_CodeSignat ure/CodeResources
    /System/Library/SystemProfiler/SPDisplaysReporter.spreporter/Contents/_CodeSigna ture/CodeResources

    Everything seemed to work, but I know that permissions for the above files should NOT be 000, so I re-ran the combo updater in Safe Boot mode, loggged in as Root. I also unmounted all the external drives, including the one that holds my normal (non-root) user, which is NOT the boot drive. This 2nd update also hung when it was done and I had clicked the "restart" button, requiring a manual reboot using the power button on the MacPro.

    As expected, a "sudo find -x / -perm 000" turned up nothing (zero files with permissions set to 000), but wonderfully enough, when I then ran Disk Utility in verify mode, no files turned up that Disk Utility wanted to set to permissions 0. (The files with the -l errors still show up, but that's another story, and not a problem). I also manually checked the files in Terminal, and they all have the correct permissions. So it appears that the receipt file(s) are now correct, and a repair run in Disk Utility won't mess them up.

    Just another anecdotal report.

    Billy
    MacPro with two dual cores and 6GB of ram, Mac OS X (10.5.8)
1 2 3 4 ... 8 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.