Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

A possible fix for non-functioning function key shortcuts System
I've had a few occasions where most Mac OS X keyboard shortcuts suddenly stopped working (e.g., F9 for ExposÚ, F12 for Dashboard). Strangely, Copy, Paste, and Cut continued to work. The only solution seemed to be a reboot.

I discovered the cause yesterday: Dashboard. There must be some circumstance where it must not properly release the keyboard grab. Fortunately, I also discovered that explicitly invoking Dashboard (by double-clicking on Dashboard in Applications) cures the problem.

[robg adds: I haven't experienced this problem myself, but I'd be curious to know if others have, and if this fix works.]
    •    
  • Currently 1.67 / 5
  You rated: 4 / 5 (9 votes cast)
 
[9,063 views]  

A possible fix for non-functioning function key shortcuts | 8 comments | Create New Account
Click here to return to the 'A possible fix for non-functioning function key shortcuts' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
A possible fix for non-functioning function key shortcuts
Authored by: Highlander on Apr 10, '09 07:52:20AM

Just press F11 (show desktop) twice.



[ Reply to This | # ]
A possible fix for non-functioning function key shortcuts
Authored by: damo1977 on Apr 10, '09 08:40:00AM

Strangely I have the opposite problem. Command C hasn't worked for copying on my macbook for over a year. Cut and Paste work fine, but not copy. Any ideas?



[ Reply to This | # ]
A possible fix for non-functioning function key shortcuts
Authored by: palahala on Apr 10, '09 09:43:48AM

So you don't see the Edit menu flash either when pressing Cmd-C? And is Cmd-C still listed as the shortcut in the Edit menus?



[ Reply to This | # ]
A possible fix for non-functioning function key shortcuts
Authored by: simplyelectric89 on Apr 10, '09 10:47:03AM

I have weird simular issue, but it only effects hardware control. At certain points when I restart my computer, I can't change the brightness of my keyboard or my display brightness, and weirdly enough it also disables to power button.

15" Macbook Pro (late 2008)

I have some network drives that mount on boot and I also have spaces enabled. I think that when one of those drives fails to mount that the error comes up on a different space and that somehow disables the buttons until it is dismissed. I do this stuff for a living and I have never seen anything like it.



[ Reply to This | # ]
A possible fix for non-functioning function key shortcuts
Authored by: bedouin on Apr 10, '09 04:22:41PM

I have this every once in a while. Since I have Expose mapped to two of my mouse buttons that fails to function along with the keyboards triggers.

Logging out and logging back in works as efficiently as restarting.

I'll try this hint though next time it occurs; hopefully it works.



[ Reply to This | # ]
A possible fix for non-functioning function key shortcuts
Authored by: guns on Apr 11, '09 03:42:22PM

Since the Dock is the parent process for Dashboard, killing the Dock process normally kills the Dashboard too (with signal SIGINT or SIGHUP). It always relaunches too, since it is marked as a persistent process for launchd.

I have had a few problems with keyboard focus and with the application switcher not showing up (Command-TAB); Killing the Dock solves these problems every time.



[ Reply to This | # ]
A possible fix for non-functioning function key shortcuts
Authored by: cwanja on Apr 11, '09 09:11:56PM

I have had (and just had actually) an issue where the short cuts to minimize a window and ect... would not work. I simply restart Finder and got it going back. This might be directly related to you or not. I will look into a possible Dashboard connection as well.

On a MacBookPro5,1 - the UniBody ones.

---
´ú┐ MacBook Pro 15" Aluminum Unibody 2.8
Chris Wanja
chris.wanja@mac.com



[ Reply to This | # ]
A possible fix for non-functioning function key shortcuts
Authored by: Anonymous on Apr 13, '09 10:35:22AM

Hm. A workaround described as a "fix". Not good.



[ Reply to This | # ]