linux-traipu team mailing list archive

[Kohsuke Kawaguchi <kk@xxxxxxxxxxx>]

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.

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Do.
https://bugs.launchpad.net/bugs/988699

Title:
  Does not grab <super>-space after login

Status in Do:
  New

Bug description:
  After upgrade to Ubuntu 12.04 (Unity) gnome-do does not grab
  <super>-space on login (I have Start GNOME Do at login and quiet mode
  set to true) but the process is running (as evidenced by ps -ef|grep
  gnome-do). If I then kill gnome-do and start it again (from term with
  gnome-do&) it starts grabbing <super>-space.

  Let me know how I can provide logs for this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/do/+bug/988699/+subscriptions