Repairing permissions failure

My system crashed this week. I lost all the apps. The whole thing was backed up via Time machine
To get it back into the proper order, I first installed the original OS which was 10.3 The I ran Mac hardware Test, which told me i had 2 bad memory modulesw. I pulled them out, and MHT then told me memory was OK.
Then i ran Disk Warrior from disk. This fixed a very screwed up directory.
Once that was fixed, i installed 10.5.6. After that, my G5 booted up OK, but I had none of my applications nor their library support files. So i did a file-by-file Time Machine recovery, mostly for various application support files plus the apps themselves. Meanwhile, Software Update was telling me to download 10.8. It was a good idea, since i need 10.8 to run Protools. After 2 hours, the 700+ gb file got onto my desktop, but it wouldn't load, citing an install error. I suspected that permissions might be some part of the problem.
I have just run verify permissions and repair permissions. Neither will do their job. Both gave me the message: "The underlying task reported failure on exit."
One thought i have is, because of all this uploading installing, perhaps i am not using the correct version of DU for OS 10.5.6. What i have is 11.1 is that right?
Any advise about how to get disk utility back on track is much appreciated. Is there a good 3rd party permission repair utility that will tell me where the file structure is remiss? At this point, after 3 days of trying to recover from a system wide crash caused by failed memory and trashed directories I am feeling very burned out. My next option is too reinstall by wiping the drive clean. Obviously, I'd prefer not to do that, since ZI feel i am so close to being back in the saddle. Any help is much appreciated.

Try this:
Repairing the Hard Drive and Permissions
Boot from your OS X 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 Installer menu (Utilities menu for Tiger, Leopard or Snow Leopard.) 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. Now restart normally.
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.

Similar Messages

I ran a disk verify & disk repair on my macbook.. both said my system was fine. I keep getting the underlying task reported failure on exit when trying to do disk permission or repair permissions. Also get cant install files in "/applications error. Help

m was fine. I keep getting the underlying task reported failure on exit when trying to do disk permission or repair permissions. Also get cant install files in "/applications error when ever trying to install a driver or update. Help

Hi,
Here's an article for that:
http://support.apple.com/kb/ts1901

Repair permissions Error: The underlying task reported failure on exit, ever since time machine system restore

Recently had to restore system 10.5.8 Leopard startup volume using Time machine. After many hours of migrating additional important databases that were recovered from failing startup drive, everything seemed to be back up and running smoothly on a new WD 1tb Black drive. Right before I run timemachine again to backup the new revised seemingly stable startup volume, I choose to repair disk permissions using disk utility. Repair permissions failed with this error, The underlying task reported faliure on exit. I tried using the OS X DVD to repair permissions, Diskwarrior, Onyx, none are able to reapair the disk permissions. Although everything seems perfect I would imagine that the system will fail eventually. It's strange that I had no problems repairing disk permissions in the past on this particular system that was the most recent backup. What should I do ?

Repair permissions always reports a bunch of stuff. Ignore it if it says it completed successfully.
Also note that is it usually a waste of time (except maybe after a system upgrade).

10.5.4 upgrade failure - can't repair permissions: "no valid packages"

I just ran the 10.5.4 combo updater to upgrade from 10.5.3 but now I can't boot into the main boot drive (get the circle with line through it instead of login screen). Fortunately I have Panther on another drive and was able to boot into it via the Leopard install disk Startup Drive utility. From there I've run Disk Utility and Techtool Deluxe which reports the Leopard drive is okay, but when I run Repair Permissions on that drive I get the following error:
Repairing permissions for “HD One”
Error: No valid packages (-9997)
Permissions repair complete
From the other posts about problems with 10.5.4 upgrade it looks like I have to run an Archive and Install of 10.5.0 again and then upgrade from there, but is there a problem with the drive that I need to attend to first?
Further complicating things is that the Leopard boot drive is a 320gb drive that was partitioned to a 120gb main drive + second using Speedtools ATA Cap drive utility because this G4PM can't recognize larger size drives. So I'm reluctant to do an erase of the main drive and then reinstall of Leopard.
Any suggestions?

