Bug 465602

Summary:	Search in audio library
Product:	[Applications] amarok	Reporter:	Andreas <andreas.privatadresse>
Component:	general	Assignee:	Amarok Bugs <amarok-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	tuomas
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	2.9.71
Target Milestone:	kf5
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	attachment-343691-0.html

Description Andreas 2023-02-11 22:46:35 UTC

Application: amarok (2.9.71)

Qt Version: 5.15.8
Frameworks Version: 5.102.0
Operating System: Linux 6.1.10-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.26.5 [KCrashBackend]

-- Information about the crash:
After entering a single letter to filter my local audio library (some 50k tracks), amarok crashed. This effect is reproducable. Since it occurs already for the first letter, it is not posssible do any filtering at all right now.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Amarok (amarok), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f4c4f44001e in CollectionTreeItem::row() const () from /lib64/libamaroklib.so.1
#5  0x00007f4c4f44e850 in CollectionTreeItemModelBase::itemIndex(CollectionTreeItem*) const () from /lib64/libamaroklib.so.1
#6  0x00007f4c4f443340 in CollectionTreeItemModelBase::parent(QModelIndex const&) const () from /lib64/libamaroklib.so.1
#7  0x00007f4c4dcb09b1 in ?? () from /lib64/libQt5Core.so.5
#8  0x00007f4c4dd1360c in ?? () from /lib64/libQt5Core.so.5
#9  0x00007f4c4dc7628c in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector<int> const&) () from /lib64/libQt5Core.so.5
#10 0x00007f4c4f450103 in CollectionTreeItemModelBase::tracksLoaded(AmarokSharedPointer<Meta::Album> const&, QModelIndex const&, QList<AmarokSharedPointer<Meta::Track> > const&) () from /lib64/libamaroklib.so.1
#11 0x00007f4c4dd07d00 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#12 0x00007f4c4e9a544e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#13 0x00007f4c4dcdc1e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#14 0x00007f4c4dcdf181 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5
#15 0x00007f4c4dd34413 in ?? () from /lib64/libQt5Core.so.5
#16 0x00007f4c4af1ba90 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#17 0x00007f4c4af1be48 in ?? () from /lib64/libglib-2.0.so.0
#18 0x00007f4c4af1bedc in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#19 0x00007f4c4dd33c16 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#20 0x00007f4c4dcdac5b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#21 0x00007f4c4dce2dc6 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#22 0x000055f0c7ed6f76 in ?? ()
#23 0x00007f4c4d42c5b0 in __libc_start_call_main () from /lib64/libc.so.6
#24 0x00007f4c4d42c679 in __libc_start_main_impl () from /lib64/libc.so.6
#25 0x000055f0c7ed7805 in ?? ()
[Inferior 1 (process 4584) detached]

The reporter indicates this bug may be a duplicate of or related to bug 444408.

Reported using DrKonqi

Comment 1 Tuomas Nurmi 2023-03-10 08:28:49 UTC

A fix for https://bugs.kde.org/show_bug.cgi?id=444408 has been in GIT since 7th Feb 2023, and I'd believe this is the same bug. The most readily available Amarok packages for openSUSE Tumbleweed seem to be
2.9.75git.20221114T02 in repository KDE:Extra and
2.9.75git.20230309T01 in repository KDE:Unstable:Extra

Can you confirm / check from package management (or check from About Amarok -> Build date) if the version you are using is an older build than 7th Feb 2023, and if so, try if the newer version in KDE:Unstable:Extra works for you?

Comment 2 Andreas 2023-03-12 19:21:07 UTC

Created attachment 157220 [details]
attachment-343691-0.html

Hi Tuomas

My version of amarok is the latest from OpenSuse Tumbleweed:
2.9.75git.20221114T020258~457db492b4-1.3
but the same error occurs. Maybe there is an issue with the size of the 
library which is almost 400GB and I guess some 70k tracks. I could not 
try the version from KDE:Unstable:Extra since I just arrived today. But 
I will try it soon.

Thanks and best regards
Andreas



Am 10.03.23 um 09:28 schrieb Tuomas Nurmi:
> https://bugs.kde.org/show_bug.cgi?id=465602
>
> Tuomas Nurmi<tuomas@norsumanageri.org>  changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |tuomas@norsumanageri.org
>
> --- Comment #1 from Tuomas Nurmi<tuomas@norsumanageri.org>  ---
> A fix forhttps://bugs.kde.org/show_bug.cgi?id=444408  has been in GIT since 7th
> Feb 2023, and I'd believe this is the same bug. The most readily available
> Amarok packages for openSUSE Tumbleweed seem to be
> 2.9.75git.20221114T02 in repository KDE:Extra and
> 2.9.75git.20230309T01 in repository KDE:Unstable:Extra
>
> Can you confirm / check from package management (or check from About Amarok ->
> Build date) if the version you are using is an older build than 7th Feb 2023,
> and if so, try if the newer version in KDE:Unstable:Extra works for you?
>

Comment 3 Tuomas Nurmi 2024-03-03 08:42:19 UTC

(In reply to Andreas from comment #2)
> Created attachment 157220 [details]
> attachment-343691-0.html
> 
> Hi Tuomas
> 
> My version of amarok is the latest from OpenSuse Tumbleweed:
> 2.9.75git.20221114T020258~457db492b4-1.3

Sorry for the very late reply, forgot this last year. But as I mentioned year ago, the 2.9.75git.20230309T01 version in repository KDE:Unstable:Extra had this fixed, being built from post-Feb2023 sources, while the version "2.9.75git.20221114T020258" was from November 2022 sources, and thus did not contain the fix.
However, I see that amarok version in opensuse repo-oss is 20230408 at the moment, so I assume this was fixed by updating packages mid-April last year. Please do notify me if this was not the case.

*** This bug has been marked as a duplicate of bug 444408 ***