Permissions anomalies from 10.5.8 Combo-not ones which can be ignored-V.K.?

Question

Level 6

13,220 points

Permissions anomalies from 10.5.8 Combo-not ones which can be ignored-V.K.?

I applied the 10.5.8 Combo over a 10.5.8 originally done from the Delta, then got these unusual "Permissions Differ." Found this discussions thread which suggests these do need to be removed or corrected. Could someone, maybe V.K. who was involved in this earlier discussion, please clarify just what it is I have to do now. This was a very long, complicated thread, and I'm not certain I understand how to proceed. And I wonder if anything since has come to light regarding this issue?

Thanks very much in advance for the help on this.

*EDIT: Read through carefully and just found this. Will try it.*
http://discussions.apple.com/message.jspa?messageID=9951085#9951085

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

http://discussions.apple.com/thread.jspa?threadID=2106528&start=0&tstart=0

Is this the solution here? Not sure I understand the procedure.
http://discussions.apple.com/message.jspa?messageID=9945828#9945828

+2010-02-13 09:01:11 -0500: Permissions differ on "System/Library/PrivateFrameworks/DotMacSyncManager.framework/Versions/A/Resour ces/DotMacSyncHelper.app/Contents/_CodeSignature/CodeResources", should be ?--------- , they are -rw-r--r-- .+
+2010-02-13 09:01:11 -0500: Permissions differ on "System/Library/PrivateFrameworks/DotMacSyncManager.framework/Versions/A/Resour ces/dotmacsyncui.app/Contents/_CodeSignature/CodeResources", should be ?--------- , they are -rw-r--r-- .+
+2010-02-13 09:01:11 -0500: Permissions differ on "System/Library/PrivateFrameworks/DotMacLegacy.framework/Versions/A/_CodeSignat ure/CodeResources", should be ?--------- , they are -rw-r--r-- .+
+2010-02-13 09:01:11 -0500: Permissions differ on "System/Library/CoreServices/CCacheServer.app/Contents/_CodeSignature/CodeResou rces", should be ?--------- , they are -rw-r--r-- .+
+2010-02-13 09:01:11 -0500: Permissions differ on "System/Library/CoreServices/Kerberos.app/Contents/_CodeSignature/CodeResources ", should be ?--------- , they are -rw-r--r-- .+
+2010-02-13 09:01:12 -0500: Permissions differ on "System/Library/CoreServices/KerberosAgent.app/Contents/_CodeSignature/CodeReso urces", should be ?--------- , they are -rw-r--r-- .+
+2010-02-13 09:01:12 -0500: Permissions differ on "System/Library/Frameworks/Kerberos.framework/Versions/A/_CodeSignature/CodeRes ources", should be ?--------- , they are -rw-r--r-- .+
+2010-02-13 09:01:12 -0500: Permissions differ on "System/Library/KerberosPlugins/KerberosDatabasePlugins/db2.bundle/Contents/_Co deSignature/CodeResources", should be ?--------- , they are -rw-r--r-- .+
+2010-02-13 09:01:12 -0500: Permissions differ on "System/Library/KerberosPlugins/KerberosDatabasePlugins/kldap.bundle/Contents/_ CodeSignature/CodeResources", should be ?--------- , they are -rw-r--r-- .+
+2010-02-13 09:01:12 -0500: Permissions differ on "System/Library/SystemProfiler/SPDisplaysReporter.spreporter/Contents/_CodeSign ature/CodeResources", should be ?--------- , they are -rw-r--r-- .+
+2010-02-13 09:01:15 -0500:+
+2010-02-13 09:01:15 -0500: Permissions repair complete+

Message was edited by: WZZZ

iMac G3/400 OSX 10.4.11, iMac G5/1.6 OSX 10.5.8

Posted on Feb 13, 2010 6:51 AM

Reply

Answer 1

TildeBee

Level 7

31,917 points

Feb 13, 2010 7:40 AM in response to WZZZ

WZZZ --

+2010-02-13 09:01:15 -0500:+
+Permissions repair complete+

