Repairing Permissions is a real joke!!!

I thought Leopard was suppose to be better, faster. What's with the 10 minute wait for Repair Permissions to do what it's suppose to.
I can't be the only one seeing this!!!

Tiger has support for ACL's but they are off by default, and the system doesn't use them for anything, so for the most part the standard UNIX permissions are all that are used. Leopard on the other hand, has ACL's enabled, and most of the system folders have extended permissions (usually just a deny delete), so more things need to be checked. Repairing permissions now involves checking for an ACL in addition to the standard permissions, testing against the receipt and .bom files in the Receipts folder, and possibly repairing both. Using the "Apply to enclosed items" on a system folder can also have the unexpected side effect of creating a bunch of ACL's that the system is not expecting, so things can get pretty busy.
Repairing permissions isn't some kind of magic bullet that fixes everything, although sometimes it is hard to tell from some of the posts around here. You shouldn't have to use the repair permissions utility at all, unless there is some kind of problem with them - most just use it for system updates.

Similar Messages

Disk Utility can't repair permissions

For the first time I neglected to repair permissions before security upgrade and now I find I can no longer repair permissions. Everything goes as normal until about 75% done and then it just freezes. I have tried running it from the install CD but it does the same. I used the disk repair and got this error message;
ERROR: The underlying task reported failure on exit (~9972)
1 Volume could not be repaired.
Computer otherwise OK. AHT reported all OK.
Is this the start of an HD failure or some querky software malfunction? Help needed!
G4 867 MDD Mac OS X (10.3.9) Extra 120Gb HD, 1.75Gb SDRAM LG 4163B Superdrive

If my HD has developed a bad sector then surely a clone will not work?
My best guess is that the cloning would fail when it tried to access the data that's referenced in the bad directory node. I've had similar problems when trying to copy files when there were directory problems. You may not have a bad sector per se, but certainly the directory record is damaged in such a way that Disk Utility can't reconstruct the record.
If I moved all my APPS folder to another HD and then did a Zero and format on this one could I then still use the APPS folder with a new install by repairing permissions?
You have to remember that apps store files in other locations - particularly in the /Library, /System/Library/ and /Users/username/Library directories. While you can copy the Applications directory to another drive, you're liable to miss supporting files the apps are going to look for. Since there's no real way to determine what the damaged directory is referencing, you'd be chancing something's going to get missed and leave you with apps that won't run. The only way I've ever been able to find what directory erorrs were pointing to was to copy files to another drive one chunk at a time until I found the offending directory and then narrow down the search by copying files individually. Given the nature of OS X to store files in directories that are otherwise hidden from the user, this can be a complicated and tedious process.
Since Disk Utility running from the install disk can't repair the damaged directoy record, I'd go to the Disk Warrior repair strategy next.
-Douggo

How come I always get the same results when I repair permissions?

When I repair permissions I get the following messages, even if I do it again immediately afterwards:
+Permissions differ on "usr/share/derby", should be drwxr-xr-x , they are lrwxr-xr-x .+
+Repaired "usr/share/derby".+
+Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.+

