Shortcut working only in a special typing order

[JBP]

Hi,
I've just installed Diodon on ubuntu 14.04, and I ha some troubles ith the shortcut. It' s now set to <Shift><Alt>A.

When I press "a" first, then Shift and Alt, it displays the menu (but it types an "a" too).
But when I began my shortcut by somethings else than "a",, either Shift or Alt the menu doesn't appear.

I got a similar problem for <Ctrl><Alt>V

Would someone have an idea why ?

Best,

[Oliver Sauder (sao)]

I cannot reproduce this problem on my machine. We have been working on the shortcut change though which might fix this issue.

Can you test it whether you have this issue with the daily ppa version https://launchpad.net/~diodon-team/+archive/ubuntu/daily as well?

[JBP (jeanbaptiste-pham)]

Hello,
Thank you very much, I've just tested the daily ppa version, and now it
works perfectly well !
Diodon is a great software, I'm happy to keep using it !
Best,
Jean-Baptiste Pham

On 07/10/14 12:50, Oliver Sauder wrote:
> I cannot reproduce this problem on my machine. We have been working on
> the shortcut change though which might fix this issue.
>
> Can you test it whether you have this issue with the daily ppa version
> https://launchpad.net/~diodon-team/+archive/ubuntu/daily as well?
>

[Oliver Sauder (sao)]

Good to hear that it works now.

Closing this issue then.

[Daniel Röhrig (roehrig-daniel)]

Reopening this bug report, because it's still an issue on my system (Elementary/Ubuntu 14.04) with the daily ppa. The order in which I press the keys determines whether the menu shows or not.

[Thierry (thdox)]

I am on Debian Jessie, aka testing, aka Debian 8, and I confirm the bug. Here are some additional informations, that may (or not) help.

I have set the keybarod shortcut to: <Ctrl><Alt><Shift>w

1. Order does not matter
I have tried to press Ctrl, *then* Alt, *then* Shift, *then* w. I have tried all the combinations of Ctrl-Alt-Shift, w is always last. I have found that all combination may fail. I have not found a combination that always work.

2. Pressing several times *does* help
When I say several times, I mean "I let <Ctrl><Alt><Shift> pressed, and hit 'w' several times"
What I have found is that pressing 2 times or sometimes 3 times the combinationonce will finally bring the popup.

[Thierry (thdox)]

This may be related to bug 1435032

[Oliver Sauder (sao)]

To clarify: this issue has initially been reported to happen on Unity.

This issue should have been fixed though for Unity and GNOME in Diodon version 1.3.0 as those desktop environment provide a special service to grab hotkeys which Diodon has implemented. All other desktop environments still suffer from this issue as Diodon uses the fallback of grabbing keys through X.org.

[Thierry (thdox)]

FWIW, I confirm this bug with diodon-1.3.0 on Debian 8, that is GNOME 3.14.

[Oliver Sauder (sao)]

@Thierry
Your issue might be different as it sounds like Diodon doesn't properly recognize that you are running GNOME desktop.

To verify can you run Diodon the following way:

G_MESSAGES_DEBUG=all diodon > diodon_debug.log

if issue is still reproducible attach diodon_debug.log to this issue so I can analyze. Thanks.

[Thierry (thdox)]

See attached file.
The first time I pressed <Ctlr><Alt><Shift>w, the popup appears.
The *second* time I pressed <Ctlr><Alt><Shift>w, the popup does *not* appears.
The *third* time I pressed <Ctlr><Alt><Shift>w, the popup does *not* appears.

[Oliver Sauder (sao)]

As I thought is this a different issue - Diodon doesn't seem to recognize correctly that you are running GNOME and is therefore fall back to X11 legacy mode. I have opened bug 1439804 for this. Leaving this issue open for other DE.

[Oliver Sauder (sao)]

Decision has been made to drop the internal Diodon hotkey feature and leave the responsibility of register a custom shortcut up to the desktop environment.

You can find more details here how you can do this:
https://esite.ch/2015/07/using-custom-shortcuts-of-de-as-diodon-hotkey/

Depending on the DE you use but the typing order should not matter anymore otherwise would it be an issue of the specific desktop environment.