Summary: | Amarok crashes on scan on external harddrive | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Moritz Moroder <moritz.moroder> |
Component: | Podcast | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | bart.cerneels, ichbinanon |
Priority: | NOR | ||
Version: | 2.3.1 | ||
Target Milestone: | 2.3.2 | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | New crash information added by DrKonqi |
Description
Moritz Moroder
2010-08-14 12:44:23 UTC
*** This bug has been marked as a duplicate of bug 237000 *** Created attachment 51485 [details]
New crash information added by DrKonqi
amarok (2.3.1) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0
- What I was doing when the application crashed:
Scanning from external USB HD. Also, while playing...
-- Backtrace (Reduced):
#7 0x02ba1b39 in KSharedPtr (this=0xbfebb004, o=...) at /usr/include/ksharedptr.h:84
#8 0x02b9e2b5 in Podcasts::UmsPodcastProvider::playlists (this=0x8c14518) at /home/anupam/deb-src/amarok/amarok-2.3.1/src/core-impl/collections/umscollection/podcasts/UmsPodcastProvider.cpp:168
#9 0x00ed4b2f in PlaylistBrowserNS::MetaPlaylistModel::data (this=0x9097390, index=..., role=14) at /home/anupam/deb-src/amarok/amarok-2.3.1/src/browsers/playlistbrowser/MetaPlaylistModel.cpp:159
#10 0x00efa61c in PlaylistBrowserNS::PodcastModel::data (this=0x9097390, idx=..., role=14) at /home/anupam/deb-src/amarok/amarok-2.3.1/src/browsers/playlistbrowser/PodcastModel.cpp:279
#12 0x00edc206 in QtGroupingProxy::belongsTo (this=0x90acfb8, idx=...) at /home/anupam/deb-src/amarok/amarok-2.3.1/src/browsers/playlistbrowser/QtGroupingProxy.cpp:63
Please do not add backtraces to duplicate reports, and please read the origina bug 237000 before adding a comment, we need confirmations for either Amarok 2.3.2 beta or current git only. Sorry for nearly useless back trace. May be this information will make it more helpful: it is for latest nightly. :) (I will retry the current git repo again in a week since currently I am busy and will try to make a better report). |