The message about the ARDAgent is the result of an Apple update to Apple Remote Desktop from awhile ago. If you ran the update, you will get the notice. The "derby" message says that instead of a folder in the /usr/share directory there is now a symbolic link. Since derby is a java gizmo for the Apache web server, and there is a new Java update from Apple (which I haven't run yet, as it requires a restart), it is quite possible that the update makes that change. As Barney noted, Apple has not been good at making changes in the permissions database when they send out updates. The result is that we begin to see these little notes. Initially the database was in complete accord with what the installation had, and there were no warnings at all in Snow Leopard. After the ARD update the SUID warning began, and it is likely the Java update just added another one.
However, the tendency of people to just automatically ignore all warnings all the time, a legacy of the horrible performance of Apple in updating the database in Leopard (where one would get dozens of these things), is I think unfortunate. There can be real errors, some of which could indicate something bad, such as a compromised computer. One really needs to stop and think about which files are showing a warning, and what the warning means, and whether it is the case that all Snow Leopard installations that are fully updated are showing the particular warnings in question.
Francine
Francine
Schwieder

ACL found by repair permissions

OK, here is what we have. Macbook 1 died. Macbook 1 was on Time Machine. Did a restore from Time Machine to MacBook 2. Every since then, when I repair permissions the following comes up:
Repairing permissions for “Macintosh HD”
ACL found but not expected on "private/etc/apache2/users".
Repaired "private/etc/apache2/users".
ACL found but not expected on "Library/Preferences/Audio".
Repaired "Library/Preferences/Audio".
ACL found but not expected on "System/Library/Keychains/X509Anchors".
Repaired "System/Library/Keychains/X509Anchors".
ACL found but not expected on "private/var/db/launchd.db/com.apple.launchd".
Repaired "private/var/db/launchd.db/com.apple.launchd".
ACL found but not expected on "private/var/yp/binding".
Repaired "private/var/yp/binding".
Permissions repair complete
My question is: How do I remove the ACL?
Repair permissions, Disk Warrior, TechTools Pro do not repair.
I would imagine that some place in the "man" pages this information could be found, but I sure cannot find it.
Thanks.
Steve H

First of all, I should point out that I think I understand that these messages are OK to ignore.
Second, I ran your/Kappy's Terminal command suggestion and now the message I should ignore and gone. (yippie) Many thanks to the Florida contingent.
My point is, why should you keep getting the same message, over and over if you should ignore them? If we should ignore them, stop showing them to us. It drives some of us crazy. And for some of us, it's a very short drive.
If you shouldn't really ignore the messages, then either actually do something to address them, or tell us what to do. Which hopefully for most it's not running Terminal commands.
The other thing is, Disk Utility does say it repaired something.
Repaired "private/etc/apache2/users".
Did it really repair something?
If so, why does it constantly repair the same reported issue, over and over?
It appears as if it didn't really repair something.
I'm not trying to be a pain on this issue. lt's just that it seems this is how Disk Utility has worked for some time. I've always wondered why someone at Apple doesn't do something about it.
It's like the old joke, "Doctor it hurts when I do this."
Doctor, "Dont' do that."
Either way, thanks.

How long to repair permissions

Got the grey screen...trying to fix with repair permissions...any idea how long it might take to run the repair....I have a 250G drive with about 120G of it used. I am asking just so I know if at some point I should give up....or just leave it for a while while it does its work.

There is no hard and fast time for repairing permissions - I have a PB running 10.5.2 and it takes almost 45 minutes, but on my intel aluminum iMac also running 10.5.2, it takes 3 minutes.
I generally get impatient when a process stalls as I track it in Activity Monitor and it doesn't do anything for several minutes. An Archive and Install can take as lttle as half-an-hour or the two hours it took you. I'm sorry there's no real answer tyo give you, but machines are variable and so are times.

Excessive CPU activity when Repairing Permissions & Emptying Trash Securely

I've a new Macbook and, when compared to my humble ibook G4, the CPU nears 100% activity in the monitor and the fan whirrs loudly.
One such occasion included the following -
process name: 'instaldb'
user: _installer
real memory: 147MB
virtual memory: 158MB
Msgs received: 70
Msgs sent: 94
I've restarted and - obviously - repaired permissions, to no avail.
I think this overload issue may also include problems I'm having with Logic 8 audio overload, but am not sure.

while that may be true - it doesn't explain how my 1.33Ghz ibook, on 512Mb RAM had no problem performing these routine tasks.
and i have to say, it is pretty alarming when the fan's on full bore and the Activity monitor's peaking!

"repair permissions" isn't actually repairing permissions?

it seems that "repair permissions" isn't actually repairing permissions here.
I've just come home, switched the Macbook and thought I'd verify permissions again.
"Permissions differ on "System/Library/PrivateFrameworks/GraphicsAppSupport.framework/Versions/A/Frame works/QuartzComposer.framework", should be lrwxr-xr-x , they are drwxr-xr-x ."
and
"Permissions differ on "System/Library/PrivateFrameworks/GraphicsAppSupport.framework/Versions/A/Frame works/ImageKit.framework", should be lrwxr-xr-x , they are drwxr-xr-x ."
.... came up. I repaired, rebooted and re-verified. The same two entries came up again.

Where are our Apple gurus?
I can't speak for any gurus, but where I've been is doing other things for the last couple of days because the Apple Discussions software/servers were so seriously messed up that attempting to do anything in AD was quite pointless, and led to having a very bad attitude due to frustration.
As to whether you actually have a problem: as long as everything works, and the real folders are where they are supposed to be, don't worry about it.
This one:
System/Library/PrivateFrameworks/GraphicsAppSupport.framework/Versions/A/Framewo rks/QuartzComposer.framework
Should have the original here:
"/System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuartzCompose r.framework"
It the originals are in place, having extra copies rather than symbolic links doesn't matter. You just have an extra 25MBs of space taken up by duplicate folders.
Francine
Francine
Schwieder

Why do so many items appear after repair permissions.

Something that has never made sense to me is repair permissions. It is suggested that we repair permissions yet so many items reappear in verify. In my case a verify revealed 119 items of concern with one suid warning. Have run repair a number of times yet 60 items remain including the suid warning- Remote Management ARDAgent.
MBP with Snow Leopard 10.6.8

akashelby wrote:
Something that has never made sense to me is repair permissions.
No biggie. Simplifying matters a bit, Apple's Installer leaves behind a list of items installed. "Repair permissions" goes through the system software and checks it against the list. Where it finds that permissions differ, it resets them to the values in the list. Permissions get changed for various reasons, including poorly programmed software and users who know just enough to get into trouble. Fixing permissions is a step which does not require any expertise and, once started, does not require user interaction. That, and, as CT says, the black magic touch, is probably the reason it is so often recommended, even by tech support, although it probably works only in a small number of cases. There's no point in wasting time about the list of specific fixed permissions in this instance -- if Apple says ignore them, do just that. There's enough other stuff we need to worry about.
Now, as to your real problem -- "Finder doesn't find anything". You'll have to provide more details, but it sounds your problem is not so much with Finder as with Spotlight.

Repaired permissions, now TM doing a full backup?

Hi, intelligent user who doesn't have much advanced knowledge concerning what Repairing Permissions even means here.
So I'm planning on replacing my Macbook Pro's HD, and I just finished making a full bootable backup onto a 200GB FW drive using Super Duper, and checked the "Repair Permissions first" option. I figured that having a latest Time Machine backup (1TB Time Capsule) would make sense as well, so before powering down to unscrew the case I did a Back Up Now. It scanned the entire computer and decided that it would backup all 70 GB fresh. I'm assuming this has something to do with having repaired permissions, but I don't quite know what that means. It may be something similar to what recently happened to me, when I erased my whole computer and refreshed from Time Machine, and then on the next backup it did everything over again instead of updating (for that backup I can still browse dates before that happened as long as I start at the root drive).
Anyone know what I could do to fix this?

Brian wrote:
We have to be careful here: there are three different scenarios:
New computer or logic board. Time Machine identifies your computer by it's +Media Access Control address+ (MAC address), embedded in the hardware of the logic board. There is a way that some folks have gotten around this on Leopard after a new logic board, but it's tedious and very easy to mess up (I did that, twice!) per the link in #C8 of Troubleshooting. (It's very dangerous on a different Mac).
That was automated for Snow Leopard, resulting in the Re-Use prompt mentioned in #B5 of Troubleshooting. But, as #B5 specifies, Time Machine usually still does a full backup; the advantage is, Time Machine will delete the old backups normally.
New drive on the same Mac (per the link you provided). I don't believe that works on Snow Leopard, and I've not seen a hack specifically for Snow Leopard posted here.
Full restore (from Time Machine, a "clone", or otherwise) to the same drive on the same Mac. This almost always results in a new, full backup. An Apple engineer said that would stop with Snow Leopard, but obviously didn't. Some real techie UNIX guru decided there ought to be a way to do it; he posted a two-page log here a few months ago, of altering all sorts of things via Terminal, converting UUIDs to hex, etc., and claimed to have made it work. But he did it only as an exercise, and even he wouldn't recommend it, even to expert UNIX types.
. . . I suppose the best way to save space on my Time Capsule (it now has at least 3 copies of my entire system with only very minor differences in the existence of some files) would be to make sure I have all the files I will ever want to have backed up, then delete the old records, which is something I presume wouldn't be too hard, make a fresh backup, then delete whatever I don't think I need right now, knowing it will all be found by scrolling back to July of 2010?
I'd have to agree. It just isn't worth the hassle, or the risk of damaging something that you might not notice for a long time. I have no problem hacking around with most things, but not my backups.
Depending on whether Time Machine made new sparse bundles, it may not be too tedious to delete the old backups. See #12 in Time Machine - Frequently Asked Questions (or use the link in *User Tips* at the top of this forum).

Why can't I delete repaired permissions?

I recently upgraded from Tiger to Snow Leopard. I repaired permissions before and after. For the most part, the upgrade was successful without any major problems. The issue I have is when I repair permissions I can't delete the "history" of fixed permissions ... they clear with the clear history button but as soon as I repair again they all come back and it takes about three times longer to repair permissions than it did on Tiger. Any thoughts ?

First, despite what you'll often read on this site, repairing permissions is a complete waste of time unless you have a permission error involving a system file, which you probably never will. It's not a routine maintenance task, and certainly not something you need to do before or after a system upgrade.
Second, if you do repair permissions, it will always spew false errors, which makes it almost impossible to tell whether there were any real ones.

Problem: I have to run repair permissions to access the internet using safari, firefox or chrome on my mac pro. What can I do to fix the problem once and for all?

This is what I get when I run repair permissions in disk utility. Thanks for any assistance you can give.
Repairing permissions for “Macintosh HD”
Repairing permissions for “Macintosh HD”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pl.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pl.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pl.lproj/MainMenu.nib”
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pl.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pt_PT.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pt_PT.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pt_PT.lproj/MainMenu.nib”
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pt_PT.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pt.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pt.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pt.lproj/MainMenu.nib”
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pt.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/sv.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/sv.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/sv.lproj/MainMenu.nib”
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/sv.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/ru.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/ru.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/ru.lproj/MainMenu.nib”
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/ru.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/no.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/no.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/no.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/no.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/fi.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/fi.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/fi.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/fi.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/da.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/da.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/da.lproj/MainMenu.nib”
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/da.lproj/MainMenu.nib”
Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent” has been modified and will not be repaired.
Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent” has been modified and will not be repaired.
ACL found but not expected on “private/var/db/launchd.db/com.apple.launchd”
ACL found but not expected on “private/var/db/launchd.db/com.apple.launchd”
Repaired “private/var/db/launchd.db/com.apple.launchd”
Repaired “private/var/db/launchd.db/com.apple.launchd”
Permissions repair complete
Permissions repair complete

Would you care to tell us which version of Mac Pro, and which version of OS X, you are running? (It's not always safe to assume that a User is running Lion just because he posted in the Lion Forum.)

Help With Repair Permissions!

Hi All,
I have a June 2009 17" 2.8 UMBP. I keep getting regular Spinning Beach Balls, Lock Ups, Delays and a whole host of Trackpad Issues much like many people are experiencing with the 1.7 Firmware Update which only is supposed to affect the 13" & 15" UBMP Models. I read on another post that Apple recommended to "Verify & Repair Disk Permissions" which I done. The problems still remain and the report in "Verfiy Permissions" is exactly the same (it seems) as that of the "Repair Permissions" and where it says "Repair Permissions Complete" at the end. The "Repair Permissions" Report still says that "Permissions Differ" on all lines - how can they have been repaired if they still differ? I am a novice and not technically aware about Macs so I hope someone can help me. Here is a copy of the report:
2009-07-17 15:10:11 +0100: Verify permissions for “Macintosh HD”
2009-07-17 15:10:23 +0100: Reading permissions database.
2009-07-17 15:10:23 +0100: Reading the permissions database can take several minutes.
2009-07-17 15:13:50 +0100: Permissions differ on "System/Library/Frameworks/CoreVideo.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:13:52 +0100: Permissions differ on "System/Library/Components/AudioCodecs.component/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:13:52 +0100: Permissions differ on "System/Library/Components/CoreMediaAuthoringPrivateComponents.component/Conten ts/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:13:52 +0100: Permissions differ on "System/Library/PrivateFrameworks/CoreMediaAuthoringPrivate.framework/Versions/ A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:13:52 +0100: Permissions differ on "System/Library/PrivateFrameworks/CoreMediaPrivate.framework/Versions/A/CodeRes ources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:13:53 +0100: Permissions differ on "System/Library/QuickTime/AppleProResDecoder.component/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:13:53 +0100: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:13:53 +0100: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTAdvance d.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:13:53 +0100: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTAdvance d.prefPane/Contents/Resources/QTMediaKeys.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:13:53 +0100: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTAdvance d.prefPane/Contents/Resources/QTMime.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:13:54 +0100: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTAdvance d.prefPane/Contents/Resources/QTTransport.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:13:54 +0100: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTPlugIn. prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:13:54 +0100: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTRegiste r.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:13:54 +0100: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTRegiste r.prefPane/Contents/Resources/QTAbout.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:13:54 +0100: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTStreami ng.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:13:54 +0100: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTUpdate. prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:14:31 +0100:
2009-07-17 15:14:31 +0100: Permissions verification complete
2009-07-17 15:14:31 +0100:
2009-07-17 15:14:31 +0100:
2009-07-17 15:14:38 +0100: Repairing permissions for “Macintosh HD”
2009-07-17 15:15:07 +0100: Reading permissions database.
2009-07-17 15:15:07 +0100: Reading the permissions database can take several minutes.
2009-07-17 15:18:32 +0100: Permissions differ on "System/Library/Frameworks/CoreVideo.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:18:33 +0100: Permissions differ on "System/Library/Components/AudioCodecs.component/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:18:34 +0100: Permissions differ on "System/Library/Components/CoreMediaAuthoringPrivateComponents.component/Conten ts/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:18:34 +0100: Permissions differ on "System/Library/PrivateFrameworks/CoreMediaAuthoringPrivate.framework/Versions/ A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:18:34 +0100: Permissions differ on "System/Library/PrivateFrameworks/CoreMediaPrivate.framework/Versions/A/CodeRes ources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:18:35 +0100: Permissions differ on "System/Library/QuickTime/AppleProResDecoder.component/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:18:35 +0100: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:18:35 +0100: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTAdvance d.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:18:35 +0100: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTAdvance d.prefPane/Contents/Resources/QTMediaKeys.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:18:35 +0100: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTAdvance d.prefPane/Contents/Resources/QTMime.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:18:35 +0100: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTAdvance d.prefPane/Contents/Resources/QTTransport.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:18:35 +0100: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTPlugIn. prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:18:35 +0100: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTRegiste r.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:18:35 +0100: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTRegiste r.prefPane/Contents/Resources/QTAbout.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:18:35 +0100: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTStreami ng.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:18:35 +0100: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTUpdate. prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
2009-07-17 15:19:13 +0100:
2009-07-17 15:19:13 +0100: Permissions repair complete
2009-07-17 15:19:13 +0100:
2009-07-17 15:19:13 +0100:
How do I fix things so things do not differ? I am hoping that will then fix the issues I am experiencing with my UBMP!
Thank You,
Suave!

Hi
I think you will find that many people are suffering this very same problem with permissions, it is nothing to be too concerned about and will in all probability disappear after a system update sometime in the future.
There was a similar problem when I had a PowerBook G4 every time you repaired permissions it showed a whole raft of errors which would not go away. Eventually Apple released a system update and they all vanished.
It is not broken and it is not going to impact on the running of the computer in anyway.
I have just got a new MBP and have the same permission problem but my trackpad is functioning perfectly and I don't suffer any spinning beach ball.
I would contact Apple, or go into an Apple Store and seek advice about the trackpad and spinning beach ball as these are probably caused by other problems than permissions being wrong.
Phil

New Mac Mini and Repairing Permissions

I've been having trouble with my Mail program and thought I would repair permissions to see if that would help. I ran disk utility from my internal hard drive and ran repair permissions. Apparently it found several permissions to repair, so I thought I would run repair permissions again and the same list appeared. Running a third time and the same list appeared again.Do these permissions ever get repaired? What do I do from here? Should I repair permissions after booting up off of my original system disk? This Mini is only a couple of weeks old and I'm already having problems with Mail and repairing permissions.
rskover

Thank you Tim but the computer is packed back waiting for TNT to take it back to Apple. I don't have time to play with permissions, the permissions are OK in the old computer.
This is what may have been your problem. The permissions on your old computer may not have matched the new computer. I think you gave up before the penny dropped.
They sell the computers very expensive and I think they would have to improve quality.
I am unsure how that can be one of your gripes as when the cube came out it was way overpriced in comparison to their other desktops. That did not stop your or I getting one then.
Your issue was a software problem not a hardware problem so no matter what kind of mac you had it would have needed troubleshooting.
The quality of the new mac mini far exceeds that of the cube. Try playing 1080P high definition media on your cube, or even 480P for that matter. Try outputting 5.1 surround sound from your cube without the addition of a firewire audio interface.
I know how frustrating it can be when something just does not seem to work. I have encountered this a few times in my work. However sometimes I just have leave it come back with fresh eyes and try other approaches and I succeed.
What you need to appreciate installing an upgrade should be planned for any eventuality. In business upgrades are scheduled to have the minimum impact on the workplace. That being said I have worked 48 hrs solid over a weekend getting systems up for a monday morning. They are not always straightforward.

Repairing permissions - ERROR: NO VALID PACKAGES

I think I may have deleted something important!
I had a bit of a tidy up the other day, mainly deleting printers & fonts that I don't use. But it looks like I may have removed a few important things.
In disk utility, I can no longer repair disk permissions. When I try, I get a box saying;
FIRST AID FAILED
DISK UTILITY STOPPED REPAIRING PERMISSIONS ON "MACINTOSH HD" BECAUSE THE FOLLOWING ERROR WAS ENCOUNTERED:
NO VALID PACKAGES
Is there an easy way of fixing this? Or am I looking at a reinstall of Tiger?

Glad that sorted your immediate problem.
On the face of it I would have thought that none were necessary, as the name of the folder and the fact that they're installer packages for things that have already been installed would seem to indicate that they are not needed. BUT the fact that the loss of one of those files caused a problem with something that can be as important as the ability to repair permissions is pretty clear evidence that the files in there are used for something!
So, I would recommend leaving alone the packages for apps/etc. that are still on your machine, or files that you do not recognize. On the other hand, there are some items (very few, actually) in my receipts folder that I would feel comfortable deleting, e.g. a virus defs package for Norton, which I installed right when I got my MBP, but it utterly failed for reasons I won't go into here, and I actually ran the uninstaller to get rid of it, but clearly it left this little gift for me. And poof, it's gone.
But the majority I would recommend leaving alone. On my HDD the Receipts folder is ~170 MB, so it's not a huge chunk, but of course every little bit adds up!
Hope this helps...

Repairing permissions - Error: No valid packages(?!) Wha?

Computer's been doing strange things lately. Not recognizing my airport signal (none of my neighbor's wireless signals either); not recognizing any printers when time to print; no quicktime playback; some sent and received emails lost in space, etc. So I'm getting ready for an archive and install when I think I'll try repairing permissions first. Verifying disk says volume is fine. But i get an immediate error of no valid packages for repairing permissions. Anyone know what this means and how to rectify it?

First "Try Disk Utility
1. Insert the Mac OS X Install disc that came with your computer, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
3. Click the First Aid tab.
4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
5. Select your Mac OS X volume.
6. Click Repair. Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Verify & Repair if needed, then use Disk Utility's Repair Disk Permissions feature...
http://docs.info.apple.com/article.html?artnum=25751
Where are we now after a reboot?

Repairing Permissions is a real joke!!!

Similar Messages

Maybe you are looking for