Freeze then Permissions Repair "Warning'

I just had my 4 month old iMac completely freeze up after a Software Update. After I restarted I ran Repair permissions and (along with a bunch of other stuff) found the following message:
+Warning: SUID file "System/Library/CoreServices/Finder.app/Contents/Resources/OwnerGroupTool" has been modified and will not be repaired.+
+Group differs on "private/etc/cups", should be 0, group is 26.+
Is this anything I should be worried about?

No. See, Mac OS X 10.5- Disk Utility's Repair Disk Permissions reports issues with SUID files.

Similar Messages

Permissions Repair Warning Explanation Please

Hello Everyone,
It's been a while since I last posted on the Apple forums.
I just installed the Mac OSX 10.6.3 v1.1 Combo Update.
After doing so, I launched Disk Utility and ran "Repair Permissions".
At the very end of the permissions repair log, I found the following warning:
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
Does anyone know what this means, or why it cannot be repaired?
If ARDAgent means Apple Remote Desktop Agent, as I suspect, then I am mystified, because, to my knowledge, I never use Apple Remote Desktop for anything, unless it is possibly used during the Software Update process without my knowledge.
I just want to know who has modified it, and why its permissions can't be repaired.
My computer specs are in my sig below.
Thanks!

Hello Niel. Thanks for your response. I just did some checking, and it appears that Mac users have been reporting this -- and similar messages by Disk Utility -- since at least three years ago when Leopard was first introduced.
In fact, I found a page here on the Apple site called "Mac OS X: Disk Utility's Repair Disk Permissions messages that you can safely ignore".
It can be accessed at the following URL:
http://support.apple.com/kb/TS1448?viewlocale=en_US
So I suppose that, as you have stated, the message can be ignored.

Permissions repair warning message

Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
...what does this mean and is it something I need to be concerned about?

You could try manually re-installing the Apple Remote Desktop 3.2.1 Client software. Then run the Disk Utility and repair permissions to see if the files were replaced with the correct permissions.
-Doug

Preloader Freezes, then 'Unresponsive Script' Warning

Hi folks-
This is my first Edge Animate project.
I have created a simple cross-fading 'slide show' with moving text overlays using the most recent upgrade of Edge Animate 3.0.0. 8 slides. The stage isn't that huge: 748x334 pixels. There is one .png overlay with a transparent interior to create the framing; the 8 slides revealed underneath are all Q50 'saved for web' jpgs averaging under 40kB each. I have used one of the simple preloaders in the included library and published for web.
My problem presents regardless of which browser I use (tried the latest versions of Firefox, IE, Safari, Chrome and Opera), and whether I run the published .html solo (hosted on my server), or embedded in the final web page it's destined for. Also, I get the same result when I use Ctrl-Enter from within Edge Animate to preview in my default browser (Firefox).
The problem is that the preloader gif only runs briefly, then freezes, followed by up to a minute of waiting (sometimes even more) before the first slide appears and the animation begins. Solo'd, it's just the frozen animated gif during the wait. Embedded in the final web page, the whole page, including navigation, is unresponsive until after the wait is over.
Depending on the browser, I will get various warnings. In Firefox I get the 'Unresponsive Script' warning and it identifies the unresponsive scripts as:
http://ajax.googleapis.com/ajax/libs/jquery/2.0.3/jquery.min.js:4
Or
http://ajax.googleapis.com/ajax/libs/jquery/2.0.3/jquery.min.js:5
Or
http://animate.adobe.com/runtime/3.0.0/edge.3.0.0.min.js:166
Or
http://animate.adobe.com/runtime/3.0.0/edge.3.0.0.min.js:45
Sometimes I've selected 'cancel script'; sometimes I've selected 'wait for script to finish'; it doesn't seem to matter which one I select. Sometimes it works immediately after making either selection; In some cases I get the warning message 2-3 times before it finally works.
I've tried both hosting the runtime files myself and on Adobe CDN. I've also tried 'Immediate' and 'Polite' for the preloader. It makes no difference.
I've also disabled all add-ons in Firefox and the result is the same, though it may take less time to recover from the freeze.
I ran a speed test and my current download speed is 13mbps, so I can't believe my paltry image files are taking this long to load...and even if they were, shouldn't the preloader continue to animate during the load?
Has anyone else seen this behavior? I sure am hoping for a solution~!
When I created something similar to this in Flash a couple years ago, it didn't even need a preloader it loaded up and ran so fast...
Quite Puzzled,
bOB

