sleep wake problem with Yosemite on my Mac Mini Mid 2012

do you connect to your monitor?

HDMI to HDMI?

if so change it to the cdmi to DVI-D connector if your monitor supports it

Mine works as it should now

Clive

Hi,

same for me, i have the same problems on a mac mini mid 2011, base model. At first, it did not properly recognise my sound output, and afterwards, after this didn't occur any more, the mini wakes up on key pressure on apple bluetooth keyboard. I still can move the mouse pointer with bluetooth trackpad, but the mini does not do anythting. The setup is the same as under Maverick, it all happened after the update to Yosemite.

Best regards,and i hope we'll see a fix from apple soon.

Chris

Have you tried a SMC reset?

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

If you read this thread from the beginning it should be clear that PRAM/SMC reset didn't help at all.

My apologies for not hanging on every precious word that you write.

Respectfully, it is unhelpful to join this sort of online conversation and respond without having first read back over the entire thread completely. Every single person closely following the discussion trying to solve the same problem just got e-mailed to come check out your comment...and it neither aided nor educated any one of them.

You're absolutely free to decline to read an entire thread because you feel it could be a waste of your time, but that does not make it acceptable that you should put wasting many other people's time ahead of your own desire to be heard. If you're not interested in fully researching the issue and trying to help everyone out in the most efficient way possible, please quietly listen instead of speaking. 🙂

The previous comment contributes nothing to the discussion.

Having the same problem with a late 2012 Mac Mini using HDMI video and 3.5mm audio out. Looking forward to a solution that doesn't involve losing functionality (volume control)!

I just wanted to add to this thread that I experienced the same problem. I've my 2011 Mac Mini setup as a media center connected through HDMI to my receiver (which in turn is connected to my speakers of course and to my TV through HDMI). I've read this thread and found that my setup is different from most people who experienced this problem... I've nothing connected through the 3.5 jackplug... never had...

Based on this thread I checkt my sound output settings and found that there were three devices listed. The headphone (internal), my receiver (HDMI) and a third one from a progam called LogMeIn. Seemed like a way to control the sound of the Mac Mini through that third option. To be sure I deleted the program, so now I'n down to two output devices (headphone and receiver). Going to bed now and see tomorrow if this "solved" the problem for me.

I'll keep you posted!

After having a 100% failure rate with speakers attached and 0% failure rate without speakers (via the headphone jack), I just experienced the locked screen without speakers attached.

Situation is that yesterday I uninstalled a utility called xtrafinder, then upon the next restart, my system would boot 1/4 of the way and crash. After a time machine restore till before I installed the utility, I had to install the last few updates regarding yosemite beta and then upgrade to final. Did that yesterday. This evening I'm getting back behind my system. Black background and login window but no response to the keyboard. And the funny thing there is where ordinarily I have a logitech illuminated keyboard; in order to get through the restores etc I attached an apple keyboard (as the logitech requires some remapping of option and command).

So, anyway, I can now confirm the issue on a '12 mini without something in the headphone jack 😟

I don't know why it happens, either. But I hooked up my Bose speakers via an old Airport Express and it seems to be a reliable workaround.

I was also having this problem on my Mid-2010 27" iMac (i7, 12gb) since the OS X 10.10 update, and not prior. The issue is not only existent on the Mac Mini.

I've fixed the issue in a similar manner to the audio devices fix, but in my case it was not my external speakers being plugged in that caused the issue. The issue was that I had airparrot installed (like many 2010 iMac owners who were disappointed that we just missed the airplay video mirroring cutoff by a single model year). Airparrot had installed an audio device driver, which caused me to have a second device in my list, which many on this thread determined was the issue.

After removing airparrot and all of its components (as described here: http://help.airsquirrels.com/support/articles/1000106969-i-need-to-remove-airpar rot- ) the issue has been resolved. Now if Apple had just opened up airplay to a few older (and quite powerful) iMac models, we wouldn't have this issue.

I do agree though, that this is a bug for sure. It was not an issue on and previous versions of OS X. Hope this helps.

Same with me. Mac mini late 2012. I unplugged the speakers jack and everything is fine. I have a monitor with HDMI and mini jack output, so I plugged my speakers to that. Now everything works fine!. I noticed that at some time earlier, mac mini did not recognized the plugged in speakers and I had to manually choose as sound output the speakers.

On a MacBook Air (13", Mid 2012).

After reading the above consensus on multiple audio inputs being the culprit, I, too, deleted AirParrot. It installs a kernel extension, which can always be problematic. I had previously unplugged a set of speakers from the headphone jack to no avail. Problem still existed after that.

For the record, I still have two inputs listed in Sound Prefs. Internal Audio, and the HDMI input from my display, which I can't disable via software in System Prefs, but I did manually set the in-display settings to "PC audio" vs "HDMI audio." Not sure if that does anything.

HOWEVER, after uninstalling AirParrot completely, I had another system freeze. Not upon wake from sleep, this time, just normal usage shortly after startup.

Once AirParrot was gone from my system, I restarted and used it for a bit before the machine froze up again when a Little Snitch incoming SSH alert popped up. I had to do a hard restart. The freeze occurred about three more times before I singled out Little Snitch. Again, AirParrot was gone from my system at this point.

Both AirParrot and Little Snitch put out new versions for Yosemite, btw. They do both install their own kernel extensions, which could be gumming up the mix.

I ended up uninstalling Little Snitch, as well, and with my speakers unplugged, my sound settings set to internal speakers, and my energy settings set to never sleep, I've not had any crashes in two days now.

Did anyone else have a combination of AirParrot and Little Snitch installed when experiencing the freeze upon wake from sleep issue?

I know this throws a wrench in the mix, as the later freezes didn't occur during wake from sleep. However, I wasn't able to test that as my machine never GOT to sleep before Little Snitch went to work freezing things up. But, if some others on the thread had both of these installed, we might be on to a new culprit. Could be that Apple got tougher on third-party kernel extensions in Yosemite.

For the record, I've had both apps installed for ages and I occasionally experienced wake from sleep freezes under Mavericks, too. I usually attributed it to virtual memory swap files/a memory leak filling up my main hard drive while my machine slept (Not that much free space on this 128GB drive, and I frequently got "out of disk space" messages that necessitated a restart to clear things out. I know, I know).