Currently Being ModeratedFeb 1, 2013 10:43 AM (in response to octium)
It's a bug that Apple hasn't yet fixed. Open Activity Monitor (in the Utilities folder), find the process "appleeventsd", and terminate it. (You have to use "Force Quit", not "Quit".)
This is a workaround, and I don't know how long things remain "fixed" after you implement it.
Currently Being ModeratedFeb 5, 2013 9:38 AM (in response to jacobwb)
Do you have TotalFinder installed? If so, uninstall it and reboot.
The appleeventsd bug also prevents the OS-X "Archive Utility" from unpacking .zip archives. If Archive Utility is working for you, your problem is not appleeventsd. The next thing to try is to re-index Spotlight: http://support.apple.com/kb/HT2409
Currently Being ModeratedFeb 5, 2013 11:17 AM (in response to jpdemers)
I don't have TotalFinder installed and Archive Utility doesn't work (haven't noticed that before since I use Incredible Bee's Archiver App).
When I kill appleeventsd it naturally goes away and then it opens again as soon as I hit "show in finder" – I assume it should act like that since the force quit is merely to force a restart on the process.
Any other ideas :/?
Currently Being ModeratedFeb 5, 2013 1:06 PM (in response to jacobwb)
Got me stumped there. My understanding (limited) is that the Apple Events daemon works for a while when freshly launched, but for reasons unknown it gets bolloxed after a certain number of calls. No error messages appear in Console, which makes it especially hard to track down. If yours gets hosed immediately, that's not the usual pattern.
iPhoto and iTunes use Apple Events quite a lot.... if you have either of those apps running, you might see what happens without them. Failing that, see what happens when no applications are running. Finally, see what login items are being fired up (System Preferences => Users and Groups => Login Items) and disable those.
This bug only crops up on a small number of Macs, and as far as I know nobody's been able to track down what triggers it.
Currently Being ModeratedFeb 17, 2013 10:43 AM (in response to octium)
Just to add my 2 cents. I have the same problem on iMac 2.93 with 8GB RAM running 10.8.2. Quitting appleeventsd has no effect. I also note that in addition to restarting appleeventsd when you touch "show in finder" it also restarts immediately if you touch the yellow warning triangles next to the "erroneously" flagged keyboard shortcuts for spotlight noted above. I've reset all the keyboard shortcuts to default and don't know of any shortcuts in other appl that overlap these (much less the fact that none are running at this point).
Changing the keyboard shortcuts however to alt space and shift alt space, immediately stopped the wierd show in finder problem.
Can someone smarter than me figure out where the problem is?
Currently Being ModeratedFeb 17, 2013 11:47 AM (in response to drhoek)
"Changing the keyboard shortcuts however to alt space and shift alt space, immediately stopped the wierd show in finder problem."
Are you saying that this is a fix? If it is, that's great -- but it's one of the strangest I've ever seen.
Currently Being ModeratedFeb 23, 2013 7:46 AM (in response to jpdemers)
It's been a week and it's still working. I don't consider it a fix, for sure. But, it does seem to be a work around. I would still prefer to get back to command-space as my keyboarding muscle memory has that one already stored and I keep hitting it. I suspect that there is something else assigned to command-space (hence the little yellow triangles under spotlight prefs as noted above by octium). I can't figure out what it is though. My most key combo intensive application is Logic Pro and I reset that to defaults so there shouldn't be any overlap. I'm not enough of a code monkey (not to mention too lazy) to have gone through and actually changed keyboard commands for any of my other apps.
I'm open to suggestions for troubleshooting this, but the alt-space alternative is still working.
Currently Being ModeratedFeb 23, 2013 8:36 AM (in response to drhoek)
Shortcuts generally kick in only for the application that's currently "in front", but some apps are "system wide" and trump the usual rule. One of those might be the culprit.
First thing to do is check the preference panel at System Preferences > Keyboard > Keyboard Shortcuts, to see what else might have comandeered the cmd-space combo. If nothing there, see what happens if you start in safe mode, or when all startup items are disabled.