Bug 114622 - adding song to playlist always doubles
Summary: adding song to playlist always doubles
Status: RESOLVED DUPLICATE of bug 111579
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 1.3.3
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
: 114623 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-10-18 17:30 UTC by Christian Parpart
Modified: 2006-06-11 12:32 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Parpart 2005-10-18 17:30:57 UTC
Version:           1.3.3 (using KDE 3.4.3, Gentoo)
Compiler:          gcc version 3.4.4 (Gentoo 3.4.4, ssp-3.4.4-1.0, pie-8.7.8)
OS:                Linux (x86_64) release 2.6.13-hardened

when DnDing a song (from currently being played playlist) to a custom playlist on the left side (which is being folded), the song to be added their exists twice in there then. (oh my, bad english today :p)

However, they do exist twice (instead of just once).

Although -sometimes- I see just the pathname when doing DnD/moves instead of their tag name.
Comment 1 Mark Kretschmann 2005-10-18 17:48:01 UTC
*** Bug 114623 has been marked as a duplicate of this bug. ***
Comment 2 Isaiah Damron 2005-12-01 20:15:15 UTC
To clarify, is this the problem?: When 'Playlists' is selected on the sidebar, and you drag a track from the right side to the sidebar, and drop it on a custom playlist, the track is added to that playlist twice?

If that's the case, then I'm unable to recreate this problem with either SVN or 1.3.6(gentoo).  It may've been fixed since 1.3.3, though I don't see it in the changelogs.  Could you upgrade to the most recent version and see if the problem still occurs?
Comment 3 Isaiah Damron 2005-12-01 21:27:52 UTC
Is this the same as bug 111579?
Comment 4 Isaiah Damron 2005-12-05 21:16:20 UTC
Unless the user responds and says otherwise, I'm assuming this is the same as bug 111579, which is fixed in the latest SVN.

*** This bug has been marked as a duplicate of 111579 ***