Although we haven't experienced the issue, PLENTY of others have, and there are no absolute tried-and-true solutions as yet:
http://discussions.apple.com/thread.jspa?t...11&tstart=0There are a couple of suggestions towards the bottom of that very long thread which might be worth a try:
QUOTE
I have a MacBook Pro 2.2 LED and suffered from this problem previously.
I reset the NVRAM, then did a safe boot and repaired permissions (very suspiciously, since I work at an Apple Authorized Repair Center and figured there's no way it would make a difference). Then around the same time, I turned off safe sleep (which was coincidental--it was because I was tired of waiting 45-60 seconds for my laptop to sleep). I haven't had the problem for several weeks now.
After researching the problem, I've found that the problem (for many people) seems to occur most often after waking up from safe sleep. My guess is that certain keyboard settings being saved in NVRAM are being corrupted by safe sleep (which is why I would suggest resetting NVRAM simultaneously).
This isn't a permanent or completely satisfactory solution (it might not even help your situation), but until Apple gets out this much-awaited update/fix, perhaps it will help some of you out there.
To disable safe sleep, run the two following commands in Terminal:
$ sudo pmset -a hibernatemode 0
$ sudo nvram "use-nvramrc?"=false
When done, restart your computer. Now delete the file "/private/var/vm/sleepimage" to free up a good chunk of hard drive space (the amount of RAM you have installed). With safe sleep disabled, a total power loss (i.e., removing your battery without the AC adapter connected) will wipe out whatever was in RAM at the time. Safe sleep is a nice feature, but since I don't switch out my battery and it's never fallen out before, the time I save makes it worth disabling for me (not to mention the fact that it seems to solve the keyboard problem).
The weird thing about this problem is that it sometimes takes days or weeks to show up. For all I know, my MBP may develop this issue too - it's hard to gauge exactly how widespread or universal the issue is or is becoming. Since Apple is now aware of it, let's hope they sort it out soon!
