amarok crashed with SIGSEGV in CollectionTreeItemModelBase::populateChildren()

[Beto29]

Binary package hint: amarok

Version of the package: 2:2.2.0-0ubuntu2
I'm using Kubuntu 9.10 64-bit on a Toshiba A305D SP6801 laptop. It crashed after stand-by

ProblemType: Crash
Architecture: amd64
Date: Wed Oct 21 10:55:48 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/amarok
Package: amarok 2:2.2.0-0ubuntu2
ProcCmdline: /usr/bin/amarok
ProcEnviron:
 PATH=(custom, user)
 LANG=es_UY.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x7feeec0e8886 <_ZN27CollectionTreeItemModelBase16populateChildrenERK5QListI10KSharedPtrIN4Meta8MetaBaseEEEP18CollectionTreeItemRK11QModelIndex+326>: mov (%rax),%r13
 PC (0x7feeec0e8886) ok
 source "(%rax)" (0xffffffff5a25a8c8) not located in a known VMA region (needed readable region)!
 destination "%r13" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: amarok
StacktraceTop:
 CollectionTreeItemModelBase::populateChildren(QList<KSharedPtr<Meta::MetaBase> > const&, CollectionTreeItem*, QModelIndex const&)
 CollectionTreeItemModelBase::handleNormalQueryResult(QueryMaker*, QList<KSharedPtr<Meta::MetaBase> > const&) ()
 CollectionTreeItemModelBase::newResultReady(QString const&, QList<KSharedPtr<Meta::MetaBase> >) () from /usr/lib/libamaroklib.so.1
 CollectionTreeItemModelBase::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libamaroklib.so.1
 QObject::event(QEvent*) ()
Title: amarok crashed with SIGSEGV in CollectionTreeItemModelBase::populateChildren()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video

[Jonathan Thomas (echidnaman)]

Is this crash reproducible? Unfortunately the backtrace that was autosubmitted was incomplete, so we may have to get a new one manually.

[Jonathan Thomas (echidnaman)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with Amarok itself, and not with our Amarok packages. But don't worry! This issue is being tracked by the KDE developers at: https://bugs.kde.org/show_bug.cgi?id=213991
Once fixed in Amarok, it will be included in Kubuntu once the Amarok version the fix is in in reaches Kubuntu.

Thanks!