Comment 5 for bug 988699

To understand what's going on, I created a wrapper shell script that redirects output from gnome-do. Ouput captured this way shows that during the session login, gnome-do is failing to bind <Super>space. The following message gets reported twice:

  (Do:16097): libd-WARNING **: Binding '<Super>space' failed!

If I add "sleep 3" to this shell script and delay the launch of gnome-do, it will bind correctly. So I'm currently using this as a work around.

Based on these observations, I wonder if Unity is grabbing <Super> before it reads my keybinding customization and releases it, and Gnome Do happens to be initializing at the same time or something. I don't really have any evidence for this, but I can't think of anyone else who's grabbing <Super>space.

I hope it aids the maintainers in tracking down the root cause.