My apologies for the pile-on, but I have this same problem, except with Mountain Lion. I find that it only happens after the computer has hibernated (not ordinary sleep), and happens inconsistently. Have you tried the following:
- re-pairing your keyboard
- resetting NVRAM and SMC
- killing process blued when the failure occurs
I'm a little frustrated that the established resolution for this problem is a restart.
Welcome to the Support Communities!
Are you having an issue with an Apple bluetooth keyboard or a different brand?
Have you replaced the batteries in your keyboard?
The articles below provide additional troubleshooting steps:
I hope this information helps ....
Have a great day!
Sorry about that. I should have provided more information.
Information about resetting your NVRAM or PRAM is here.
Information about resetting your System Management Controller (SMC) is here.
blued is the bluetooth daemon, and in simple terms is a process that the system runs to support bluetooth devices. You can force quit the process by opening Activity Monitor (search for it using Spotlight or find it in Applications>Utilities), searching for 'blued' in the list of processes, selecting/highlighting it, and then clicking the "Quit Process" at the top of the window, which will prompt you to quit or force quit the process (blued) that you've selected.
Let me know if you have any other questions.
Yes, I have an apple keyboard and mouse...no different brands involved. Although I did not know what a SMC reset is, after finding out I realize that I have done this on my own for other "ghost" problems I have had.
For some reason my iMac also likes to intermittently shut itself off after being in the sleep mode. And at times will not awaken...my solution (until it happens again) has been to unplug, wait a couple of minutes and then start over. It's has worked in the past but as you can surmise it's more than annoying!!!
I was hoping that my upgrade to Mavericks would eliminate the problem, but it happened to me again today...
Seems like the hardware knows its exact "gone out of warranty" date and acts accordingly.