This discussion is locked
Stat
Level 1 (0 points)

Q: Repairing permissions after 10.5.8 update extreme oops maybe???

Ok I understand that there is still the issue of Repairing permissions regarding hard code links no big deal. Apple still has not fixed this in this update.

The problem that I have at the moment is understanding why the dbase is not updated properly it appears.

After applying the update to two separate machines both intel based and running Repair permissions through Disk Utility which is what I always do after any os update, there were some very strange oddities that pertains to core files and even after reboots and rechecking seferal times there is no change.

Someone at Apple messed up I think and did not update the permissions dbase during or after the update. I also used the Combo updater versus the smaller regular update as I always do to to avoid some intermittent occasional install problems some tend to see when using the smaller updaters.

Anyone else seeing this and how big of an issue is it to have it show for core files permissiona "should be ?--------- ," ??

Below is an example and is on both an iMac 24" and a MacBook Pro:

Reading permissions database.
Reading the permissions database can take several minutes.
...... I cut out the standard stuff we are used to seeing with the links "l" permisions

Permissions differ on "System/Library/Frameworks/AppKit.framework/Versions/C/_CodeSignature/CodeResou rces", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/_CodeSignature/CodeResources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/_CodeSignature/CodeResources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/DotMacSyncManager.framework/Versions/A/_CodeS ignature/CodeResources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/DotMacSyncManager.framework/Versions/A/Resour ces/DotMacSyncHelper.app/Contents/_CodeSignature/CodeResources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/DotMacSyncManager.framework/Versions/A/Resour ces/dotmacsyncui.app/Contents/_CodeSignature/CodeResources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/DotMacLegacy.framework/Versions/A/_CodeSignat ure/CodeResources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/_CodeSignature/CodeDirecto ry", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/_CodeSignature/CodeResourc es", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/_CodeSignature/CodeSignatu re", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBEHCI.kext/ Contents/_CodeSignature/CodeDirectory", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBEHCI.kext/ Contents/_CodeSignature/CodeResources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBEHCI.kext/ Contents/_CodeSignature/CodeSignature", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBHub.kext/C ontents/_CodeSignature/CodeDirectory", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBHub.kext/C ontents/_CodeSignature/CodeResources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBHub.kext/C ontents/_CodeSignature/CodeSignature", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBMergeNub.k ext/Contents/_CodeSignature/CodeDirectory", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBMergeNub.k ext/Contents/_CodeSignature/CodeResources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBMergeNub.k ext/Contents/_CodeSignature/CodeSignature", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBOHCI.kext/ Contents/_CodeSignature/CodeDirectory", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBOHCI.kext/ Contents/_CodeSignature/CodeResources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBOHCI.kext/ Contents/_CodeSignature/CodeSignature", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBOpticalMou se.kext/Contents/_CodeSignature/CodeDirectory", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBOpticalMou se.kext/Contents/_CodeSignature/CodeResources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBOpticalMou se.kext/Contents/_CodeSignature/CodeSignature", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBUHCI.kext/ Contents/_CodeSignature/CodeDirectory", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBUHCI.kext/ Contents/_CodeSignature/CodeResources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBUHCI.kext/ Contents/_CodeSignature/CodeSignature", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBCompositeDriv er.kext/Contents/_CodeSignature/CodeDirectory", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBCompositeDriv er.kext/Contents/_CodeSignature/CodeResources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBCompositeDriv er.kext/Contents/_CodeSignature/CodeSignature", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBHIDDriver.kex t/Contents/_CodeSignature/CodeDirectory", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBHIDDriver.kex t/Contents/_CodeSignature/CodeResources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBHIDDriver.kex t/Contents/_CodeSignature/CodeSignature", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBLib.bundle/Co ntents/_CodeSignature/CodeResources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBUserClient.ke xt/Contents/_CodeSignature/CodeDirectory", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBUserClient.ke xt/Contents/_CodeSignature/CodeResources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBUserClient.ke xt/Contents/_CodeSignature/CodeSignature", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBMassStorageClass.kext/Contents/_CodeSignature/C odeDirectory", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBMassStorageClass.kext/Contents/_CodeSignature/C odeResources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Extensions/IOUSBMassStorageClass.kext/Contents/_CodeSignature/C odeSignature", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/CoreServices/CCacheServer.app/Contents/_CodeSignature/CodeResou rces", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/CoreServices/Kerberos.app/Contents/_CodeSignature/CodeResources ", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/CoreServices/KerberosAgent.app/Contents/_CodeSignature/CodeReso urces", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/Frameworks/Kerberos.framework/Versions/A/_CodeSignature/CodeRes ources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/KerberosPlugins/KerberosDatabasePlugins/db2.bundle/Contents/_Co deSignature/CodeResources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/KerberosPlugins/KerberosDatabasePlugins/kldap.bundle/Contents/_ CodeSignature/CodeResources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/SystemProfiler/SPDisplaysReporter.spreporter/Contents/_CodeSign ature/CodeResources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/CoreServices/Screen Sharing.app/Contents/_CodeSignature/CodeResources", should be ?--------- , they are -rw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/ScreenSharing.framework/Versions/A/_CodeSigna ture/CodeResources", should be ?--------- , they are -rw-r--r-- .

