Bug 222919 - Juk: clicking on Album name of current played song produces list with false entries
Summary: Juk: clicking on Album name of current played song produces list with false e...
Status: RESOLVED WORKSFORME
Alias: None
Product: juk
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Scott Wheeler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-16 01:29 UTC by Franciszek Janowski
Modified: 2021-03-24 01:26 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Franciszek Janowski 2010-01-16 01:29:03 UTC 
Version:            (using KDE 4.3.4)
OS:                Linux
Installed from:    openSUSE RPMs

Steps to reproduce:

1. Create a list with several mp3's, all must have same Album in the id3tag.
2. Play any song.
3. Click on Album name, that displays as a link, this should filter the list and show only songs from given album.
4. Note, that some songs in the new filtered list exist twice, the first entry is much shorter, e.g. 0,14 min, the second entry is for full length song.

Expected behaviour: A list of songs from given album, without false entries that doesn't exist as a file.
Comment 1 Michael Pyne 2011-04-25 04:16:42 UTC 
I can verify the behavior is not correct -- I only get one song (the playing song) listed even though many others are present.

I do not get invalid entries however, not that it would be the first time JuK has ever made improper PlaylistItem*'s :(
Comment 2 Jan Gerrit Marker 2011-08-10 09:47:42 UTC 
Hi, I can't reproduce the bug with Juk 3.7. Is it reproducible for you with that version?
Comment 3 Justin Zobel 2021-03-09 06:26:59 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 4 Michael Pyne 2021-03-24 01:26:03 UTC 
I haven't been able to reproduce this in years, though I have refactored this code a bit to fix some other bugs which should hopefully address this as well.