I have Panther on another drive and was able to boot into it via the Leopard install disk Startup Drive utility. From there I've run Disk Utility and Techtool Deluxe which reports the Leopard drive is okay, but when I run Repair Permissions on that drive I get the following error:
Repairing permissions for “HD One”
Error: No valid packages (-9997)
Bad move trying to repair a Leopard disk with something from Panther or Tiger. They're not compatible. As for the permissions, the receipts structure is totally different that's why it can't do the job.
As for using the SpeedTools thing, I have no idea. Your best bet is to get another ext FWHD and install Leopard onto to it, use the Migration Assistant to transfer your stuff from the hosed volume, and see if that works. If so, then use Carbon Copy Cloner or SuperDuper! to clone the FWHD installation to the hosed volume.

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

MacBook Pro Hard Drive Repair/Permissions Problems

My MacBook Pro (2.2GHz) wouldn't start. I was getting the grey screen with the Apple logo and the spinning wheel that never stops. Tried zapping the PRAM. Tried holding down the shift key. No luck.
So I finally booted from the Leopard Install CD. No problem. Figured I'd use the Disk Utility to repair the disk. I get the following two problems every time:
REPAIR DISK PERMISSIONS:
Repairing Permissions for "GROOVY"
Error: The underlying task reported failure on exit
REPAIR DISK:
Checking Catalog File
incorrect block count for file pcscd.pub
(it should be 16 instead of 17)
Every time I re-launch the computer, using the Leopard CD, I get the same two problems. Can't repair permissions at all. And I get the same "incorrect block count for file pcscd.pub" error when trying to Repair Disk. Even though Disk Utility appeared to repair that problem (and then recheck it) the last time.
Anyway I was able to use Firewire Target Disk Mode to copy all my files to my PowerMac G4. While I was connected I also used DiskWarrior. Seemed to repair the disk with no problems.
So at this point I've pretty much resigned myself to doing an Archive and Install. Unfortunately I've tried it twice and I keep getting this:
INSTALL FAILED
Mac OS X could not be installed on your computer
The installer could not install some files in "/Volumes/GROOVY". Contact the software manufacturer for assistance.
Click restart to restart your computer and try again.
Now I'm going to try wiping the disk and doing a fresh install. If that doesn't work I guess I'll have to call Apple. Anybody else having similar problems?
Thanks,
LT

As I understand it, you can't fix a failing SMART status. Believe me I tried on my iBook! I was originally under the impression that DiskWarrior and Tech Tool Pro could fix anything, but I now understand that they and Disk Utility can only repair the directory. As it was explained to me, SMART was set up to give warning of hard drive failure so that you could rescue your data before the hard drive dies altogether. You can disable it I think, but that's like putting black tape over the warning light in your car that lights up if you are running out of oil--possible to do, but not a good idea.
So if your SMART status is failing, then the only cure is to replace the hard drive. The hard drive can work for a while, but it's on its way out.
Here's a little background information on SMART status:
http://www.computerhope.com/issues/ch000184.htm
And I hope this was just a rhetorical question!

Can't seem to repair permissions

I am preparing to update to Mavericks. So, I started to verify permissions. There were many inaccuracies; so, I repaired permissions. Pages of corrections. Checked a second time--same list of errors. Booted from separate disk. Repaired again twice. Same list of errors.
After the first failure to repair permissions, I verified the disk. Was told it needed repair. So booted from outside disk and repaired disk. No errors. Then went on to repair permissions with the same result as above.
So, what is this and what should I do about it? Thanks.

Read the threads in the "More Like This Column" over here---------------->

Disk Utility: cannot Repair Permissions, even on Leopard installation disk

After reinstall of iLife '08 and Software Update completed, I ran Repair Disk Permissions. Got an immediate red note "error: The underlying task reported failure on exit (sic)." with a flag: "First Aid failed. Disk Utility stopped repairing permissions on 'Mac HD...' because the following error was encountered: The underlying task reported failure on exit."
I went to my Leopard Installation disk and ran "Repair Disk." No problem found. From the Installation disk, ran Repair Disk Permissions. got the same RED INK comments and flag, First Aid failed.
Restarts don't help. Also, so far I have not found an application which is NOT working despite this Disk Utility problem, happy to report ;-))
Additional background. I was reinstalling iLife to fix iPhoto after a clean reinstallation of Leopard and reincorporation of files and apps vis Time Machine. It had been several weeks and iPhoto appeared to be the only app which was not quite right.

