Bug 503847

Summary: Merkuro crashes when writing in the location field
Product: [Applications] Merkuro Reporter: Riccardo Robecchi <sephiroth_pk>
Component: generalAssignee: Claudio Cambra <claudio.cambra>
Status: RESOLVED DUPLICATE    
Severity: crash CC: aavin.fernando, carl
Priority: NOR Keywords: drkonqi
Version First Reported In: 25.04.0   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report: https://crash-reports.kde.org/organizations/kde/issues/174038/events/a17e8b75579f432c9a9ba9544cffca48/
Attachments: New crash information added by DrKonqi

Description Riccardo Robecchi 2025-05-06 15:11:09 UTC 
Application: merkuro-calendar (25.04.0)

ApplicationNotResponding [ANR]: false
Qt Version: 6.9.0
Frameworks Version: 6.13.0
Operating System: Linux 6.14.1-x64v3-xanmod1 x86_64
Windowing System: X11
Distribution: KDE neon 6.3
DrKonqi: 6.3.4 [CoredumpBackend]

-- Information about the crash:
Every time you create or edit an event and write in the location field, Merkuro crashes. This is 100% reproducible.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#6  QScopedPointer<QObjectData, QScopedPointerDeleter<QObjectData> >::get (this=0x8, this=<optimized out>) at /usr/src/qt6-base-6.9.0-0zneon+24.04+noble+release+build112/src/corelib/tools/qscopedpointer.h:110
[...]
#9  QObject::deleteLater (this=0x0) at /usr/src/qt6-base-6.9.0-0zneon+24.04+noble+release+build112/src/corelib/kernel/qobject.cpp:2465
#10 0x00007fa1d87bccf8 in QDeclarativeGeocodeModel::abortRequest() () at /lib/x86_64-linux-gnu/libQt6Location.so.6
#11 0x00007fa1d87bd29d in QDeclarativeGeocodeModel::update() () at /lib/x86_64-linux-gnu/libQt6Location.so.6
#12 0x00007fa1d87d5251 in QDeclarativeGeocodeModel::qt_metacall(QMetaObject::Call, int, void**) () at /lib/x86_64-linux-gnu/libQt6Location.so.6


Reported using DrKonqi
Comment 1 Riccardo Robecchi 2025-05-06 15:11:10 UTC 
Created attachment 180997 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Aavin 2025-05-24 16:18:25 UTC 

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