Bug 495362

Summary: Amarok crashes after the use of the local search
Product: [Applications] amarok Reporter: Martin Seidel <web.mseidel>
Component: generalAssignee: Amarok Bugs <amarok-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash CC: tuomas
Priority: NOR Keywords: drkonqi
Version First Reported In: 3.1.1   
Target Milestone: kf5   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi

Description Martin Seidel 2024-10-25 20:06:10 UTC
Application: amarok (3.1.1)

Qt Version: 5.15.13
Frameworks Version: 5.115.0
Operating System: Linux 6.11.4-amd64 x86_64
Windowing System: Wayland
Distribution: Debian GNU/Linux trixie/sid
DrKonqi: 5.27.11 [CoredumpBackend]

-- Information about the crash:
I typed in a title and hit Enter since it was only one result.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#5  0x00007fcc5c21f8ba in Collections::SqlQueryMaker::abortQuery() () from /lib/x86_64-linux-gnu/libamarok-sqlcollection.so.1
#6  0x00007fcc5c21f902 in Collections::SqlQueryMaker::~SqlQueryMaker() () from /lib/x86_64-linux-gnu/libamarok-sqlcollection.so.1
#7  0x00007fcc5c21fe0d in Collections::SqlQueryMaker::~SqlQueryMaker() () from /lib/x86_64-linux-gnu/libamarok-sqlcollection.so.1
#8  0x00007fcc7890bd09 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007fcc79563092 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5


Reported using DrKonqi
Comment 1 Martin Seidel 2024-10-25 20:06:11 UTC
Created attachment 175240 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Tuomas Nurmi 2024-10-25 21:19:05 UTC
Thank you for the report! Unfortunately, doesn't seem to be directly reproducible with the given steps. Seems like a duplicate of https://bugs.kde.org/show_bug.cgi?id=492406 , so marking it as such. (A possible fix was introduced to git a couple of days ago, but I don't have data yet if the fix works or not.)

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