| Summary: | amarok crashes while scanning newly ripped files [@ ScanResultProcessor::addTrack] | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Oliver Henshaw <oliver.henshaw> |
| Component: | Collections/Local | Assignee: | Amarok Bugs <amarok-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | mitchell, shweduke |
| Priority: | NOR | ||
| Version First Reported In: | 2.3.0 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Oliver Henshaw
2010-05-22 02:23:31 UTC
As best I can tell this is actually a Qt bug. The crash comes in QDir; this is a read-only object from Amarok's POV, so it's not likely something Amarok is doing that is causing this. I will try to figure out a test case to submit upstream to the Qt guys...in the meantime, I suggest if you hit this bug more to try ripping your tracks to a directory outside your collection, then to move them in afterwards :-| *** Bug 242604 has been marked as a duplicate of this bug. *** |