Problem creating shortcuts with super-key (win-key/mod4)

I have set up the shortcut to launch "Home folder" as Mod4+E (corresponds to super+e (or winkey+e)), but to actually open my home folder I need to press super+e+e . When pressing super+e (or most other letters) I get a small gray input box in the buttom left corner, which is almost complety covered by the buttom panel. Super+d works fine for showing the desktop.

[wulftone]

+1, this is quite annoying. Exactly the same issue. I'm using cinnamon 1.4 as just updated on LMDE Update Pack 4

[tamland]

This is an issue inherited from gnome3/mutter. A workaround is to set the "overlay-key" property to empty or some other key. You'll loose the built-in shortcuts though.

Gnome
using dconf-editor: /org/gnome/mutter/overlay-key

Cinnamon
using gconf-editor: /apps/gnome/muffin/general/overlay-key

[wulftone]

thanks, that works. it would be nice to get a solution instead of a workaround, but this will do for now.

[rcrath]

SUperkeys and shortcuts were working in Cinnamon 1.4 on top of gnome 3.2 but has stopped on LMDE update pack five because of an update to gnome 3.4 in which the shortcuts are moved completely to dconf, but the keys for deconf dont work. The former solutions offered no longer fix the problem because the dconf keys are not being registered, so the shortcut keys just don't work.
The problem is upstream and a combination of foulups on Ubuntu and gnome regarding the transition or lack thereof from gconf to dconf that seem to cover up the actual problem. responsibility for shortcuts in gnome 3.4 is turned over to dconf, but the keys in dconf are broken:

$ gsettings get org.gnome.settings-daemon.plugins.media-keys custom-keybindings

returns the plugin keys as being stored in custom0...customN, but

$ gsettings get org.gnome.settings-daemon.plugins.media-keys.custom-keybindings.custom0 binding
(or command or name instead of binding) returns
No such schema 'org.gnome.settings-daemon.plugins.media-keys.custom-keybindings.custom0'
even though I can see it in dconf. That is my guess as to where the problem is.

I know this is a gnome problem, but It would be great if this could be resolved in Cinnamon, cuz gnome and ubuntu devs don't seem to be interested in fixing for a few more versions.

[rcrath]

release notes to version 3.5.3 of gnome settings daemon say "Media-keys:

• Make keyboard shortcuts work again". see
  http://ftp.acc.umu.se/pub/GNOME/sources/gnome-settings-daemon/3.5/gnome-settings-daemon-3.5.3.news
  and
  http://ftp.gnome.org/pub/GNOME/sources/gnome-settings-daemon/3.5/
  but requires gnome 3.5.3 and a bunch of other stuff.
  It would be great if this fixes it and could be incorporated into Cinnamon

[shred]

This is really a showstopper for Cinnamon 1.6, IMHO. I used the "Keyboard" settings to use Super-1 to move to workspace 1, Super-2 for workspace 2 and so on. However, these shortcuts do not work any more now, so I cannot quickly change workspaces any more.

However, when I change the keyboard shortcut to something different (like Ctrl-1) it still doesn't work, so it seems to be not just an issue with the super key.

[mtwebster]

We are working on a keyboard page for Cinnamon Settings that will allow proper setting of keyboard shortcuts, hopefully in time for 1.6.1

[wulftone]

+1 to the 1.6.1 keyboard settings, I couldn't even get any keyboard shortcuts to change workspaces on cinnamon 1.6 from the Romeo repos

[svenjacobs]

Customizing Cinnamon keyboard shortcuts is greatly appreciated and anticipated. For example do CTRL+ALT+Left and CTRL+ALT+Right conflict with my favorite IDE.

[acherep]

+1. I really like Cinnamon together with LM13. However, after the update from Cinnamon 1.4 to 1.6.0 (or 1.6.1), my favorite super-shortcuts stopped working :( Sad to say, I had to reinstall LM13 to get it back.

[LunaticoCR]

I don't understand, I see this was closed but was it implemented?
I'm running Cinnamon 1.6.1 and I still can't use the Super key for shortcuts.

[mtwebster]

There is now a keyboard settings page in Cinnamon Settings, from which you should be able to set keyboard shortcuts properly. I don't recall if this was implemented before or after 1.6.1 though, I recommend you upgrade to the latest version.