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 337832 - Confused when trying to use the windows key for shortcuts
Confused when trying to use the windows key for shortcuts
Status: RESOLVED DUPLICATE of bug 165343
Product: gnome-control-center
Classification: Core
Component: Keyboard
unspecified
Other All
: Normal minor
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-04-09 18:25 UTC by elitepenguin
Modified: 2007-05-04 22:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description elitepenguin 2006-04-09 18:25:27 UTC 
Something should be mappped to it so you can use it by default for shortcuts
like win-m (to minimize windows).

I learned about that when I first asked somewhere in IRC. I had to go to
System->Preferences->Keyboard->LayoutOptions then map something to my windows
key, after that I could use it normally in the shortcuts dialog.

Today there was a user asking the same (not sure if on #ubuntu+1 on freenode or
on #gnome on the gimp network), so I'm not the only person who was confused by that.

Other information:
Comment 1 Vincent Untz 2006-04-15 06:38:30 UTC 
Moving to control-center.
Comment 2 Raptor Ramjet 2007-05-04 19:07:13 UTC 
I'm also trying to map "Windows Key" & "E" to launch Nautilus but when I press the key combination in "Keyboard Shortcuts" it displays "Super L" for the keyboard shortcut.  Subsequently pressing the "Windows Key" on it's own launches Nautilus.  Not what I'm after at all !

Most Windows "Power users" will be used to using things like "Win-E" to start Windows Explorer, "Win-M" to minimise all windows etc. so it would be nice to be able to set up the same keyboards shortcuts in GNOME.
Comment 3 Thomas Wood 2007-05-04 22:25:09 UTC 
Same issue as bug 165343. Please see the comments on that bug for more information and discussion.

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