-
Notifications
You must be signed in to change notification settings - Fork 356
stack tag notifications do not use the new icon #1471
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hello thanks for pointing this out. Is this a regression or was this introduced in the new dunst version? Also does notify-send beahve differently than dunstify? |
@bynect I don't know it's a regression just recently find out about stack tag and notify-send and dunstify behave similarly |
I can reproduce this issue. it is very strange that it happens only when the stack tag is set. I will investigate |
it seems to be caused by the way that tagged notifications are treated, which is different than normal duplicates |
I found the cause. it is in the way icons are compared that checks just the path name. I will try to come up with a solution without compromising performance |
if you want to try I changed the way duplicate icons are checked in #1473 |
Hey,
basically if the provided icon of a icon file is updated next notifications will use the old icon
How to reproduce
$ notify-send -h string:x-dunst-stack-tag:test -i tmp.jpg "123"
tmp.jpg
fileSystem information
dunst version:
1.12.2 (2025-03-05)
Linux distro: Archlinux
The text was updated successfully, but these errors were encountered: