| Summary: | moving a track out of collection and then into, it can not be found again until restart | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Hohyeis <hohyeis> |
| Component: | Collection Browser | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | bart.cerneels, ralf-engels |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | 2.6 | ||
| Platform: | unspecified | ||
| OS: | All | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Hohyeis
2012-05-08 15:05:52 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 *** Could you please specify why you think this is not a duplicate? Else it is pretty pointless to change that. Still waiting for your feedback, please explain. 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. 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 *** Please don't make smart-ass retorts without knowing multiple bug trackers as well as I do. (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. |