hi bOB,
I know your post has been long time ago, however recently I'm having the same issue you had, except the errors messages you're getting, my preloader stays at the same point unless I hit reload page on the browser and finally loads it. Are you still having the preloader issue even with the most recent Edge Animate version?
Thanks,
Paco

IPhoto 9.6 Yosemite asks to do upgrade and then permissions repair

After the Yosemite upgrade, iPhoto was updated and was all running fine. Could access photos etc. iPhoto previous version was the Mavericks one, so not v7 or before, requiring the Library upgrade tool.
Last night when trying to access iPhoto, it comes up with a message saying the library needs to be upgraded. (https://www.dropbox.com/s/9svb2pc91821sm0/Screenshot%202014-10-24%2014.00.48.jpg ?dl=0)
Ignoring the fact that this doesn't make sense as I have been using this library with the updated 9.6 iPhoto, I then click the Upgrade button. iPhoto starts 'Examining photo library' for a while and then comes back with a message saying the Library cannot be opened and that the permissions need to be repaired. After asking it to repair permissions, it fails and says the file cannot be opened. (https://www.dropbox.com/s/vc3w6c8rh24hpyk/Screenshot%202014-10-24%2014.07.40.jpg ?dl=0)
After trying the following, the symtpoms changed slightly.
1) Restarted the Mac (as you do)
2) Deleted iPhoto and re-installed it (advised in another thread)
3) The file was on an external USB drive, which was Mac OS Extended Journaled (and has been working on there for 2 years), so just in case, I moved it to the main hard disk in the Pictures folder
3) Ran Disk Utility repair permissions just in case, but no errors found in that file. Rebooted and ran again to make sure.
4) Showed Package Contents of iPhoto Library file and moved out the iPhotoLock.data file
After trying all this, it now skips the permission repair option and just goes straight from the upgrade screen to the failed to open screen.
I have now tried the iPhoto Library Manager tool and that opens the Library just fine (version 4.19), which suggests everything is there and working, but that iPhoto has just stopped working. However, if I use iPhoto to open or create other iPhoto Libraries, it works fine, which indicates a problem with the Library itself.
I have also tried opening the file from my iMac (also Yosemite and iPhoto 9.6), but it comes up with the same messages and errors.
Now trying a complete rebuild using iPhoto Library Manager as iPhoto won't open the file to do a rebuild using CMD-Option. This may take days for the 130Gb Library, so just wanted this post up in case anyone else is having similar issues and may have found a solution.
Any and all ideas welcome!
Thanks,
Graeme

Do you still have the original library that you used iPLM to rebuild. I as because I didn't see anywhere that you used iPhoto itself to repair the database. If you still have it try the following:
1 - launch iPhoto with the Command+Option keys held down to open the First Aid window. Be sure to follow the circled recommendation in the screenshot.
2 - run Option #4, Rebuild Database.

Permissions Repair: Warning SUID file issue?