Disk Repair can trigger "underlying task" but I've never heard or seen a Permissions Repair do so.
You should never use the DVD to repair permissions. You should be using the same OS version. And of course you can always repair permissions from your boot drive; or from backup/clone or alternate "emergency" drive. Otherwise, the DVD and older version of DU will be wrong.
I know I read that on MacFixit, but I am not sure I bookmarked it.
Don't rely on Apple First Aid, even a clean bill of health doesn't mean there aren't problems which Disk Warrior can deal with.

Repair permissions is stalling

Repair permissions is stalling at the same point on a MacBook running 10.6.7. The last entry in the repair history says:
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
I have repaired the disk using the install DVD, but same problem. Any ideas> Thanks in advance.

Hi pcalvin,
It is some very interesting stuff that Disk Utility uses when verifying permissions - it may freeze but don't be fooled. That error should normally appear: ARDAgent.app is Apple's Remote Desktop Agent that allows a network admin to acces a Mac remotely with Apple Remote Desktop.
From the installation disc, try running 'Repair Disk' again and leave it run; if a serious error is found but can be fixed, you are looking at a time of up to one-to-two hours to fix. Disk Utlility will do its best to find out and repair whats wrong.
Be warned however that this may indicate a serious HDD failure: so make sure you have backed up!
If, after, a couple of hours it has not changed, you may need to replace the HDD inside your Mac.

Post 10.5.8 Update - can't repair permissions on external HD

Just had a rocky time updating to 10.5.8 on my iMac. Install took a long time and did 2 restarts.
Once back in business, Time Machine failed to back up saying I didn't have write permissions on my external WB 160GB drive connected by USB. Checked Get Info and indeed it had changed to read only permissions. This volume had worked with TM fine since it was connected in Feb this year.
A restart restored Read/Write and TM ran successfully, but took a long time to back up 1.3GB. Thought I would do repair permissions on this drive but both Verify and Repair disk permissions are greyed out.
It may be that they've always been greyed out and I've never noticed or checked?
Can advise whether this is normal to be unable to verify/check permissions on an external USB HD please??
thanks,
M

You cannot repair permissions on a non-startup drive because there are no permissions to repair. You can, however, repair the drive were it suffering some kind of directory failure.

Repair permissions always via install dvd?

Seems that always when I repair permissions (I do it once a week and with every major install) there are the same permissions that are "wrong" every time. And the list seems to get longer.
I always repair just by starting Disk Utility and repairing - without booting from the install dvd. Is that wrong? Should I really do the repair permissions always from the dvd? (Like the app seems to suggest.)
Is there any use doing the task just from the active system or is it really useless?
Please tell me the "most pro way of cleaning up my system".
And as former PC Windows user - why is there no "Find disk errors" type of app? Does Repair Permissions repair disk errors as well?
Thanks for advice!

Hello-
I don't claim to be a 'tech expert' but my understandings seem to work for me. If I'm wrong, I'd be just as interested in other opinions as yourself, so FWIW;
Seems that always when I repair permissions (I do it
once a week and with every major install) there are
the same permissions that are "wrong" every time. And
the list seems to get longer.
The list you see doesn't mean that anything was wrong, just set to something other than what the original permissions called for. If there is a problem you will usually get a red listing indicating a failure of some sort. Although the value of arbitrarily repairing once a week if no OS/app installs or upgrades is questioned by many, the consenus opinion seems to be "it can't hurt".
I always repair just by starting Disk Utility and
repairing - without booting from the install dvd. Is
that wrong? Should I really do the repair permissions
always from the dvd? (Like the app seems to
suggest.)
As I understand it, you are doing the right thing. Some rather knowledgeable folks actually say this is the 'better' way because your version of the OS has most likely been updated to something newer than what's on the Install CD. IOW, you should Repair Disk Permissions based on the same OS version you are repairing.
Please tell me the "most pro way of cleaning up my
system".
There really isn't that much that needs to be done other than following the suggested 'proactive' approach pertaining to perm. repair, standard cache maintenance (if you run your system 24/7 it's automatic, or you can run the routines manually if your comfortable with Terminal. Otherwise, a utility like OnyX -free- is readily available.)
As long as you aren't constantly downloading, installing & removing every piece of junk you can get your mouse on you should be OK.
And as former PC Windows user - why is there no "Find
disk errors" type of app? Does Repair Permissions
repair disk errors as well?
Repair Perms doesn't, but the OS does a much better job than Windows, which needs such a utility because it creates the errors in the first place. Disk Utility does include a Repair Disk function which requires starting up from a different boot disk, but it doesn't need to be used as a matter of 'routine' maintenance.
In the event you do run into problems, these Discussions are one of the most invaluable resources available to you. Don't hesitate to ask & you'll get some excellent advice & guidance on any situation you may encounter. Just wait for considered responses before taking any response at face value.
Regards |:>)

