My display remains black after wake from sleep. How do I fix it?

I'm glad you said that, I've also had the same issue in Safari quite often and sometimes in other apps like the App Store or iTunes. I've also submitted reports through the feedback assistant in regard to both issues. Sorry you're having the same problem, though I'm glad it's not just me.

Sorry, this "temporary fix" doesn't work for me. The screen remains black until restart regardless of how many times I open or close the lid for any length of time.

As an update to all:

i happened to be in a mall with the Apple Store last night. I mentioned my issue to one of the techs who happened to know exactly what I was talking about. Apparently it's an uncommon (though known) issue that has manifested in random machines since Mavericks. He advised me to bring in my comp and said he'd show me how to fix it. when I did, he launched the bios screen and issued a few different commands to remove a certain profile or preference from something called a P-list. The one in question is com.apple.login or com.apple/login. I don't remember which. I haven't had any issues in the last few hours. Hopefully the same fix results in good performance for the rest of you as well.

Update 2:

Sorry for the delay, my machine was out of commission yesterday.

Upon further use and investigation, the solution specified above from the Apple Store was NOT a complete fix. While in the store, my machine appeared to be working fine, both waking and sleeping as expected. I think it may have even worked once after I got home. Later that evening, (within an hour of my last post) the issue was back. As soon as the display went into power saving sleep mode, it wouldn't wake again. Back to the black screen with adjustable brightness, but no motion or color. *I should note that I've also seen this issue arise while showing my login screen, but again without any pointer motion, just the frozen screen.*

Last night, after deciding it wasn't worth another drive to the Apple Store I decided to erase and perform a full reinstall. I dug out my hardware test disk and ran a couple of tests just to rule out hardware as a problem. After confirming all hardware was good, I entered recovery mode and performed a full reinstall. I am now running OS 10.10.1, and am reluctant to update to the Pre-Release 10.10.2. I've been slowly running updates on individual apps one at a time so that I can observe and hopefully identify any file causing issues. No issues to speak of for the last 18 hours and 10+ sleep/wake cycles. As a precaution, I also erased my time machine backup and let my machine create a new (hopefully clean) backup that won't carry over the previous error.

This is a long and rather unfortunate way to resolve an issue like this, I wish I had found an easier fix. On the other hand, starting fresh is kind of fun sometimes, right?

To Zolihonig's post:

I don't know enough about what the Apple guy did to give you anything more specific than I listed above. After opening the command terminal (still can't figure out which keys he pressed at boot to get there) he worked too quickly for me to keep track of what he did. Everything I know is listed above. Sorry I'm not more useful there.

Best,

ndopp

When I entered recovery mode on my machine and chose to perform a clean install of the OS it redownloaded 10.10.1 without offering me any other choices. I have yet to update to 10.10.2.

Yes, I was. I made a full backup on my time machine previous to the install just to be safe, but my files remained intact.

Thanks for the tip. I removed the application and the drivers using the commands in terminal listed on airparrot's website. Still haven't updated to 10.10.2, but when I'm feeling confident in my current system, I'll update to the pre-release again to test stability without Airparrot installed. Thanks again Nightlust.