Bug 299627 - moving a track out of collection and then into, it can not be found again until restart
Summary: moving a track out of collection and then into, it can not be found again unt...
Status: RESOLVED DUPLICATE of bug 172542
Alias: None
Product: amarok
Classification: Applications
Component: Collection Browser (show other bugs)
Version: unspecified
Platform: unspecified All
: NOR normal
Target Milestone: 2.6
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-08 15:05 UTC by Hohyeis
Modified: 2012-05-25 20:54 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Hohyeis 2012-05-08 15:05:52 UTC 
If a track is moved out of thecollection and then into it again, the track can not be found again until amarok is restarted. A "full rescan" will not add it to the collection.

Reproducible: Always
Comment 1 Myriam Schweingruber 2012-05-08 15:29:42 UTC 
What you describe is most likely a long standing bug in the Collection Browser, not updating the view.

*** This bug has been marked as a duplicate of bug 172542 ***
Comment 2 Myriam Schweingruber 2012-05-16 17:21:38 UTC 
Could you please specify why you think this is not a duplicate? Else it is pretty pointless to change that.
Comment 3 Myriam Schweingruber 2012-05-20 03:24:16 UTC 
Still waiting for your feedback, please explain.
Comment 4 Hohyeis 2012-05-20 10:02:39 UTC 
This is not the bug I wished to mark as not a duplicate. The change in "Status" marking was unintentional and happened due to the unusual behavior of the bug tracker in how it presents a different bug after you have submitted a change to a bug.

I don't know how to discern whether the error is in the collection or view of it. If you have a proposition on how I could check that, I may.
Comment 5 Myriam Schweingruber 2012-05-20 13:25:39 UTC 
Well, then please do not modify bugs before you really know what you are doing, this is just additional work for us.

*** This bug has been marked as a duplicate of bug 172542 ***
Comment 6 Hohyeis 2012-05-24 13:07:01 UTC 
Please don't make smart-ass retorts without knowing multiple bug trackers as well as I do.
Comment 7 Bart Cerneels 2012-05-25 20:54:40 UTC 
(In reply to comment #6)
> Please don't make smart-ass retorts without knowing multiple bug trackers as
> well as I do.

Please don't escalate then tensions. We understand the mistake you make. You can change bugzilla's default behavior to move down the list after changing a bug. I find it annoying as well.

Please be careful when editing bugs though. Myriam has a valid point that it's additional work (mainly for her as our top bug triager) that could be avoided.