Currently Being ModeratedFeb 22, 2012 7:59 AM (in response to Saxman2011)
What bugs Mountain Lion might fix is something no one here will know.
Your problems are almost certainly not due to bugs in Lion, though, since it works quite well for millions of people. If you'll detail the problems, including the exact text of the error messages you're receiving, someone here may be able to help (tagging onto someone else's thread isn't usually the best strategy for getting assistance for your own issues).
Currently Being ModeratedFeb 22, 2012 9:03 AM (in response to Saxman2011)
Repairing the permissions of a home folder in Lion is a complicated procedure. I don’t know of a simpler one that always works.
Launch the Terminal application by entering the first few letters of its name into a Spotlight search. Drag or copy – do not type – the following line into the window, then press return:
chmod -R -N ~
If you get an error message about permissions, enter this:
You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up.
Next, boot from your recovery partition by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
When the recovery desktop appears, select Utilities ▹ Terminal from the menu bar.
In the Terminal window, enter “resetpassword” (without the quotes) and press return. A Reset Password window opens.
Select your boot volume if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select ▹ Restart from the menu bar.
Currently Being ModeratedFeb 22, 2012 9:32 AM (in response to Linc Davis)
Just wondering here...
chmod -R -N ~
That should remove the ACLs and change mode on file hierarchies...
Running Reset Home Directory Permissions and ACLs from Recovery seems redundant?
Currently Being ModeratedFeb 22, 2012 9:51 AM (in response to Saxman2011)
Will the new OS Mountain Lion have the Lion permission issues fixed?
I don't have any permission issues and neither do any of our users. So the problem is obviously specific to your computer and not with the OS in general.
Currently Being ModeratedFeb 22, 2012 10:45 AM (in response to Linc Davis)
Linc Davis wrote:
Ta! More learning...
Currently Being ModeratedMar 16, 2012 11:49 PM (in response to Linc Davis)
This procedure does not work for Mountain Lion. Anyone know how to reset the "Everyone" group to Read from No_Access? I managed to lock myself out of my MacbookAir by changing the access for "Everyone" to "No_Access".
Currently Being ModeratedMar 17, 2012 12:41 AM (in response to 4RayData)
If you are using Mountain Lion legally then you will have access to the appropriate forums for this kind of assistance. If you're not using it legally, well good luck with that.
Currently Being ModeratedMar 17, 2012 12:37 PM (in response to Terence Devlin)
Seems like a mean and vindictive response Terence to my question above. I apologize if you think I posted to the wrong forum. I arrived here through a Google search based on Lincoln Davis' solution above.
I am a NDA'd Apple Developer member. That doesn't mean as much as it used to. Did you know that once you install Apple's beta software on your computer that you can't get support through Developer Support? I was referred to "Apple Care". Unfortunately, without a $50, upfront payment, you can't discuss "an incident" with anyone who might have a solution unless you have an Apple Care agreement.
Anyway, thank. I'll search elsewhere.
Currently Being ModeratedMar 19, 2012 7:11 AM (in response to 4RayData)
Nothing "mean" nor "vindictive". Terence politely pointed out that discussions about unreleased software are not allowed here. If you decide you wish to violate your NDA, that's your decision, but doing so in Apple's own forums is rather unwise.
Apple Developer Support does indeed provide some assistance, but they are not general tech support - they don't have those sorts of resources, they're for assistance with development of software - and since they clearly tell you that the seed software is unfinished, the amount of support they provide for operational matters is limited. But you have developer forums to which you have access where you can ask for assistance.
Currently Being ModeratedMar 19, 2012 9:03 AM (in response to 4RayData)
I was referred to "Apple Care".
I'd actually be surprised if AppleCare were able to assist you with Mountain Lion issues. No one is trying to be rude. Discusison in public forums about Mountain Lion is against the non-disclosure agreement which you agreed to as part of your participation in either the Developer Program or AppleSeed Program (although, I don't know if Apple has started an AppleSeed Program for ML yet). In either case, they provide you access to the ML support forums. Any issues related to ML should be addressed there. In particular, as those forums are just for people using ML, you are much more likely to get someone who may be able to assist you.
Currently Being ModeratedMar 19, 2012 11:14 AM (in response to varjak paw)
Thanks Joey and Varjak. And, apologies to Terence and the forum.
Varjak, the issue I am having is not specific to Mountain Lion. I don't believe that mentioning it violates my Apple NDA.
..to the problem..
Joey, maybe ' "No one" is trying to be rude ' but I am still being ostracized by "Everyone"! This pun is intended to be funny. If you perform a "Get info" on your main volume and then iff you unlock "Sharing & Permissions" and then, iff you change the permissions for "everyone" to "No access" from it's default setting of "Read only", you will create the problem I have. My question was -- how do you recover from this. I know it was dumbness on my part - you can stop chuckling now. But if there are suggestions, I'm willing to listen.
Currently Being ModeratedMar 19, 2012 11:18 AM (in response to 4RayData)
Niel has created a tip specifically for this problem.
Currently Being ModeratedMar 19, 2012 11:39 AM (in response to 4RayData)
There may be tools or techniques or situations that would apply to Mountain Lion but not one of the released versions of Mac OS X or vice-versa, and hence could not be discussed here. That's why you have developer forums available to you. You're not being "ostracized"; you're being told that we cannot discuss any unreleased Apple software here, even if the problem appears to be one that would affect a released version of the Apple software, and are being told where you can ask for assistance without fear of violating your NDA. I would suggest your re-read sections 5 and 6 if your NDA agreement should you question why you're being directed elsewhere.