Custom keyboard shortcuts do not work if they use the Super key

[Paddy Landau]

Prior to Precise 12.04, you could use the Super key in shortcuts, for example Ctrl-Super-M.

However, with 12.04, if you set a shortcut with Super, it simply does not work. There is no error message; it just doesn't do anything.

To duplicate:

First, ensure that zenity is installed (it should be, by default).

Second, create the shortcut:

1. System Settings > Keyboard > Shortcuts > Custom Shortcuts
2. Press "+".
3. Name: Test
4. Command: zenity --info --title='Test' --text='Testing shortcuts'
5. Apply.
6. Click on "Disabled".
7. Press Ctrl-Alt-M

Third, test it:

1. Press Ctrl-Alt-M
2. A dialogue displays.
3. Close the dialogue.

Fourth, use the Super key:

1. Click where it says "Ctrl-Alt-M"
2. Press Ctrl-Super-M

Fifth, test it again:

1. Press Ctrl-Super-M
2. Nothing happens.

What should happen: A dialogue displays.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Mon May 7 11:39:23 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu3
 deja-dup 22.0-0ubuntu2
 gnome-bluetooth 3.2.2-0ubuntu5
 indicator-datetime 0.3.94-0ubuntu2

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jo-Erlend Schinstad (joerlend.schinstad-deactivatedaccount)]

I am not able to set a custom keyboard shortcut using any combination with Super. No difficulties otherwise. However, there is an exception; I can use super+0 to switch to another workspace. That slot is unused on the launcher. Very strange. In a guest user, I emptied the launcher completely, and then I could assign super+num to switch between workspaces, though it didn't seem to work immediately.

Weird bug. I think it'll need some thorough testing.

[Paddy Landau (paddy-landau)]

More information...

It seems to be related to the category of the shortcuts.

For example:

If I set (say) Super-D as a shortcut in one of the main categories (e.g. Launchers > Launch Terminal), then the Super key works.

But if set in the Custom Shortcuts, then the Super key will not work.

See http://ubuntuforums.org/showthread.php?p=11922661#post11922661

[Keng-Yu Lin (lexical)]

A gnome-settings-daemon package with the patch in the comment 13 is available at the PPA (https://launchpad.net/~lexical/+archive/gsd/) for testing.

[Simon Volpert (sacredpathwalker)]

I have installed the gnome-settings-daemon package from the ppa, killed the gnome-settings-daemon process and waited for it to respawn; the custom keyboard shortcuts began working immediately.

[Gavin van Lelyveld (mdcore+launchpad)]

I just installed the gnome-settings-daemon package from the ppa, killed the gnome-settings-daemon process, waited for it to respawn, then tried, but my custom shortcuts are still taken by the dock. I'm trying to rebind Super+<1, 2, 3, 4, etc> to workspaces, but the dock apps launch instead.

[Keng-Yu Lin (lexical)]

If you have the shortcuts work in Unity 2D, it could be another issue in Unity or Compiz (as mentioned in bug 950160).

[Paddy Landau (paddy-landau)]

I have tried this in Unity, Unity 2d and even Gnome Classic (No Effects).

They are all the same.

[Attila Hammer (hammera)]

Keng-Yu, I tryed your patched package version in GNOME Classic no effects session, my system working wonderful.
If I defined a custom command, super+h association for example work my system. My friend asked me I look this association for example the Pcm file manager to open he's machine this file manager the home folder, this type command he's system not worked.
Before not installed your patched package version, I see same issues. Other type shortcuts works, for example CTRL+ALT+Letter based shortcuts.

Hopefuly your fix will be committed in the Precise branch.

Attila

[Simon Volpert (sacredpathwalker)]

An update to my last comment; After killing the gnome-settings-daemon, the custom shortcuts begin working *for the remainder of the session*. Logging out or rebooting resets the behavior, until gnome-settings-daemon is killed again.

[ChrisKelley (ckelley)]

Does this mean we can login, find and kill gnome-settings-deamon and that will work? I use Autokey-qt and am quite vexed at Super+T interfering with my normal macros.

[Simon Volpert (sacredpathwalker)]

@ckelly Only if you have the PPA build of gnome-settings-daemon installed, which is a few versions stale. In addition, killing gnome-settings-daemon has some unfortunate consequences of having any application that depends on it for configuration fall back to defaults, unless restarted as well (this is most noticeable in Nautilus).

An update to my recent comments: The bug in question affects *ONLY* key shortcuts set via the Settings->Keyboard->Shortcuts dialog; any shortcuts defined directly in CCSM (Commands page) or via Ubuntu Tweak (Admins->Shortcuts) work as intended even if they use Super as one of the keys. This can be used as an effective workaround, permanently.

[Israel Dahl (israeldahl)]

Still a bug.

[Paddy Landau (paddy-landau)]

On 2012-05-30 the status was changed to Incomplete.

However, that question was answered; so shouldn't the status be reset to Confirmed?

[Keng-Yu Lin (lexical)]

I am making this bug as a duplicate of bug 950160 as I think it makes sense.

If anyone has other finding, please re-open the bug as a separate one.

[Paddy Landau (paddy-landau)]

This bug is not exactly a duplicate of bug #950160, as I can still create keyboard shortcuts with the Alt key (e.g. Alt-Y).

As I do not know the technical underpinnings, would the resolution of bug #950160 also fix this bug?

If so, marking this as a duplicate is valid; if not, this is not a duplicate.