Error after moving computers

[kenwardc]

Hi there

I've moved my kJams Pro to my new iMac but have a problem. When I attempt to start the program (the first time it asked me to enter my serial number, which I did and it solved the "trial" issue) I get told there is an update. I say YES let's have the update.... it downloads the update and attempts to install it, but then I get the following error:

Error
Auto Update: ### Error moving self to trash: "afpAccessDenied, insufficient access privileges for operation"

HELP!?

All the best
Chris

[dave]

fix your permissions with disc utility, try again.

if that fails, use this tool: Yet Another System Utility

then try again. should be fine.

[kenwardc]

Hi Dave

Sorry that's a little cryptic for me. Fix which permissions and where?

Cheers
Chris

[dave]

http://www.google.com/search?q=fix+your ... sc+utility

[kenwardc]

Hi Dave

OK - Have run the Disk Utility and it found loads of permissions errors on the disk which, I assume, have come from me migrating from my Macbook Pro to the iMac. However, even after running this twice and doing the repair twice, it is still not updating the program and gives me the same error as before.

If I uninstall the kJams package and reinstall, will that help resolve this? Also will I lose the database if I uninstall? Whew - I've put in hours of work which would be lost at that point.

Cheers
Chris

[dave]

i said that if disk utility doesn't work then use the other tool "Yet Another System Utility"

no, uninstall/reinstall will not do anything to help fix your permissions.

[kenwardc]

i said that if disk utility doesn't work then use the other tool "Yet Another System Utility"

no, uninstall/reinstall will not do anything to help fix your permissions.

Hi Dave

Yes - I saw what you wrote. I've done the first bit but it hasn't made any difference at all. I'll download the YASU package and run it and then I'l get back to you.

Cheers
Chris

[dave]

okay good, i think that should do the trick

[kenwardc]

Hi Dave

Bad news I'm afraid. I've done the YASU thing and it appears to have repaired all the disk permissions errors that were coming up. There is now just one advisory left as follows when I run Check Permissions on the main hard disk:

Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAgent” has been modified and will not be repaired.

Do you know whether this file has anything to do with the fact that kJamsPro cannot delete itself when upgrading? If not, then I'd really appreciate some help if possible - at this point I cannot update the package and haven't done so since I transferred to the iMac.

Cheers
Chris

[dave]

Okay i think i've found the problem

go to your user folder
then type command-shift-g
then type ".Trash" (no quotes)
then get info (command-i)
make sure your user has read&write privilege

let me know

[kenwardc]

Hi Dave

Here's a screenshot for ya.

Hope it helps.

[dave]

Okay get me on ichat so i can see this.
https://karaoke.kjams.com/wiki/IChat/Mac

[DeusExMachina]

Dave:

This is the same issue I discussed with you. For now you can work around by either just downloading the update from the website, or surfing to

/private/var/folders/68/68pDcWUwFdGnn4I2cKm+tk+++TQ/-Tmp-/TemporaryItems/kJams\ Temp

(the two items after "folders" in your path might be somewhat different, just surf til you find the right one) and drag the application to your Applictions folder.

Dave:
Might I suggest, as a generic work around for this issue, that you include a button to "Show Downloaded Application" in that error dialogue? This would allow them to use the Finder to copy the app manually.

[dave]

It's a deeper issue than that. the user is unable to trash things at all, apparently. but yeah, i'll add that to the list.

[DeusExMachina]

Well, I get the same error every time I upgrade, and I never have any trouble trashing things, and my permissions on .Trashes is fine, too, AFAICT. I just browse to the temp folder and copy it over the version in the Applications folder and all is well.
FTR, I did not have this issue when I ran from an admin account.