Unable to remap keyboard shortcut for F1

Bug #1179543 reported by Kyle
54
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Unity
Invalid
Undecided
Unassigned
unity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I am unable to remap the F1 keyboard shortcut on Ubuntu 13.04 using the Unity interface. This is what I have tried:

System Settings -> Keyboard -> Shortcuts -> Navigation -> Switch to workspace 1 -> click on keyboard binding

When I try to define a new accelerator using the 'F1' key (which on my keyboard happens to alos have the 'Help' function on it), it spawns the Ubuntu Desktop Guide and nothing gets registered as a keyboard mapping. I can't find a way of defining the 'F1 (help)' key as an accelerator.

Any workarounds?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity (Ubuntu):
status: New → Confirmed
Revision history for this message
Warren H (swift-raptor) wrote :

I have exactly the same problem as the bug description above. :(

Revision history for this message
Bjorn Solberg (bjorn+launchpad) wrote :

I have the same problem. This affects my user experience a lot, as I tend to use my shortcut a lot (F1 = bring window to top). Is there any time frame for when this will be fixed, or how I may go about working around it to take back F1?

Thanks,

Bjorn

Revision history for this message
David Somach (dsomach) wrote :

+1, I have been using F1/F2 for workspace switching for a few years, so this is a productivity killer for me :(

Revision history for this message
David Somach (dsomach) wrote :

This isn't an ideal solution, but I ended up remapping F1 to a key I never use (F7) and remapped F7 to F1, so my standard keyboard shortcuts for F1/F2 are now mapped to F7/F2, and I don't need to change an old habit!
(http://askubuntu.com/questions/24916/how-do-i-remap-certain-keys)

Changed in unity:
status: New → Confirmed
Revision history for this message
Seth Johnson (sethj) wrote :

As part of the big bug review for 16.04 LTS I have tested this on 15.10 and the bug is still there. The system settings happily accept F1 as a proper binding and it worked as expected.

Changed in unity:
status: Confirmed → Invalid
Changed in unity (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.