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 604423 - Ctrl+alt+d binging corrupted
Ctrl+alt+d binging corrupted
Status: RESOLVED DUPLICATE of bug 145272
Product: gnome-control-center
Classification: Core
Component: [obsolete] Keybinding
2.28.x
Other Linux
: Normal major
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-12-12 05:28 UTC by cyberkm
Modified: 2009-12-13 10:02 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Disabled ctrl-alt-d shortcut (41.37 KB, image/png)
2009-12-12 05:28 UTC, cyberkm 		Details

Description cyberkm 2009-12-12 05:28:25 UTC 
Created attachment 149623 [details]
Disabled ctrl-alt-d shortcut

When switching to "programmers dvorak" keyboard layout the shortcut ctrl+alt+d stops working, instead it continues to work when pressing the ctrl+alt+e. (In dvorak layout the "E" button is located on the qwerty's "D" position). Because of it I am unable to use "C-M-E" shortcut in emacs. It simply minimizes all windows and brings up the desktop.

It looks like this shortcut is ignoring layouts of the keyboard. So I tried to disable the shortcut (see atachment), but it still focuses the desktop.

How to reproduce:
1. Switch to the programmers dvorak layout on the keyboard.
2. Press Ctrl+alt+d -> nothing happens
3. Press Ctrl+alt+e -> all windows minimized and desktop appears
4. Press ctrl+alt+e again -> All windows are restored.
5. Repeat steps 3--4 as long as you like.
6. Go to Menu -> System-> Preferences - Keyboard shortcuts
7. Select "Hide all normal windows and set focus to the desktop"
8. Press Backspace to disable the shortcut.
9. Goto step 5.
Comment 1 Jens Granseuer 2009-12-13 10:02:25 UTC 
The fact that the shortcut still works after disabling it is a bug in metacity (supposedly already fixed in recent versions).

The rest is already filed elsewhere, too.

*** This bug has been marked as a duplicate of bug 145272 ***