Disk utility repair permissions stops altogether

I tried running Disk Utility Repair permissions and received a grey message box saying it stopped repairing permissions because of the following error:
Error: The underlying task reported failure on exit.
This same error message was repeated in the usual information box that disk utility uses to provide detail about what it is doing.
I believe the problem occurred because I selected Macintosh HD and added another user (myself) to read/write in the disk permission section of the information window, and I also applied that to all enclosed items. I did this in the first place because of repeated attempts and failuire to install the latest version of skype into my applications folder (being told that I didn't have enough permissions to complete the overwrite task). When I tried verifying the disk I received the error message "ERROR: could not freeze volume permissions denied"
I switched users to a specific administrator account that I reserve for troubleshooting, but got the same result when I tried running disk utility.
As a not unrelated issue when I attach my ipod touch, itunes says that it cannot recognize this ipod, then after about the third time simply doesn't acknowledge my itouch exists.
everything was working well until i did this large change permissions operation.
So does anyone have any idea what I have done (wrong) and how I can fix it?
thanks
John

John Fountain wrote:
I believe the problem occurred because I selected Macintosh HD and added another user (myself) to read/write in the disk permission section of the information window, and I also applied that to all enclosed items.
Uh-oh. You completely trashed your whole system by doing that. Boot up from your Leopard DVD and restore that last Time Machine backup that was made before you made that mistake. If you don't have any backups you will have to reinstall Leopard.
I did this in the first place because of repeated attempts and failuire to install the latest version of skype into my applications folder (being told that I didn't have enough permissions to complete the overwrite task).
When that happens, just trash the old application first, then drag in the new one.
When I tried verifying the disk I received the error message "ERROR: could not freeze volume permissions denied"
I switched users to a specific administrator account that I reserve for troubleshooting, but got the same result when I tried running disk utility.
Changing permissions on the HD and applying to enclosed items hosed your whole system. That's what's causing all your problems. It's doubtful that you will be able to repair it. Restore your system from backup, or reinstall.

Repairing permissions - repeated problems

I've been trying to install Leopard for a few dayson my emac.
Due to getting spurious 'damaged disk' messages, I've tried it using the installer disk in the emac itself, in an external DVD drive and connected via firewire to my ibook.
I managed to install it eventually,and then couldn't repair permissions.
I decided to erase and install, and I've come up against it again: trying to repair permissions, the disk utility still says repeatedly 'the underlying task reported failure on exit'. This is on a newly-erased hard disk, just-installed version of 10.5.1, nothing else done to the computer since then.
Any clues?

I ran repair permissions again a few more times, and it finally worked.
Then I decided to restart to install 10.5.2.
I got a kernel panic, which repeated every time I tried to startup.
Eventually, I decided to erase and install, again, after running DiskWarrior too, and now I'm getting the 'damaged media' message in various forms.
I can't believe it's meant to be this difficult.

Problems repairing permissions on leopard

every time I try to repair permissions from disk utility I receive the following message: "The underlying task reported failure on exit". Can anyone tell me how I can get around this issue??? One interesting thing is that it sometimes gets to repair some permissions before displaying the error, while sometimes it just fails before repairing anything.. Have tried this from the mac os x disc with the same results. People help!!!!

I expect you've found the 10 minute Repair problem with DU? I think this is just another aspect of that, which should be fixed with 10.5.1, due out in a couple of weeks. Hang in there. In the mean time, download Onyx, and use it to repair permissions. I wouldn't get too jacked over this.

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.)

Repairing permissions failure

Similar Messages

Maybe you are looking for