Keyboard Shortcut Needs Two Taps

I just turned on Super L and I am not seeing the problem. What version of GnoMenu are you using? Are you using a 32 or 64 bit version of Linux and what flavor?

Sorry, should have included those details...

gnomenu 2.9.0-1~ppa1
Distributor ID: Ubuntu
Description: Ubuntu 10.04.1 LTS
Release: 10.04
Codename: lucid

On Mon, Sep 13, 2010 at 8:08 AM, technoshaun <email address hidden> wrote:

> I just turned on Super L and I am not seeing the problem. What version
> of GnoMenu are you using? Are you using a 32 or 64 bit version of Linux
> and what flavor?
>
> ** Changed in: gnomenu
> Status: New => Triaged
>
> --
> Keyboard Shortcut Needs Two Taps
> https://bugs.launchpad.net/bugs/636632
> You received this bug notification because you are a direct subscriber
> of the bug.
>

I'm using the same setup and I'm not experiencing the issue at all. However, I'm using 32 bit so if you're using 64 bit then there may be an issue there. If not then there might be a conflicting app that is also trying to use the Super L key (Compiz-Fusion for example) which can cause issues like this. You may want to check your system and login start up lists to see if this may be the case.

I'm 32-bit as well... no conflicting apps. :-(

On Tue, Sep 14, 2010 at 6:41 PM, technoshaun <email address hidden> wrote:

> I'm using the same setup and I'm not experiencing the issue at all.
> However, I'm using 32 bit so if you're using 64 bit then there may be an
> issue there. If not then there might be a conflicting app that is also
> trying to use the Super L key (Compiz-Fusion for example) which can
> cause issues like this. You may want to check your system and login
> start up lists to see if this may be the case.
>
> --
> Keyboard Shortcut Needs Two Taps
> https://bugs.launchpad.net/bugs/636632
> You received this bug notification because you are a direct subscriber
> of the bug.
>

I have the exact same issue, and it seems to be caused by an intentional 'every other time' code block in globalkeybinding.py. I'm sure there was a legitimate purpose for this, but removing it fixes this problem for me. Here's a patch.

There is one remaining issue, which has to do with not detecting the current state of the menu. This scenario still exhibits incorrect behavior:

# open menu by pressing bind key
# close menu by clicking panel icon
# pressing bind key again should open menu, but it does not

my guess would be that there's some saved state somewhere (an open/closed toggle) that's being bumped out of sync by alternating between the mouse click and keyboard press.