1st gen Intel Mac running latest updated version of 10.6.8 as of this date
About 10 days ago, I began to get system freezes ..... except for allowing my mouse to move the cursor, the OS completely ignored all other mouse or keyboard inputs, and the only way to recover was to hold down the power switch (or pull the plug). The freezes became more frequent and eventually required me to cycle power and restart in Safe Mode, then do a controlled (software) shutdown, then re-cold start ... the forced power switch shut downs appeared to be degrading the OS.
This behavior me to use Disk Utility to view and repair permissions. When I did, I got all of the (apparently faux) permissions warnings (which 'repair' doesn't fix) that people have complained about in this thread. Specifically I'm getting 74 permissions violations in the following general categories:
- Java class files that were globally executable now globally non-executable and visa versa
- Java libraries with owner access changed from root to an administrative uid
- Apple remote management language directories converted to files ("...should be drwxr-xr-x , they are -rwxr-xr-x", for example)
- Java framework file names that should be direct are now links
- A flashplayer plug-in resource that should only have admin group access has root access, and it should have write access for user and group, but has global read only access
- The SUID warning that started this thread
- /private/var/root/ and two of it's resources having an added ACL
I trust the expert advice in prior posts here: these permissions notices are due to Snow Leopard updates that Disk Utility fails to account for. Ergo, the freeze problem I'm having is unlikely to be related to the permission violations.
However, it is very easy to imagine how all of the name aliasing along with a few privilege changes involving the root could be the work of malfeasance. Furthermore, with 70-some-odd warnings that are now to be ignored, it is extremely difficult to tell if any actually indicate a problem that possibly should be addressed.
I am very unhappy that Apple has apparently chosen not to provide mitigation for this issue.
ps - my original message is an off-topic example to explain how I came to be confused by the faux permission warnings given by Disk Utility and how they can cause someone to lose a lot of time chasing a non-problem. If by chance anyone has a clue about the freeze behavior I'm seeing, please direct me to somewhere I can find out about it.