Permissions repair complete

G5, MBP. MB, and iMac 24", Mac OS X (10.4.11), Also 10.5.8 in some intel machines

Posted on Aug 5, 2009 7:22 PM

by Gerben Wierda,Solvedanswer
Gerben Wierda Gerben Wierda
Level 2 (185 points)
Mac OS X
A:
I think this is what happens:
- For files not installed yet, their permissions (and owner) are taken from nonexisting files during the update process and stored in the package Receipts (Base system). Obviously, the combo drive may affect more files.
- Installing the update twice +without repairing permissions between+ re-reads permissions from the files which at that point are available and the receipts are fixed.

I have tested this and it works. If you install the update twice without repairing permissions in between, the permissions database does not have the permission-000 settings for the files.

Posted on Aug 6, 2009 10:53 PM

Close
Stat

Q: Repairing permissions after 10.5.8 update extreme oops maybe???

  • All replies
  • Helpful answers

first Previous Page 5 of 8 last Next

  • by netnothing,

    netnothing netnothing Aug 7, 2009 6:51 AM in response to Stat
    Level 1 (65 points)
    Wireless
    Aug 7, 2009 6:51 AM in response to Stat
    So what exactly is the CodeResources?

    The permissions being affected aren't he Apps themselves, but this CodeResources file.

    Anyone have any new info on whether this is even an issue?

    -Kevin

  • by mert,

    mert mert Aug 7, 2009 6:53 AM in response to mert
    Level 3 (880 points)
    Aug 7, 2009 6:53 AM in response to mert
    mert wrote:
    I'm off to try the back-to-back combo install (I was too nervous to mess with pkgutil). If double install works - and it sounds like it does for many folks - that seems like be a more "gentle" fix than using pkgutil.


    This appears to have worked. Verify Permissions no longer reports file that should be changed to ----------.

    Nice job Gerben!

  • by Gerben Wierda,

    Gerben Wierda Gerben Wierda Aug 7, 2009 8:22 AM in response to mert
    Level 2 (185 points)
    Mac OS X
    Aug 7, 2009 8:22 AM in response to mert
    If my idea about the cause is correct, if you have run a single install followed by a repair permissions, a double install after that (so a triple install in total) could fix that too. As I did not repair permissions after the first install, I cannot check this.

    Note, if I am correct, install-repair-install will have correct files, but the permissions database will still be wrong.

    So, I am only certain that install-install prevents the problem by creating a good permissions database when the second install is executed.

  • by lkrupp,

    lkrupp lkrupp Aug 7, 2009 8:43 AM in response to Gerben Wierda
    Level 5 (4,235 points)
    Mac OS X
    Aug 7, 2009 8:43 AM in response to Gerben Wierda
    Gerben Wierda wrote:
    If my idea about the cause is correct, if you have run a single install followed by a repair permissions, a double install after that (so a triple install in total) could fix that too. As I did not repair permissions after the first install, I cannot check this.

    Note, if I am correct, install-repair-install will have correct files, but the permissions database will still be wrong.

    So, I am only certain that install-install prevents the problem by creating a good permissions database when the second install is executed.


    I can confirm your theory. Initially I performed a repair-install-repair and wound up with the permissions "?" as described. I've been running this way since day one without any apparent issues. Everything is fine. Taking your advice I booted from an external drive and applied the 10.5.8 Combo update twice in a row without repairing permissions in between. Verifying permissions shows the "?" permissions issue gone, just like you predicted.

    Are you saying that repairing permissions going forward will or will not cause the issue to return? Thanks for your work in this matter, by the way. It is appreciated by all.

    Message was edited by: lkrupp

  • by mert,

    mert mert Aug 7, 2009 9:56 AM in response to lkrupp
    Level 3 (880 points)
    Aug 7, 2009 9:56 AM in response to lkrupp
    lkrupp wrote:
    ...Taking your advice I booted from an external drive and applied the 10.5.8 Combo update twice in a row without repairing permissions in between.


    I don't believe it is necessary to boot from an external drive. I think the only key is doing the Combo install twice, without a Repair Perms in between. After the second install completes, future Repair Perms should not cause problems (and, you can verify this, by running Verify Permissions prior to Repair Permissions... there should be no reports of files needing to be changed to ----------, aka 000).

  • by Gerben Wierda,

    Gerben Wierda Gerben Wierda Aug 7, 2009 2:07 PM in response to lkrupp
    Level 2 (185 points)
    Mac OS X
    Aug 7, 2009 2:07 PM in response to lkrupp
    No, if my theory is correct, the issue will not return by itself and certainly not for the same files. You can run repair permissions from now on, the database is OK and the files are in place, so the database won't get corrupted again because of nonexisting files.

    A new update could have the same problem, though. But with different (new) files.

    External booting is not necessary in all of this, I think.

  • by lkrupp,

    lkrupp lkrupp Aug 7, 2009 3:22 PM in response to Gerben Wierda
    Level 5 (4,235 points)
    Mac OS X
    Aug 7, 2009 3:22 PM in response to Gerben Wierda
    Thanks you so much. Applying the combo update from an externally booted drive seems to go faster and you don't have the double restart to wait through. That's the only reason I tried your fix using that method.

  • by netnothing,

    netnothing netnothing Aug 7, 2009 3:34 PM in response to Stat
    Level 1 (65 points)
    Wireless
    Aug 7, 2009 3:34 PM in response to Stat
    So....does anyone know what problems this MAY cause?

    Is there any reason to fix these?

    -Kevin

  • by netnothing,

    netnothing netnothing Aug 7, 2009 4:45 PM in response to Stat
    Level 1 (65 points)
    Wireless
    Aug 7, 2009 4:45 PM in response to Stat
    Same permissions problem happened to both my Mac Pro and MacBook, installed the combo update, checked permissions, and it set all the permissions incorrectly. Can't say I saw any problems from this, but decided to fix it.

    Anyway, I did the following to solve it on my MacBook (like others have suggested):
    1) installed the Combo 10.5.8 update again
    2) VERIFIED permissions - still incorrect
    3) installed the Combo 10.5.8 update again
    4) VERIFIED permissions - this time permissions correct
    5) REPAIRED permissions - everything still correct

    Hope this helps.

    -Kevin

    Message was edited by: netnothing

  • by KJK555,

    KJK555 KJK555 Aug 7, 2009 8:08 PM in response to Stat
    Level 4 (2,895 points)
    Aug 7, 2009 8:08 PM in response to Stat
    Reapplying the Combo update back to back should cause no problems, I've done this in the past with other contrary updates
    with no ill effects.

    Kj

  • by Gerben Wierda,

    Gerben Wierda Gerben Wierda Aug 8, 2009 12:11 AM in response to netnothing
    Level 2 (185 points)
    Mac OS X
    Aug 8, 2009 12:11 AM in response to netnothing
    What problems may arise? This all depends on the actual files affected. Even if in this case there are not many problems, I have noticed in the past that some parts of Mac OS X become rather unpredictable in situations like these. As a developer I have experienced that wrong permissions on files in /System had unexpected results for the actual working of core technologies. So, for instance, an app experienced unexpected behaviour and a repair permissions fixed that. For me, therefore, repair permissions is the first action to take when I am experience system problems and in many (if not most) cases it fixes my problem. I have concluded over the years that Mac OS X is sensitive for the permissions to be correct (might be the price to pay for a somewhat higher level of security

  • by macwiz1220,

    macwiz1220 macwiz1220 Aug 8, 2009 12:15 AM in response to Gerben Wierda
    Level 4 (1,940 points)
    Aug 8, 2009 12:15 AM in response to Gerben Wierda
    I don't think OS X's file permissions sensitivity is an OS X specific thing. I have seen OSes of all types, Linux, OS X, Windoze get pretty messed up due to bad permissions. Most other OSes, afaik, don't have a frontend for fixing them, so users aren't always aware of permissions.

  • by KJK555,

    KJK555 KJK555 Aug 8, 2009 2:15 AM in response to macwiz1220
    Level 4 (2,895 points)
    Aug 8, 2009 2:15 AM in response to macwiz1220
    You are right macwiz:
    Many a Windows user reloaded XP thinking files were corrupt, when actually it was actually permissions
    issues instead.

    Kj

  • by RonL,

    RonL RonL Aug 9, 2009 4:13 PM in response to Stat
    Level 1 (45 points)
    Aug 9, 2009 4:13 PM in response to Stat
    Bump

  • by Count Rockula,

    Count Rockula Count Rockula Aug 10, 2009 8:30 AM in response to Stat
    Level 2 (210 points)
    Aug 10, 2009 8:30 AM in response to Stat
    man, after reading this... it makes me worry that perhaps I shouldn't apply this combo update just yet. This thread got geeky fast, and it shouldn't be this difficult! I don't want to deal with the same sorta solution.

    So, has it been determined that the combo update I just dl'd from apple is the same exact one everyone has had trouble with? Or has apple fixed this already? I don't suppose that Apple can "patch" an update that had something wrong with it, and still call it 10.5.8 can they?
first Previous Page 5 of 8 last Next