Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 80572 - gnome-keybinding-properties doesn't allow bindings to be removed
gnome-keybinding-properties doesn't allow bindings to be removed
Product: Red Hat Public Beta
Classification: Retired
Component: control-center (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jonathan Blandford
David Lawrence
: Triaged
Depends On:
Blocks: 79579
  Show dependency treegraph
Reported: 2002-12-27 22:00 EST by Need Real Name
Modified: 2013-04-02 00:17 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-14 16:41:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2002-12-27 22:00:05 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218

Description of problem:
When you click an action to configure, the text shown is "type a new
accelerator, or press backspace to clear".  If you press backspace, it says
"That accelerator key is already in use by: /apps/panel/global/run_key"

Either backspace should not report as already bound, or another key should be
specified in order to clear the binding.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Start gnome-keybinding-properties
2.click an action to change
3.hit escape

Actual Results:  The program reports that escape is already bound

Expected Results:  the actions current binding should be removed

Additional info:
Comment 1 Havoc Pennington 2003-01-02 17:24:18 EST
This is fixed already in newer upstream versions, we just need to get a 
new version.
Comment 2 Jonathan Blandford 2003-01-14 16:41:46 EST
Fixed in Rawhide/CVS

Note You need to log in before you can comment on or make changes to this bug.