Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Strange Finder Behavior
- Thread starter MarkW19
- Start date
- Sort by reaction score
Yes, I understand the ACL inheritance but it seems that somehow <i>every file and subdirectory</i> got an ACL set on it. I've cleared the ACLs from both by home directory and all of the Documents/Library/&c. files within it, but still every file on down from there has an ACL set on it. I can go through and just chmod -N *, but it takes a while ...
Well, it seems like that ACL script is just the same as booting up from the Leopard DVD and going to Reset Password>Reset ACLs, someone has said?
And I've done that, and it didn't alter anything.
Does anyone have any other ideas?
And I've done that, and it didn't alter anything.
Does anyone have any other ideas?
Can anyone help me with this, please?
I've read through that thread, and I've already done the Leopard DVD>ACLs thing, and it didn't alter anything, I'm still having the problem...
I've read through that thread, and I've already done the Leopard DVD>ACLs thing, and it didn't alter anything, I'm still having the problem...
At this point, the best advice I can give is to back up your user files, if you haven't already, then Archive and Install Leopard. Do NOT check the preserve users and network settings option - this will lead to the problem coming back. Once you've done that, copy over your stuff from the backup. If the problem's gone now, great! All you'll need to do now is reapply software updates, which is a bit of a pain.
Strange Finder Behavior.
I had done exactly that and the error did not go away. I had an Apple case (# 952 630 52) - a person by the name Chris (in the Product Specialist) department was very helpful in the end. He had forwarded the issue to the developer team. (I also had sent them the links to this thread and the macfixit thread.) In the end the developers came back with some Terminal commands to run and after that the issue was gone. Unfortunately I did not write down the commands.
Good Luck.
I had done exactly that and the error did not go away. I had an Apple case (# 952 630 52) - a person by the name Chris (in the Product Specialist) department was very helpful in the end. He had forwarded the issue to the developer team. (I also had sent them the links to this thread and the macfixit thread.) In the end the developers came back with some Terminal commands to run and after that the issue was gone. Unfortunately I did not write down the commands.
Good Luck.
Hi,
Sounds promising. What sort of commands where they? chmod, or something different?
Strange Finder Behavior.
yes, it was CHMOD command. try to call apple and see if they let you pull my case number. if you can't get through let me know i'll call them again and see if i can get the command.
yes, it was CHMOD command. try to call apple and see if they let you pull my case number. if you can't get through let me know i'll call them again and see if i can get the command.
Great, thanks! I'll give them a call.
Were you having the exact same problems as me then?
Thanks for the help.
Were you having the exact same problems as me then?
Thanks for the help.
Hi There,
I just had the same problem!
I fixed this by doing the following:
- Enable root user (for the sudo command, directory utility enable root user)
- open terminal (to give the commands)
- close all apps and folders/files in your dock to be sure there's no access denied trouble
- type: sudo chown -R myusername:staff /Users/myusername
-> replace myusername with your username, makes sure you own the files in your homedir
- type: sudo chmod -R ug+rwX /Users/myusername
-> replace myusername with your username, makes sure user&group (myusername.staff) can read write and eXecute (X in caps = no folders, x gives it also to folders)
- type: sudo chmod -R -N /Users/myusername
-> replace myusername with your username (this removes the ACL from all the files, like the double everyone with one having custom access, this is the problem)
- type: sudo diskutil repairPermissions /
-> fixes all system related permissions, just to make sure since we changed a bunch of permissions. also fixes strange finder behaviour.
- type: reboot
-> just to make sure, after the reboot everything should be fine again.
- disable root user if you don't use it very often
must say, it really creeped me out because in terminal all acl's seemed fine, but in the finder the files had two records for the everyone perm. (one read only and one with custom access)
good luck
grts
I just had the same problem!
I fixed this by doing the following:
- Enable root user (for the sudo command, directory utility enable root user)
- open terminal (to give the commands)
- close all apps and folders/files in your dock to be sure there's no access denied trouble
- type: sudo chown -R myusername:staff /Users/myusername
-> replace myusername with your username, makes sure you own the files in your homedir
- type: sudo chmod -R ug+rwX /Users/myusername
-> replace myusername with your username, makes sure user&group (myusername.staff) can read write and eXecute (X in caps = no folders, x gives it also to folders)
- type: sudo chmod -R -N /Users/myusername
-> replace myusername with your username (this removes the ACL from all the files, like the double everyone with one having custom access, this is the problem)
- type: sudo diskutil repairPermissions /
-> fixes all system related permissions, just to make sure since we changed a bunch of permissions. also fixes strange finder behaviour.
- type: reboot
-> just to make sure, after the reboot everything should be fine again.
- disable root user if you don't use it very often
must say, it really creeped me out because in terminal all acl's seemed fine, but in the finder the files had two records for the everyone perm. (one read only and one with custom access)
good luck
grts
Thanks for the advice.
Sorry to sound paranoid, but as this is your first and only post, and you only joined today (presumably to post this), can anyone please verify these commands won't cause any harm to my system?
As I said, I apologise, but not knowing much about terminal commands, I just want some confirmation from someone that does.
Thanks for your help.
Sorry to sound paranoid, but as this is your first and only post, and you only joined today (presumably to post this), can anyone please verify these commands won't cause any harm to my system?
As I said, I apologise, but not knowing much about terminal commands, I just want some confirmation from someone that does.
Thanks for your help.
No problem, its always better to be safe, we'll have to wait while someone veryfies it's no BS 
Just updated my post with some comments to clearify the steps.
I have a new mac and forgot my other username thats why I made a new account, im not that very active here, but came across your post because I was freaking out I couldn't pinpoint where this behaviour was coming from.
Good luck.
Cheers
Just updated my post with some comments to clearify the steps.
I have a new mac and forgot my other username thats why I made a new account, im not that very active here, but came across your post because I was freaking out I couldn't pinpoint where this behaviour was coming from.
Good luck.
Cheers
Hey there. I'm familiar with Terminal commands, and although I don't have this particular issue, it seems I was right all along about the cause, and I was almost there with regards to the solution... I do want to add one more thing though: Don't leave the root user enabled after you run all those commands. It just leaves you needlessly vulnerable.No problem, its always better to be safe, we'll have to wait while someone veryfies it's no BS
Just updated my post with some comments to clearify the steps.
I have a new mac and forgot my other username thats why I made a new account, im not that very active here, but came across your post because I was freaking out I couldn't pinpoint where this behaviour was coming from.
Good luck.
Cheers
That said, these commands seem to be the right ones for this situation. If you scroll back earlier in the thread and look at my other posts you'll see I had the right idea but wasn't quite there.
No problem, its always better to be safe, we'll have to wait while someone veryfies it's no BS
Just updated my post with some comments to clearify the steps.
I have a new mac and forgot my other username thats why I made a new account, im not that very active here, but came across your post because I was freaking out I couldn't pinpoint where this behaviour was coming from.
Good luck.
Cheers
Well, that seems to have fixed it, from what I can tell!! I'll know for sure within a few days when I've used more files, but I've tested the "usual suspects", and I can modify, rename, delete etc. all just fine. Also, the "custom access" seems to have gone on the files I've looked it, and I now have full "read and write".
So, it looks like that was it! Terminal still returned some errors "found ACLs where not expected" etc., but it all seems good.
Thanks so much for your help!
Well, that seems to have fixed it ... the "custom access" seems to have gone on the files I've looked it, and I now have full "read and write".
So, it looks like that was it! Terminal still returned some errors "found ACLs where not expected" etc., but it all seems good.
Thanks so much for your help!
Didn't suspect otherwise
Good to hear you fixed it now. Those acl errors came prob. from the permissions fix so no worries there. So much better then a reinstall of your precious mac huh
Does Mac OS X ask you for your password when you attempt to drag stuff? If it doesn't, you probably have a dirty mouse. If it does, then run the Terminal commands listed a few posts above this one. That should fix it.