Bug 124069 - amarok treats all audio CDs as same (adding wrong data to collection)
Summary: amarok treats all audio CDs as same (adding wrong data to collection)
Status: RESOLVED FIXED
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 1.4.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
: 125494 130580 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-03-22 13:57 UTC by madman
Modified: 2008-10-21 18:46 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description madman 2006-03-22 13:57:03 UTC
Version:           1.4-beta2 (using KDE 3.5.1, Gentoo)
Compiler:          gcc version 3.4.5 (Gentoo 3.4.5-r1, ssp-3.4.5-1.0, pie-8.7.9)
OS:                Linux (i686) release 2.6.16

There is a slight problem with Audio CD playback. Whichever CD is played by Amarok, metadata is a sum of all CDs played.
For example, I play track 1 from CD A. Then I also play the first track, but from CD B. When I play first track from CD C, amarok tells me this track has been played two times before, not taking into account that those tracks were on different CDs. Maybe it would be easiest (for the 1.4 release) to simply disable that data for audio CDs ?
Comment 1 Alexandre Oliveira 2006-06-15 07:08:33 UTC
*** Bug 125494 has been marked as a duplicate of this bug. ***
Comment 2 Alexandre Oliveira 2006-07-10 22:55:00 UTC
*** Bug 130580 has been marked as a duplicate of this bug. ***
Comment 3 Myriam Schweingruber 2008-08-06 06:48:17 UTC
Unfortunately, Amarok 1.4.x is not actively maintained anymore, as all the focus lies on Amarok 2.0.
Feel free to report any bug you should come across in Amarok 2.0.
Comment 4 Malte S. Stretz 2008-08-06 15:17:10 UTC
Myriam: Before closing this bug as WONTFIX, you should have checked whether it is fixed in 2.0 or not.  If this is fixed, close it as FIXED.  If it still happens, keep it open and add a note that you tested it in 2.0.  All those nifty new features in 2.0 don't magically fix all bugs in the backend.

I reopened it, please confirm that it is fixed before closing it.
Comment 5 Myriam Schweingruber 2008-10-21 10:41:11 UTC
Malte, it's useless to reopen this bug as development for Amarok 1.x has ended and there will be no fix for it in 1.x. Feel free to open a new bug for Amarok 2 if you come across this same behaviour. I can't reproduce it for now in 2.0 beta 2 and no developer will ever look at old 1.x bugs anymore.
Comment 6 Malte S. Stretz 2008-10-21 18:30:27 UTC
Myriam, if you could not reproduce it in Amarok 2 its fine, then the bug is probably FIXED (and not WONTFIX).

Don't get me wrong but I try the best to do bug wrangling, especially when I report them, and when people close my bugs as WONTFIX without checking for a moment if its still there its a bit annyoing.  Because as I said before, just because the version is bumped from 1 to 2 doesn't mean all old bugs are gone, especially a subtle one as this.
Comment 7 Mark Kretschmann 2008-10-21 18:36:34 UTC
Malte, actually the old bugs are gone, because Amarok 2 is almost a complete rewrite. You can't really view it as a newer version of the same application, but rather as a different application.

Hence the WONTFIX.
Comment 8 Malte S. Stretz 2008-10-21 18:46:58 UTC
This starts to get philosophical, but if a bug existed in v1 and doesn't exist in v2 anymore, isn't it FIXED then?

And is it really so hard to check with a small bug like this one if it is fixed or maybe survived the rewrite because maybe its in the Xine backend or some part of the logic which survived the rewrite?  I've seen bugs surviving "complete rewrites" before, just because the logic which led to the bug was kept.

Anyway, glad that it is fixed (it really is, isn't it?), I would have checked anyway if all my old KDE bugs are still around once I upgraded to KDE 4 (which I won't do until Amarok 2 is stable ;~)