I have this issue with Lenovo Thinkcentre Edge. Its keyboard has Fn key, which acts in my Ubuntu (with Fluxbox) as if it is always "active/pressed".
I can't use standard F1-F12 keys unless I hold down this stupid key. You see, I'm a programmer so it's really pain to me.
So I decided to remap function keys with xev and xmodmap
I remapped F1-F3 and 'till this point everything is fine, but F4 does some kind of window minimization. When I run xev and hit F4, I don't get a reply from the program with a keycode and stuff, instead the window is minimized and when I maximize the window again there is no response from the key.
Important info: The function of Fn key can't be disabled in the BIOS.
So the question is: Do you have ANY idea how to solve my mystery?
EDIT:
# content of .fluxbox/keys
# click on the desktop to get menus
OnDesktop Mouse1 :HideMenus
OnDesktop Mouse2 :WorkspaceMenu
OnDesktop Mouse3 :RootMenu
# scroll on the desktop to change workspaces
OnDesktop Mouse4 :PrevWorkspace
OnDesktop Mouse5 :NextWorkspace
# scroll on the toolbar to change current window
OnToolbar Mouse4 :PrevWindow {static groups} (iconhidden=no)
OnToolbar Mouse5 :NextWindow {static groups} (iconhidden=no)
# alt + left/right click to move/resize a window
OnWindow Mod1 Mouse1 :MacroCmd {Raise} {Focus} {StartMoving}
OnWindowBorder Move1 :StartMoving
OnWindow Mod1 Mouse3 :MacroCmd {Raise} {Focus} {StartResizing NearestCorner}
OnLeftGrip Move1 :StartResizing bottomleft
OnRightGrip Move1 :StartResizing bottomright
# alt + middle click to lower the window
OnWindow Mod1 Mouse2 :Lower
# control-click a window's titlebar and drag to attach windows
OnTitlebar Control Mouse1 :StartTabbing
# double click on the titlebar to shade
OnTitlebar Double Mouse1 :Shade
# left click on the titlebar to move the window
OnTitlebar Mouse1 :MacroCmd {Raise} {Focus} {ActivateTab}
OnTitlebar Move1 :StartMoving
# middle click on the titlebar to lower
OnTitlebar Mouse2 :Lower
# right click on the titlebar for a menu of options
OnTitlebar Mouse3 :WindowMenu
# alt-tab
Mod1 Tab :NextWindow {groups} (workspace=[current])
Mod1 Shift Tab :PrevWindow {groups} (workspace=[current])
# cycle through tabs in the current window
Control Tab :NextTab
Control Shift Tab :PrevTab
# go to a specific tab in the current window
Mod4 1 :Tab 1
Mod4 2 :Tab 2
Mod4 3 :Tab 3
Mod4 4 :Tab 4
Mod4 5 :Tab 5
Mod4 6 :Tab 6
Mod4 7 :Tab 7
Mod4 8 :Tab 8
Mod4 9 :Tab 9
# open a terminal
Mod1 F1 :Exec x-terminal-emulator
# open a dialog to run programs
Mod1 F2 :Exec fbrun
# volume settings, using common keycodes
# if these don't work, use xev to find out your real keycodes
176 :Exec amixer sset Master,0 1+
174 :Exec amixer sset Master,0 1-
160 :Exec amixer sset Master,0 toggle
# current window commands
Mod1 F4 :Close
Mod1 F5 :Kill
# open the window menu
Mod1 space :WindowMenu
# exit fluxbox
Control Mod1 Delete :Exit
# change to previous/next workspace
Control Mod1 Left :PrevWorkspace
Control Mod1 Right :NextWorkspace
# change to a specific workspace
Control F1 :Workspace 1
Control F2 :Workspace 2
Control F3 :Workspace 3
Control F4 :Workspace 4
#osobni
Mod4 d :ShowDesktop
Mod4 m :Maximize
Mod4 f :Exec firefox
Mod4 u :Exec unison-gtk
Mod4 e :Exec eclipse
Mod4 t :Exec thunderbird
Mod4 q :Exec qutim
Mod4 s :Exec skype
Ubuntu is 12.04 LTS, kernel
3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Fnbehavior to be changed in any way. Your symptoms don't look like a problem with the BIOS though: the BIOS wouldn't know how to minimize a window. It looks like Fluxbox has mappedF4to minimizing a window. Please post your Fluxbox configuration, and also tell us what Ubuntu release you're using. Do you see the same symptoms on a new account with no Fluxbox configuration? What about with other window managers?Fn. I've seen many laptops that have a BIOS option to choose whether the physical key registers as F1-F12 or the extra function, since a lot of end users don't use the F1-F12 keys. Thinkpad Edge's even do this by default (you need Fn-F1 to get F1). What I meant was if this is the case, finding the BIOS option would be much easier than trying to remap each F1-F12 key individually.