ITunes 6.0.2 and Permission Repair

Question

Just a note for the masses...
After I installed iTunes 6.0.2 and QT 7.0.4 on my Powerbook under 10.3.9, I found that I was unable to repair my permissions, with the process hanging halfway through and a dialog telling me that Disk Utility had lost its connection to Disk Management and I'd have to quit, then restart Disk Utility and try again. Unfortunately this doesn't result in success and I was becoming increasingly frustrated, thinking that it might have been a QT 7.0.4 issue. I followed a few suggestions from others, but nothing worked, and was ready to go visit the Genius Bar...
But I did find out from MacFixIt that it's an easily solved (temporarily, at least) problem.
I moved iTunes out of the Applications folder to the Desktop, THEN ran Disk Utility/Repair Permissions- and the process completed normally and successfully. Easy as that. I then put iTunes back in Applications.
I did read that you have to repeat this process every time you want to repair permissions, at least until the glitch is fixed. It also seems to occur mostly with 10.3.9, though I should note this Permission problem didn't happen on my Mac Mini.
Just wanted to pass the info on.
--Richard

Answer 1

I downloaded iTunes 6.0.3, with OS10.3.9 and found the same problem with trying to repair permissions. Moving iTunes to the desktop also seems to have fixed it. What’s so special about the Applications folder?
When I ran TinkerTool to repair permissions it gave the following log:
Determining correct file permissions.
* malloc[511]: Deallocation of a pointer not malloced: 0x130a810; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug
: for architecture i386 object: ./Applications/iTunes.app/Contents/MacOS/iTunes malformed object (unknown flavor for flavor number 0 in LC_UNIXTHREAD command 27 can't byte swap it).
I’m not up to speed with the arcane language of Unix, so haven’t the faintest idea what it all means.
Maybe someone out there could come up with a patch to fix this annoying problem.
eMac   Mac OS X (10.3.9)