After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 671236 - When setting up keyboard shortcuts there is no warning if the same shortcut is bound twice.
When setting up keyboard shortcuts there is no warning if the same shortcut i...
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: Keyboard
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-03-02 23:52 UTC by Georgiy Treyvus
Modified: 2012-08-18 04:13 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
A picture is worth a thousand words. (643.37 KB, image/png)
2012-03-03 18:32 UTC, Georgiy Treyvus 		Details

Description Georgiy Treyvus 2012-03-02 23:52:08 UTC 
This is an issue not just with mutter but metacity also.

In KDE for example you are warned and prevented from binding the same keybinding to 2 different commands. Gnome on the other hand cheerfully does so and chaos ensues. Completely random chaos.
Comment 1 Florian Müllner 2012-03-03 07:15:58 UTC 
(In reply to comment #0)
> Gnome on the other hand cheerfully does so
> and chaos ensues. Completely random chaos.

How do you set up your keybindings? Using System Settings -> Keyboard -> Shortcuts, you should get a warning when assigning an existing shortcut.
Comment 2 Georgiy Treyvus 2012-03-03 18:32:48 UTC 
Created attachment 208916 [details]
A picture is worth a thousand words.

Again a picture is worth a thousand words.
Comment 3 Florian Müllner 2012-03-03 21:44:28 UTC 
That's definitively not how it's supposed to work - reassigning to System Settings
Comment 4 Bastien Nocera 2012-03-04 01:02:46 UTC 
Works fine here. How do I reproduce? Which version of gnome-control-center are you using?
Comment 5 Georgiy Treyvus 2012-03-04 04:19:35 UTC 
This has occurred on multiple gnome installations I've tried it on. Whether the one on Debian(my current distro with version 2.30.1) or the one on the Fedora 16 live disk(from which the screenshot was taken) or Linux Mint's Mint's modified GNOME 3.

I can pop in the live disks and get the versions of those also.

Gimme a sec.
Comment 6 Georgiy Treyvus 2012-03-04 04:38:42 UTC 
Version is 3.2.1. On Fedora 16 live disk. Seem to have misplaced Linux Mint live disk but it was there too.

Again this was a problem on all version of GNOME I tried it on. I don't get how you're not having this problem? Maybe this was fixed in the still experimental GNOME 3.4 and you're runnning that...
Comment 7 Georgiy Treyvus 2012-08-18 04:13:58 UTC 
@Bastien:

I just did a test on GNOME version 3.4 on version 3.4 it works fine.

Apparently the problem is only for GNOME versions 3.2 and below.

For versions 3.4 onwards you guys perhaps inadvertently perhaps purposefully fixed the problem so a big thank you for that.

So you're right this bug can now be considered squashed unless of course you want to backport the fix to the earlier versions of GNOME as well :-P