Please follow the steps below and check the boxes with [x] once you did the step.
Please provide information about your system and the version of Clementine used.
When playing a long playlist in "non-repeat" and "random: all" some songs (roughly half) are repeated twice. The expected behaviour would be that songs are only played once, and certainly not repeated immediately when "non-repeat" is selected.
Can reproduce on every Clementine 1.3.1 I tested: openSUSE Leap/Tumbleweed and Kubuntu.
I have the same issue, on Ubuntu and Lubuntu 16.04, 32 and 64 bit
I too have the same issue on Ubuntu 16.04, 64 bit.
Bug seems to be a duplicate of #5523. Can everyone confirm that WMA (or possibly AAC) songs are involved in triggering the bug? The problem is that the bug is not triggered when you select the file manually, so you have to wait for it to happen and check the track before the one that was played twice.
I can confirm that this annoying bug is related to WMA format. It appears when playing non-manually selected songs.
Ubuntu 16.04, 64 bit, Clementine 1.2.3
I have the issue with mp3 and flac songs
@gavelez Are you sure? Not that the song that is repeated can be of any format (including MP3), but the song before the repeated is always a WMA.
I have this same issue Clementine - V 1.3.1 Mac OS 10.12.3 (16D32)
I have a mix of MP3 and WMA files in the my playlist. Set to shuffle.
1.3.1 on Mac 10.11.6. To me it is a WMA related bug. It happens as follow:
Step 1. Use Previous OR Next to jump to play a WMA song;
Step 2. When this WMA song (noted as Song A) finishes. the next song (noted as Song B) will be played but the "current track" highlighting is still on the just-finished WMA Song A;
Step 3. When Song B finishes the first time, the "current track" highlighting will then move from Song A to Song B, and start to play Song B again.
During the Step 2 above, if the seek bar is used to jump to the end of Song A, the "current track" highlighting will move to the next song correctly and thus the bug will not be triggered.
Thanks @freezelty that's a very accurate bug description. I was able to reproduce it:

Using next:

Waiting until the WMA track ends:

Currently Iron Man - Black Sabbath (FLAC) is already playing, but the interface shows still the WMA track.

Iron Man is played twice. First with the old track displayed, and second with the correct track displayed. (By the way: ratings through a shortcut will also edit the wrong track)
So in short: If you switch to a WMA track, the track after that will be repeated.
I'll do the workaround and just convert my WMA files.
Same here (Debian 9, Clementine 1.3.1 too), for so long now. So glad I've finally found this issue 馃槃
@freezelty, @Jeybla a big thanks to you. It's WMA-related, indeed 馃憤
But as mentionned in #5523, it happens only when the track is randomly played (not manually queued for instance).
Same here with .ogg files
I have a list of .wma-only files.
It looks like there is something wrong with this marker for some reason.
Clementine: 1.2.3
Qt: 4.8.7
Linux Mint 18.2 Sonya (using the default ubuntu xenial repos in the background)
I have this issue with Clementine 1.2.3 on Ubuntu 16.04 64-bit when playing .wma files.
I have this issue with wma files on Clementine 1.3.1 on MX Linux 17.1.
Sounds like duplicate of #3924 (though this one is better described, so if anyone is actually closing duplicates then targeting #3924 would be likely a better idea)
Most helpful comment
1.3.1 on Mac 10.11.6. To me it is a WMA related bug. It happens as follow:
Step 1. Use Previous OR Next to jump to play a WMA song;
Step 2. When this WMA song (noted as Song A) finishes. the next song (noted as Song B) will be played but the "current track" highlighting is still on the just-finished WMA Song A;
Step 3. When Song B finishes the first time, the "current track" highlighting will then move from Song A to Song B, and start to play Song B again.
During the Step 2 above, if the seek bar is used to jump to the end of Song A, the "current track" highlighting will move to the next song correctly and thus the bug will not be triggered.