Audacious - OLD, PLEASE USE GITHUB DISCUSSIONS/ISSUES

It seems I cannot edit the description.
The steps to reproduce should read as follows (not crossed out!):

Steps to reproduce:
1) Play a song with an embedded album cover and the Desktop Notification plug-in active.

A notification with the album cover will be shown

2) Without closing Audacious, play another song that doesn't contain one.

A notification with the album cover of the previous song will be shown.

Michael Steenbeek wrote:

It seems I cannot edit the description.
The steps to reproduce should read as follows (not crossed out!):

Steps to reproduce:
1) Play a song with an embedded album cover and the Desktop Notification plug-in active.

A notification with the album cover will be shown

2) Without closing Audacious, play another song that doesn't contain one.

A notification with the album cover of the previous song will be shown.

I couldn't reproduce it in version 3.6-beta1 on Arch Linux.

I just tried version 3.6-beta1. This version shows the correct generic icon if you stop the current song first and then play another, but still shows the wrong cover if you start the new song while the old one is still playing.

I tried playing another song while the old one (with the cover) is still playing and works as expected for me. Did you compile also "audacious-plugins" 3.6-beta1?

I've just installed audacious and audacious-plugins 3.5.2 and couldn't reproduce the error. It may be an environment problem? I will go on trying to reproduce it.

My OS is Ubuntu 14.10, x86_64. I always use the Winamp interface. My audacious-plugins are also at 3.6-beta1.
Tested it again today with the following files, in this order:
1) One with an album cover
2) One without
3) Another one with an album cover
4) Another one without

Strangely, it did correctly show a generic icon for file 2, but not for 4. Apparently it doesn't happen with every file.
Perhaps you can reproduce it with several files in a row?

The commit you pointed to solves another problem entirely. The problem here is not that the notify plugin shows an old notification, but that it shows a notification for the current song with the album cover of the previous one.

Wait. Seems I spoke a bit too soon. Sorry about that.

It seems that in the commit has solved notifications showing the wrong album cover.

There is just a little thing though: with this patch, changing the song when the old notification is still on the screen does not cancel the old notification.
Meaning that, if you skip a few times, it will show notifications for all the songs you skipped, one after another. (To see this, start a playlist, then press Skip five times or so). Hopefully this can be ironed out as well before the release of 3.6.

That's a bug in your notification daemon. Nothing we can do about it.

It didn't do that before applying the patch, though.

Or, more specifically: it didn't do that in the 3.6beta1 version, compiled by Webupd8, that I used before checking out Git and compiling.

Of course it didn't. It used to reuse the same notification; that's why you saw the old album art hanging around. The only way to fix that problem is to create a new notification, and then you have the possibility of the old notification hanging around. There's no perfect solution.