It is normal after an update to have Permissions notations.
Relax.
It did not say "Repair Permissions Failed."

Reply

Answer 2

WZZZ Author

Level 6

13,220 points

Feb 13, 2010 8:24 AM in response to TildeBee

From V.K.

http://discussions.apple.com/thread.jspa?threadID=2106528&start=0&tstart=0

yes, I've seen it. I applied the delta update on one of my computers and it didn't exhibit such strange permissions messages afterwards. then I applied the combo update on my other computer and it showed such messages as you are seeing.

should be ?--------- , they are -rw-r--r-- .

*I checked and the permissions repair process changes the permissions on all such files to 000 i.e. no permissions to anybody! this is most definitely wrong.* i also checked and the permissions on all such files are most decidedly NOT 000 on my other system with the delta update. In particular I also got the same message as you did

Permissions differ on "System/Library/PrivateFrameworks/ScreenSharing.framework/Versions/A/_CodeSigna ture/CodeResources", should be ?--------- , they are -rw-r--r-- .

I checked the permissions on this file on the system updated using the delta update and they are 644 (i.e. -rw-r--r--) and the repair permissions process reports no errors on that system. I rolled back my other computer to my clone backup and updated it using the delta update and those strange messages went way. I thought it might be just a problem with my system but now that i see your post maybe not...

*Anybody who sees such messages should know that this is NOT normal and should not be left alone.*

Reply

Answer 3

V.K.

Level 9

56,174 points

Feb 13, 2010 10:01 AM in response to WZZZ

right, these ones are actual errors although I don't know how serious they are. the solution is very simple. reinstall 10.5.8 *twice in a row*. do not repair permissions in between installs. then run repair permissions and those kind of messages should be gone.

Reply

Answer 4

WZZZ Author

Level 6

13,220 points

Feb 13, 2010 10:20 AM in response to V.K.

Thanks. Saw that solution after reading through more carefully. Very time consuming, so not looking forward to it. But glad there's some simple solution. Yeah, no one seemed to know if it was innocuous, or what yet-to-be-discovered havoc it might wreak. But haven't noticed anything amiss...yet.

Will give it a try. I wonder if Apple ever responded to the bug report on this, although I'm not holding my breath. 🙂

Reply

Answer 5

V.K.

Level 9

56,174 points

Feb 13, 2010 10:27 AM in response to WZZZ

WZZZ wrote:
Thanks. Saw that solution after reading through more carefully. Very time consuming, so not looking forward to it. But glad there's some simple solution. Yeah, no one seemed to know if it was innocuous, or what yet-to-be-discovered havoc it might wreak. But haven't noticed anything amiss...yet.

Will give it a try. I wonder if Apple ever responded to the bug report on this, although I'm not holding my breath. 🙂

not that I've heard of which is why i suspect those messages are not serious. still they are actual errors and can be removed using this method.

Reply

Answer 6

WZZZ Author

Level 6

13,220 points

Feb 14, 2010 1:27 PM in response to V.K.

Yep, that did it. Took forever, since I did it from Safe Boot. Any idea if I'd have to do that twice back to back if I ever needed to re-apply it again, or you think would one run through would be enough if there's ever a next time?

Reply

Answer 7

V.K.

Level 9

56,174 points

Feb 14, 2010 1:28 PM in response to WZZZ

why did you do it from safe boot?
and you would only need to do it again if you see such errors again. that's not likely unless you are talking about a full system reinstall but yes, if you do have to do it again then you'll have to rerun 10.5.8 combo update twice in a row again.

Reply

Answer 8

WZZZ Author

Level 6

13,220 points

Feb 14, 2010 1:52 PM in response to V.K.

why did you do it from safe boot?

Maybe just voodoo or some kind of superstition, but from my Tiger experiences, any kind of major update was supposed to be less problematic from SB, with third party stuff disabled and not interfering; just the essentials running, I guess. A precaution. Not needed, you think?

Reply

Answer 9

TildeBee

Level 7

31,917 points

