Summary: | Collection entries are corrupted | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | msched |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | basura, mitchell |
Priority: | NOR | ||
Version: | 2.1.1 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
msched
2009-07-11 02:03:10 UTC
i think this is a duplicate of https://bugs.kde.org/199388 Seems to correspond to the second problem I described above, yes (but doesn't account for the completely missing entries I described in the first problem). (In reply to comment #2) > Seems to correspond to the second problem I described above, yes (but doesn't > account for the completely missing entries I described in the first problem). Well, you actually shouldn't submit two different items in a bug report. Marking this as a duplicate. BTW; both problems are well known and there already are bug reports available for both of it. Please check the existing reports. *** This bug has been marked as a duplicate of bug 199388 *** It wasn't clear to me if these were two different problems, especially since #2 usually appears only after trying to get rid of #1. I did spend some time looking for similar bug reports, but couldn't find any (the fact that the already rather confusing bugs.kde.org wizard kept timing out didn't help). I believe this to be a duplicate of bug 178973. It should be fixed in current SVN, which I encourage you to try so that if it's not we don't release 2.2 with such an issue. Please note that that bug deals with *database* corruption. There are still some issues with the collection browser showing things incorrectly. A good metric is, if things don't look right, and you close Amarok and restart it and things look right again, then it's not related to that bug. *** This bug has been marked as a duplicate of bug 178973 *** |