Notification stays when --id is used and triggered too fast

[macxcool]

I'm using i3 and have a notification when entering a mode with --id and also a notification on launching something from that mode using the same --id so the notification is replaced. If I trigger the mode and then hit a hotkey to launch a program too quickly the second notification stays until I click on it even though it's set with a 1s timeout.

[hellojoe88]

Tried reproducing:

1. Assign hotkey in ir with bindsym $mod+p exec --no-startup-id twmnc --id 1 -c "Hello hello"
2. Launched twmnc --id 1 -c "Hello" from terminal
3. Pressed hot quikly after (within same second)

But the message doesn't stay. It just dissapears as expected.

Does this issue still exist for you?

[AndrewBastin]

@joekienzle I am facing the same issue too. Firing notifications with an id repeatedly, makes the notification stay there. If I fire one more request to the same ID after a small interval, it will work properly again though.

[Penguin-Guru]

When no message is displayed and I invoke twmnc --remote previous, there is a three second delay and then the bar shoots out and back in quickly. If I try invoking the same command again during that period, the three second delay is extended until three seconds after the last invocation. Seems related?

[Penguin-Guru]

@AndrewBastin I've made a few changes on my Github (esp. Working branch) that may or may not have helped with these issues, but I'm not a programmer so try at your peril. There is at least one of these sticky bugs left, specifically with a very short --remote hide window, so I assume there is some underlying issue that has not been addressed.