Comment 9 for bug 963805

I pushed up a new revision to lp:recent-notifications which I think may fix it if you could test it out. Just run it locally as in the previous comment, no need to uninstall anything. Just want to make sure it is actually working before pushing out a new version. (It works with my tests, but I don't have chromify-osd so I may be missing something).

I added a bit of code to check the modified time of the file, and load a new icon if it changed. I think this is probably the correct way to handle it at our end. It is entirely possible an icon may be updated, so we shouldn't assume the cached version is always fresh.

As for chromify-osd, the way this is normally handled, where icons change frequently (such as with pidgin and gwibber), is to embed the image into the notification using the image_data hint (see the Formats section of http://developer.gnome.org/notification-spec/#icons-and-images ). But it may not be possible for chromify-osd to do that, I don't know, so hopefully the latest changes should fix it on recent-notifications side.