Greetings,
I have been having a sleep issue and an occasional error message that said the Time Machine backup could not be completed so I ran disk utility to repair permissions and this is what it said;
+Verify permissions for “Macintosh HD”+
+Permissions differ on "sbin/restore", should be -r-xr-xr-x , they are -r-sr-sr-x .+
+Warning: SUID file "sbin/restore" has been modified and will not be repaired.+
+Permissions differ on "sbin/rrestore", should be -r-xr-xr-x , they are -r-sr-sr-x .+
+Warning: SUID file "sbin/rrestore" has been modified and will not be repaired.+
+Permissions differ on "sbin/mount_smbfs", should be -r-xr-xr-x , they are -r-sr-xr-x .+
+Warning: SUID file "sbin/mount_smbfs" has been modified and will not be repaired.+
+Permissions differ on "usr/bin/smbutil", should be -r-xr-xr-x , they are -r-sr-xr-x .+
+Warning: SUID file "usr/bin/smbutil" has been modified and will not be repaired.+
+Group differs on "private/etc/cups", should be 0, group is 26.+
+Permissions verification complete+
Any ideas?
Thanks in advance - Scrags

it means that those files have set user id bits which shouldn't be there according to the permissions database. an s-bit makes a command run with the user id of the file for that command rather than the user invoking the command. for example, if you invoke unix restore command from terminal it ought to run as you. however, on your system it would run as root because the file /sbin/restore used to call this command is owned by root and has a user s-bit on it.
as i said this has nothing to do with your sleep issues but you might as well fix it.

Results from permissions repair: Warning...

Warning: SUID file "System/Library/CoreServices/Expansion Slot Utility.app/Contents/Resources/PCIELaneConfigTool" has been modified and will not be repaired.
What is the problem with this result if any?

You always will get a bunch of warnings from repair permissions.
For example,
Disk Utility's Repair Disk Permissions messages that you can safely ignore

After updating to Mavericks, get this during Permissions Repair: Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired"?

Repaired permissions once, got rid of the the previous iTunes errors. Cleared history and repaired again, still get:
Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent” has been modified and will not be repaired.
Any ideas?

I have just started seeing this message and, almost simultaneously, have started to have problems with various different apps crashing for no real reason. Just a coincidence?
For interest, SketchUp crashed with the message
"Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000f7f7fff9"
and QuarkXpress with the message
"Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000"
Am I just punching at shadows or could these be linked?
Hope someone can put my mind at rest.
Cheers....Scotty

Screen saver does not turn on. Have run the disc utility to repair disc permissions. Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.

screen saver does not turn on. Have run the disc utility to repair disc permissions. Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent” has been modified and will not be repaired.
I am running 10.9.1 software
Help Diggs1936

I would try reinstalling.
Reinstall Lion, Mountain Lion, or Mavericks without erasing drive
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair
When the recovery menu appears select Disk Utility. 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 then click on the Repair Permissions button. When the process is completed, then quit DU and return to the main menu. Select Restart from the Apple menu.
Reinstall Mountain Lion or Mavericks
OS X Mavericks- Reinstall OS X
OS X Mountain Lion- Reinstall OS X
OS X Lion- Reinstall Mac OS X
Note: You will need an active Internet connection. I suggest using Ethernet
if possible because it is three times faster than wireless.

After running permissions repair i get the folling msg. Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.

after running permission repair i get the following msg. anyone know how to fix this?
Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent” has been modified and will not be repaired.

As long as the report ends up with 'Permissions repair complete' then, as far as permissions go, you are fine. You can ignore the various statements in the report:
Permissions you can ignore on 10.5 onwards:
http://support.apple.com/kb/TS1448
Using 'should be -rw-r--r-- , they are lrw-r--r--' as an example, you will see the that the permissions are not changed, but the | indicates a different location. This is because an update to Leopard onwards changed the location of a number of system components.
Poster rccharles has provided this description of what it all means:
drwxrwxrwx
d = directory
r = read
w = write
x = executeable program
drwxrwxrwx
| | |
| | all other users not in first two types
| |
| group
|
owner
a little more info
Before the user had read & write. A member of the group had read.
After, only the user had read & write.

Odd warning on permissions repair??

Hi -
Just installed SL and did the permissions repair... got a funny message on the imac (not MBP):
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
Sounds like there is a vulnerability here... I don't have remote anything installed or activated (as least didn't intend to...even back to my mac)
should I worry about this? do anything?
thanks
tom

