Password for root not working

baltwo: I reported it using Apple BugReporter. Your concern is duly noted......

AEGeX: Let's hope someone turns their attention to the matter soon....

Yes.

Exactly same problem here with fresh install of Lion.

After reporting this issue using Apple BugReporter, I received the following message via email yesterday:

This is a follow up to Bug ID# 10035231. After further investigation it has been determined that this is a known issue, which is currently being investigated by engineering. This issue has been filed in our bug database under the original Bug ID# 9726353. The original bug number being used to track this duplicate issue can be found in the State column, in this format: Duplicate/OrigBug#.

In sum, Apple is working on the problem. Hopefully it will be addressed in 10.7.2......

Tested on the new Macbook Air.

Still the same problem.

OS: Lion 10.7.2

Also on a Macbook Pro.

Still the same problem.

OS: Lion 10.7.2

So, they haven't fixed it yet. Too busy mucking with cloudy stuff for iTunes and the iOS devices.😉

Having exactly the same problem on bran new mac book air with Lion 10.7.

First use of root working fine.

Next access denied whatever be the root password I set up.

Working fine on my Imac with Lion 10.7.2.

I do no wish to upgrade my mac book air to 10.7.2 as 10.7.2 has a problem

finding Time capsule when performing backup with TimeMachine after every

reboot of the mac.

jean.

P.S.:

Apple says the Time Capsule / Time Machine should be solved next Lion release.

Brand new MacBook Air, fully patched 10.7.2, and it still isn't working.

My main problem is I need to setup a persistent static route and I only know how to do it with root privileges. And this problem is affecting the regional manager's computer, and since I'm the only Mac-savvy person in the company, I got tasked with it.

Anyone know of a way to setup a permanent static route that doesn't require root privileges?

Thanks, Apple, for keeping your priorities straight. Glad you got iPhoto to not close unexpectedly on machines using some completely obscure codec plug-in, while leaving a minor problem like freaking ROOT not working on the back burner.

Good job. Really. Awesome.

This won't solve your technical issue right now ...

But I think the more people we are reporting a glitch to Apple,

the quicker they may be working on the problem.

In this spirit, I registered as an Apple develloper to have the possibility to report bugs straight

to them.

I also strongly suggested them through an Apple Care hotline satisfaction survey,

they should make a digest of all the bugs they are working on for the hot line

engineers so they don't spend hours (and us to !...) trying to find a solution to customer's

problems the OS Apple people are already working on.

Sorry not being able to help you more.

Jean.

montcley.jean wrote:

In this spirit, I registered as an Apple develloper to have the possibility to report bugs straight to them.

AFAICT, you can also use the http://www.apple.com/feedback/macosx.html path and select Bug Report. However, I've been using the BugReporter system for years and am unsure as to the path feedback takes to get to the same destination.

Wilbrik wrote:

Anyone know of a way to setup a permanent static route that doesn't require root privileges?

This isn't possible.

What do you need a permanent static route for? That is unusual.

Thanks, Apple, for keeping your priorities straight. Glad you got iPhoto to not close unexpectedly on machines using some completely obscure codec plug-in, while leaving a minor problem like freaking ROOT not working on the back burner.

Root works fine. You don't want to use root in an Aqua context. There is no reason for it and you will only have problems.

The problem is that a MacBook Air is unlikely to handle this well. Routing was designed for machines that weight as much as a refridgerator and never move. To setup routes on a mobile machine and have them work properly is tricky.

etresoft wrote:

Root works fine.

How do you figure that, given the problems being reported on this page? I can confirm the same problem on my Lion install also.