Open ayushjaipuriyar opened 2 months ago
Can you check with bustle
is the action is indeed taken rather than this being something else? Also, do you use the legacy notification module or the new one (aka, do you have a naughty.connect_signal("request::display"...
section in your config, which indicates the new one is used)
Can you check with
bustle
is the action is indeed taken rather than this being something else? Also, do you use the legacy notification module or the new one (aka, do you have anaughty.connect_signal("request::display"...
section in your config, which indicates the new one is used)
I am using the new one, as I have that line in my configs. And yes in bustle, it shows like
I'm on current master and I've noticed that even when you right click on the notification (used to just close it) now it execute the action anyway. Might be related?
I'm on current master and I've noticed that even when you right click on the notification (used to just close it) now it execute the action anyway. Might be related?
could be we might have been able to figure out which may be causing this Reddit link pull request
I think https://github.com/awesomeWM/awesome/pull/3906 tries to fix this behavior.
I merged the PR, please update and retry
I merged the PR, please update and retry
Apparently did not fix the issue. Currently, as soon as the timeout of the notification finishes the action is executed.
How to reproduce the issue:
Actual result:
Expected result:
This wasn't the case earlier, but in the recent commits this started to happen.