Feb 14, 2010 2:20 PM in response to WZZZ

WZZZ --
I'm just curious.
Aside from the permissions report,
was anything actually not working correctly on your Mac?

Reply

Answer 10

WZZZ Author

Level 6

13,220 points

Feb 14, 2010 2:49 PM in response to TildeBee

Too paranoid to give it much of a chance to find out. Didn't notice anything; V.K. said he hasn't heard of any problems directly related. It's just an unknown. Here is one post from that eight page thread that was written from the person responsible for finding the solution. Maybe nothing to worry about, but who knows what might have developed, perhaps much later. Certainly must be a lot of people who installed this, never bother with Permissions, and will probably never encounter any trouble. Who knows, the entire episode might be read as giving more ammunition to the camp that says don't ever repair Permissions.

I was already running 10.5.8 from the Delta. Ran it as a possible fix for something. Don't even know yet if it will help with the problem I was experiencing. I sure won't fool with this buggy thing again.

http://discussions.apple.com/message.jspa?messageID=9956438#9956438

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

Reply

Answer 11

Feb 15, 2010 5:26 AM in response to WZZZ

For the past 2 days I have been battling with Crashes and Lock ups in both the active OS, Windows partition, the Boot cycle and during use of the installation disk to check for Partition faults.

The main problem is a Software conflict which causes a hardware problem which initiates a hardware malfunction which causes a system crash in the OS Software.

The problem seems to originate with the conflicting permissions, My OS (10.5.8)
Showed various permissions problems on disk checking after it locked up and crashed out on Friday during a presentation.

I was using i-Movie at the time showing how tracks could be brought in. I expected either an i-Tunes or i-Movie conflict... But I couldn't check until 6 hours later because the system couldn't get past the boot screen, the thing would lock up with screen aspects over the logo, a classic hardware fault indication, but my hardware had received no external abuse nor had it been damaged.

I put my Mac in the fridge to cool it down after establishing the Temperature may be the problem. This worked, every-time the Mac got too hot the HD data transfer would be interrupted, may have something to do with increased temperature causing more resistance in the wires.

My MacBook Pro has spiked to a massive 97 Degrees C... at some points.

I installed a Cooling app to double the Fan speed, this seemed to stabilize the OS when active but doesn't solve the problem just decreases the crash risk.
It also didn't resolve the issues I have been having with the permissions crashing the OS and sudden lock outs with apps not responding especially EventUserAgent and CoreAudioD being red'd out in the Activity monitor, this may be an indication of what the permissions conflicts are causing...

It even locks up when running the OS install disk, but only after it has crashed out. If I turn the Mac on and then Quickly off again before the crash can happen it will boot fine when I turn it on again, until it either gets to hot that it crashes or it encounters one of the permissions conflicts... Begins to argue with its self over which permission is correct and locks up.

I seem to be stuck in a loop. I reinstall the MacOS 10.5.8 Combo update, Check permissions and fix, but then after a second check nothing has changed more over, it will lock up on a third so I have to repeat the process. Of installing

The worst thing is I have important work to be done and I have been struggling with it for days.

Just when I get the system stable it crashes...
I will try the dual install method and get back to you guys on how it goes.

BTW, the Hardware checks were ALL CLEAR. Also I tested the hardware with the install disc holding D at start up check, All clean.
And
Using the Tech-Tool the MacBook Pro Came with, both agree, the system is faultless... This is an error caused by the OS more specifically the Update itself. I heard so many people talking about this crash but I have only experienced this kind of Lock up scenario when running windows on my Mac using BootCamp... Back when it had stability errors and that also caused heating issues... So far the fan speed increase delays the inevitable...

BRB installing the software twice in a row.

Reply

Answer 12

V.K.

Level 9

56,174 points

Feb 15, 2010 7:34 AM in response to MarxIzalias

please start your own thread. your problem has nothing to do with the subject of this thread.

Reply

Answer 13

Feb 24, 2010 9:44 AM in response to V.K.

10.5.8, Fries the connection to the temperature sensor.

Do not install it.

Reply