Q: OS X Lion freezes at login screen + App Store is slow

I'll try and phone Apple support again tomorrow, Terry, and see if I can actually get through to a qualified technician. I had been hoping to "decommission" an old powerbook and move everything over to the 15 inch MBP

before the Lion problem arose.

I still have  Snow Leopard on the primary partition, so I can continue to use the MBP, but there isn't much point if the problem turns out to be hardware based, after all.

It seems to be somewhat disingenuous for Apple not to flag this issue. When you think about it, there must be

a large number of SL users with 2010 MBPs that wouldn't be aware of such issues, having not migrated to Lion!

@Metalizer: It sounds like you must still have an intact copy of your Snow Leopard's ~System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents/info.plis t to use as a reference - so doing what Rob and I have done (see previous page on thread) "might" solve your problem. (It could also be a hardware problem).

Or, even simpler, try replacing your Lion AGPM.kext/ ... info.plist with an unaltered copy of your Snow Leopard AGPM.kext's info.plist might work - then the GT 330M parameters would be guaranteed to match the graphics hardware (though I haven't tried exactly this myself). Once again, using TextWrangler or BBEdit is tons easier than using TextEdit (and making sure you are producing a .txt file - not an .RTF-format file, and having to mess with file-permissions via SUDO, etc

Alternatively, an Apple Certified Tech should be able to help. But if they haven't already dealt with this issue it may be a learning-process for them.

Terry, I've been trying another root, literally, as in enabling root user, as related in this thread:

https://discussions.apple.com/thread/3190075?start=0&tstart=0

so, I enabled root, repaired permisionsfrom the emergency repair volume, then repaired permissions from within the root account.

I saved the permissions report from within the root account. Now, the bizarre thing is that when I returned to my normal account later, I got the login problem again. So, I then launched the emergency volume, repaired permissions, and the same report came up, as when I was within root.

I'm going to post the report here tomorrow, as  most of the errors have to do with the Apple Power Management System, your famous kext file, and it looks like some code errors in there too, but I haven't a clue about programming....

(I'm emailing this from another machine at the moment)

I've just had a long read through this thread and it looks like Terry and Metalizer are on to a solution re: patching the AGPM. I have the freeze issue intermittently but only ever after logging in. This has made me doubt that its a hardware issue as it never happened with SL, and it is absolutely consistent in that if the freeze does happen, it will always happen at the same point, and I've never experienced a freeze outside of this time window. Applied the official graphics patch but was dissapointed that it made no difference whatsoever.

I did have a question though: I was going to implement the patch you've described but after seeing Metalizer mention that the AGPM permissions were different for the copied file I am hesitant. Is there a way of preserving the system/wheel/everyone permissions when making these edits? I used textwrangler and managed to find the entries you mentioned and removed them in a copy of that file, but is it safe to directly edit the original, and will this retain permissions or will the act of editing alter the permissions anyway?

I've heard of repairing permissions and have used it as a 'oops something's weird, quick use the magic fix' but would this be able to revert the permissions on the edited file. Would I be able to have the permissions repaired on my Kext copy if it were just on my desktop, or would it have to have already taken the place of the original. I'm concerned that if I get the system to load the edited version whilst its permissions are still wrong then something horrendous may happen.

Metalizer, after your brave experiments is there a guide you can give to making sure the edited AGPM gets its permissions restored prior to the system loading it, say for example, repairing permissions before booting into safe mode (which I understand is the way you get the system to swap the edited AGPM into its cache).

Sorry for the long ramble. Perhaps I should just wait for your endeavours to get back to Apple HQ where the engineers can facepalm, make the edits themselves and then roll out an update. However I'm not entirely confident that will happen as Apple sometimes have difficulties admiting their mistakes.

Actually I see at the top that this has been branched to a new discussion, a super secret discussion (unless I'm the only one without authorisation to see it). Perhaps Apple are watching.

All seems to be fine after logic board replacement. I hope the login beachball and safari freezes are gone forever!

Very good and fast service from apple after showing the failure was related to AGS.

The short answer is that the permissions for a copy of the file will be different if you save it in a different - non-system directory. But if you write the copy back into a directory owned by system they are not automatically "corrected". You may need to use Terminal and SUDO to do a "chown" (change owner).

And you CAN edit the original file in-place suingtextwrangler - but keep a backup copy just in case.

Thanks Terry, I will try that hack, if all else fails.

In the meantime this is what kept me up until the small hours of the morning.

This is the permissions report from within root:

Repairing permissions for “Macintosh HD (Lion)”

ACL found but not expected on “private/var/root”

Repaired “private/var/root”

ACL found but not expected on “private/var/root/Library”

Repaired “private/var/root/Library”

ACL found but not expected on “private/var/root/Library/Preferences”

Repaired “private/var/root/Library/Preferences”

ACL found but not expected on “System/Library/Extensions/AppleGraphicsPowerManagement.kext”

Repaired “System/Library/Extensions/AppleGraphicsPowerManagement.kext”

ACL found but not expected on “System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents”

Repaired “System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents”

ACL found but not expected on “System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents/Info.plis t”

Repaired “System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents/Info.plis t”

ACL found but not expected on “System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents/MacOS”

Repaired “System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents/MacOS”

ACL found but not expected on “System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents/_CodeSign ature”

Repaired “System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents/_CodeSign ature”

ACL found but not expected on “System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents/_CodeSign ature/CodeDirectory”

Repaired “System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents/_CodeSign ature/CodeDirectory”

ACL found but not expected on “System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents/_CodeSign ature/CodeRequirements”

Repaired “System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents/_CodeSign ature/CodeRequirements”

ACL found but not expected on “System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents/_CodeSign ature/CodeResources”

Repaired “System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents/_CodeSign ature/CodeResources”

ACL found but not expected on “System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents/_CodeSign ature/CodeSignature”

Repaired “System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents/_CodeSign ature/CodeSignature”

ACL found but not expected on “System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents/version.p list”

Repaired “System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents/version.p list”

Group differs on “private/var/db/GPURestartReporter”; should be 0; group is 80.

Permissions differ on “private/var/db/GPURestartReporter”; should be drwxr-xr-x ; they are drwxrwxr-x .

Repaired “private/var/db/GPURestartReporter”

ACL found but not expected on “System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents/MacOS/App leGraphicsPowerManagement”

Repaired “System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents/MacOS/App leGraphicsPowerManagement”

Permissions repair complete

now, normally, according to the google searches, the "ACL found but not expected" error can be safely ignored, even according to official Apple notes – but it seems too much of a coincidence  in these circumstances. No?

Minyall, I still haven't started on Terry's hack, but will keep you posted. I'm emailing this from the SL partition

and I will have another "root" around Lion later – will keep you informed.

I edited the kext and re-installed it using Kext helper

A few days later my MacBook experienced its first kernel panic ever.

...so I'm now posting here from the Lion partition (for the first time, I think ), so I went back into the root account and ran disk permissions repair 5 times, consecutively, I kid you not! The same ACL errors, as above, keep coming up, keep recurring, even though DU previously "repaired" them.

The only reason I'm able to post this is because I managed to get a clean login on my normal user account, but as you all know by now, this doesn't mean I've fixed anything at all.

...just to update, I restarted twice with clean logins – that's three clean logins in a row...I'm not ready to pop the cork, yet, but I'm feeling lucky right now!

Hi all guys,

practically I've quite the same problems of you, but I've a mac mini late 2009, not a MBP, so 1 video card (nvidia 9400)

This is the event log (OS X Lion 10.7.2)

15/11/11 21:16:53,756 SecurityAgent: User info context values set for maurizio

15/11/11 21:16:53,756 SecurityAgent: User info context values set for maurizio

15/11/11 21:16:53,789 authorizationhost: Failed to authenticate user <maurizio> (error: 9).

15/11/11 21:16:58,682 SecurityAgent: User info context values set for maurizio

15/11/11 21:16:58,682 SecurityAgent: User info context values set for maurizio

15/11/11 21:16:59,846 SecurityAgent: Login Window login proceeding

15/11/11 21:16:59,846 SecurityAgent: Login Window login proceeding

15/11/11 21:17:00,182 loginwindow: Login Window - Returned from Security Agent

so, any idea and/or suggestion?

As you can see, 5 seconds were elapsed after the "error 9" and the SecurityAgent log

Thank you all

Hi Maulattu, I'm not calling a fix yet, until I score a clean login from three consecutive cold starts. But, if your are feeling adventurous:

launch the emergency lion volume (either power on with option key and select drive, or power on with command r)

from the drop down menu, launch terminal, type: reset password and hit "enter" key

a new window appears with user information; here you can do two things, reset password for your user account

(just type in your old password and confirm) and change password for root (here you can choose to use same password for convenience); once you do this, you automatically enable Other Users as an added account in your

main login window.

(you can also choose to launch disk utility from within the emergency volume and repair permissions as an added step)

now quit and restart: at login click on other users, type root into name window and your password (quickly)

– you should now be in your root account; launch disk utility and repair permissions; copy the report into a text file and save it to usb stick for  future reference or if you still have SL on another volume drop it into that documents folder.

Continue to repair permissions, consecutively, a few times. (I did mine 5 times)

log out and restart, login to your normal user account.

Hi Metalizer: Re. ACLs (Access Control Lists) - I found this Apple Tech report - possibly of interest?

http://support.apple.com/kb/ts1448