Yesterday we noted a problem where the Command key, used in conjunction with other keys to execute shortcuts, does not function correctly.
We've since received several confirmation reports, as well as some workarounds.
Switching views Some users can restore command-key functionality by switching Finder views.
Jim Vance writes "Per your request in today's MacFixIt, I am reporting that I too often experience failures of this kind. Sometimes, when a Command (key) failure occurs and this failure is associated to a file or files within a Finder window, one can switch views in the window (say from list view to icon view) and discover that the previously failed keyboard command suddenly works."
Temporary selection Thomas Deliduka reports that temporarily selecting a file in the Finder for renaming allows command-key operations to apply properly:
"I have been able to work around the command-key problem by hitting return on the file as if I'm going to rename it, then hit return again and then do the command key operation I want.
"If there is more than one file selected, I arrow to one so one is highlighted, then do the above, return then use my keyboard to select the other files again and do the command key operation."
Force quit Finder Others readers have found that restarting the Finder via the "Force Quit" option is the only remedy:
"One trigger for causing certain command key shortcuts to stop working is to enable authentication when waking from sleep or exiting the screen saver as set in the Security preference pane. While logged into an account, activate the Screen Saver (via a hot corner or automatically) or put the computer to sleep, then exit the screen saver or wake the computer up. After authenticating as the currently logged-in user, some command keys will no longer work as expected. For example, pressing [command] [o] may not invoke the Open command, but pressing [command] [down arrow] will.
"My solution has simply been to relaunch the Finder via the Force Quit panel."
Activate menu Joshua Ochs found that simply activating a menu via mouse (i.e. clicking on the "File" menu once) restores the command-key functionality:
"I have also found that keyboard shortcuts in the Finder fail on occasion - usually the 'Finder' and 'File' menus. I've found that simply opening these menus and closing them 'fixes' the problem for a while, although it will occur again (and invoke swearing).
Using speech recognition For others who have the same option, Donald E. Kahle suggests the usage of speech-based Finder commands, which can be set up in the "Speech" pane of System Preferences.
"The problem manifests itself by the inability to Quit programs with the command-Q command, although clicking on command-Q in the pull-down program menu works fine. I have been using the work-around tactic in Speech Recognition 'Quit this Application' as a substitute. This tactic also works well, but command-Q doesn't work for any program even though it appears in the program pull-down menu."