I see no such report on my system, so I'm guessing you may have done an upgrade from Leo, so this message could be caused by something residual from a Leo system. Such SUID messages are innocuous and can be ignored. Most likely it will recur each time you repair permissions.

How to effect a "Permissions repair" (Adobe F.P.)?

To elaborate, I have an OS X (Snow Leopard 10.6.8) and recently received, like so many others, the "blocked plug-in" message for most of my attempts to view videos, largely on YouTube. I seemed to have succeeded in "uninstalling" the old Adobe F.P. that I had procrastinated updating. Then I installed the latest (hopefully) version: 11.7.700.169 and everything seemed fine. Then I happened to skim an old Apple Support Community dialogue wherein one reader warned
that the last important step was to make and complete a "Permissions repair." I started to follow his steps, but it seemed complicated and when he further warned of "security issues" I got a little gun shy. Anyone who can walk me through this process, I would appreciate it greatly. Thanks, R. from W.

Long version: Save and/or quit your applications & doucuments Go to Applications>Utilities Folder Click Disk Utility.
Click the Volumn (HD) that you want to check.
Click the Repair Disk Permissions button. (Don't worry about verifying)
At the bottom of window when the repairs have finished, you will see the “most important thing”: Permission Repairs Complete The previliges have been repaired or completed on the selected volumn.
Restart your computer (Optional).
Short version: Go to Applications>Utilities>Disk Utility and select your volume and then select Repair Permissions.
Same directions are also in the OS Mac Help Menu.

G5 freezes then won't start

Fellow members,
I am posting this in the Tiger Forum because I am unsure of the source of the problem, hardware or software.
I am experiencing much instability with my G5 (2 hard drives) dual Powermac. Not too long ago it started with the dreaded random freeze. Everything will freeze including the mouse. The only way to shut down is with the power button. On-screen console logs have given no indication of what is going wrong. The frequency of these freezes is perhaps 1 or 2 times a day.
Added to this now is that the Mac won't start after shutdown. By this I mean that it turns on but that's it. I hear the HD starting but nothing else. If I try to Safe boot with the shift key or boot from the installation disk nothing happens. If left in this mode the fans will eventually start to roar. Once in a while I will get to the grey apple screen or will be able to log in, but will freeze once more. In the end the G5 needs to be powered on and off between 10-15 times before I can get a full boot.
I have done the usual checking of software and hardware. This includes repairing permissions, repairing the hard drives, resetting PRAM, changing hard drives, disconnecting everything, running 3rd party hard drive diagnostics, and running the Apple hardware test (including the loop mode). All these either do not prevent the above or indicate the cause.
Before I take it in for repair I was wondering if anyone here had any ideas from a past experience?
Thank you.
Powermac G5 Mac OS X (10.4.8)

Update:
After removing my primary HD (as a security procedure) I lugged the Powermac down to Tek Serve. After taking a number a waiting a good hour, they powered up my G5 and, of course, got the same response: a grey screen with an Apple, period.
Then they hooked it up to an external firewire drive and bingo, it worked. No problems. I was very surprised. Would an external HD work if the logic-board was bad as I had suspected? Their diagnosis, however, was a bad HD (they even said they could hear that something was wrong with it). It was suggested that they replace it and leave it overnight for further testing. Well, I was more than a little skeptical at this point. Not that I wanted the diagnosis to be a bad logic-board, mind you, but the odds of having two HDs (one of which was less than a year old) going bad at exactly the same time, and which have given the exact same results, are not high. I also wanted, more than anything, an answer and solution.
I debated whether I should leave the unit there or lug it back home, detach the "bad" HD and try again to boot only with my primary drive. If the original HD was the culprit would merely detaching it from the unit stop the freezing problems and allow it to boot from the good one? The technician could not answer this one. Since Tek Serve did not have the HD I wanted anyway, and since I could replace the HD myself (probably at a cheaper price too), I decided to try. I took it home, plugged it in, hooked up only my primary drive and got .... the grey Apple again. I then hooked up the "bad" HD but this time I saw the little circle below the Apple but it stopped early. Very frustrated, and now thinking this is the last time before it goes back to the repair shop, I shut it down and tried to power up one last time. Low and behold it finally booted and stayed.
Not knowing if this would last, since it had been freezing consistently for the last few weeks, I ran Drive Genius on my primary. It had many errors that only a rebuild would fix. After it was done I restarted using my primary drive. Hey, no problems - everything is fine. I then ran a battery of tests on the "bad" drive. It came up clean too. Hooking both up did not create any problems either.
It is now four days later and only one freeze on that first day bringing it back from Tek Serve. Remember, this is after weeks of constant daily freezing, difficulty booting, then a few days of no booting at all. All this while both software and hardware tests concluded that nothing was wrong. Does this all make sense? Not to me.

Unsuccessful permissions repair

Hello,
I just used Migration Assistant to transfer some apps over from my G5 to my MacBook. Then, when I tried to throw away some unwanted applications I kept getting asked for my password. So I repaired permissions, but got the following error messages:
Warning: SUID file "usr/libexec/load_hdi" has been modified and will not be repaired
Warning: SUID file "System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources /DiskManagementTool" has been modified and will not be repaired
Warning: SUID file "System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Reso urces/Locum" has been modified and will not be repaired
Warning: SUID file "System/Library/PrivateFrameworks/Install.framework/Versions/A/Resources/runner " has been modified and will not be repaired
Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/readconf ig" has been modified and will not be repaired
Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/writecon fig" has been modified and will not be repaired
Warning: SUID file "usr/libexec/authopen" has been modified and will not be repaired
ACL found but not expected on "System/Library/CoreServices/Dock.app/Contents/Resources"
Warning: SUID file "System/Library/CoreServices/Finder.app/Contents/Resources/OwnerGroupTool" 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"
What does it mean? And what do I do about it?

You can ignore these messages, they are not the cause of any problem.
The messages mean that some of the Apple updates (the 10.5.1 update and the Remote Management Update as it turns out), modified the files in question without telling Disk Utility to expect it. Disk Utility is telling you that it detected the change and isn't going to try and second guess it and perhaps undo and important update, so that if there actually IS something wrong with the permissions on one of these files you would have to correct it manually.
Eventually Apple will put out another update that brings Disk Utility's records back up to date as regards these files.
Leopard has added a Do Not Delete property to your top level folders so that, even if you are logged in as Admin, you will still be asked to authenticate before it lets you delete that stuff.
As long is it is just happening with stuff from your Applications folder (for example) as opposed to personal files you might have on the desktop or in your various document folders, there is no problem -- it is intended behavior. However if it is asking you to authenticate when you try to delete ANY of your personal files then there is an issue -- the Do Not Delete property has been incorrectly propagated to your other files.
--Bob

Clean Install needs Disk Permissions Repaired?

I have just performed a clean install of ML 10.8.2 and performed a Disk Verify which reported back OK. Then I did a Verify Disk Permissions and it found several items that needed repair. I rebooted and ran it again but the same items came back. So I repaired the permissions.
I also had this same problem when I did a clean install of 10.8.1 and both times that was all that was on the disk.
Is this normal? Should I have to do a permissions repair after installing a new OS?

Should I have to do a permissions repair after installing a new OS?
No, and you don't have to. You never need to repair permissions unless you have an indication of a permission error involving system files, which you probably never will unless you do something very unusual. The warning messages are spurious.
Permission repair is an immensely popular, time-wasting ritual that is rarely, if ever, necessary. The one time you can be absolutely sure you don't need to do it is right after installing or reinstalling OS X.

Freeze then Permissions Repair "Warning'

Similar Messages

Maybe you are looking for