Summary: | Amarok crashed when attempting to rename many mediafiles of different types [@ CollectionLocation::slotFinishRemove] | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Jere Samuli Perttula <j.s.perttula> |
Component: | Collections/Local | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | 123kash, dbram32, doko-steve, kde.org, matej, ralf-engels, spam_betasieben, trommelpeter, vvasaitis |
Priority: | NOR | Keywords: | release_blocker |
Version: | 2.3.2 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 2.4 | |
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Jere Samuli Perttula
2010-05-02 14:56:58 UTC
Is this still a problem in 2.3.1 beta 1? *** Bug 237809 has been marked as a duplicate of this bug. *** *** Bug 246392 has been marked as a duplicate of this bug. *** Can somebody reproduce this with Amarok 2.3.1 or later? *** Bug 249025 has been marked as a duplicate of this bug. *** Bumping version based on duplicate. *** Bug 240145 has been marked as a duplicate of this bug. *** Created attachment 55472 [details]
New crash information added by DrKonqi
amarok (2.3.2) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0
- What I was doing when the application crashed:
I was renaming many files with the "organize files" dialog. Some of them could not be removed:
The window title is "Unable to be removed tracks - Amarok".
The error message is: "There was a problem and 96 tracks could not be removed. Make sure the directory is writeable."
The error message dialog also shows a list of the files which could not be removed.
-- Backtrace (Reduced):
#6 deref (this=0x2e50ec0) at /usr/include/qt4/QtCore/qatomic_x86_64.h:133
#7 operator= (this=0x2e50ec0) at /usr/include/qt4/QtCore/qmap.h:430
#8 clear (this=0x2e50ec0) at /usr/include/qt4/QtCore/qmap.h:442
#9 Collections::CollectionLocation::slotFinishRemove (this=0x2e50ec0) at ../../../src/core/collections/CollectionLocation.cpp:409
#10 0x00007f2bb5cf152f in Collections::CollectionLocation::qt_metacall (this=0x2e50ec0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffcbf1bc90) at ./CollectionLocation.moc:135
Does this bug still persist in current git? Could some one try to reproduce It? I couldn't reproduce it. Closing then. *** Bug 266121 has been marked as a duplicate of this bug. *** |