[kde] [Bug 498722] New: Cannot set event location
bugzilla_noreply at kde.org
bugzilla_noreply at kde.org
Thu Jan 16 06:19:49 GMT 2025
https://bugs.kde.org/show_bug.cgi?id=498722
Bug ID: 498722
Summary: Cannot set event location
Classification: I don't know
Product: kde
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: madonuko at outlook.com
Target Milestone: ---
Application: merkuro-calendar (24.12.1)
ApplicationNotResponding [ANR]: false
Qt Version: 6.8.1
Frameworks Version: 6.9.0
Operating System: Linux 6.12.7-200.fc41.x86_64 x86_64
Windowing System: Wayland
Distribution: Ultramarine Linux 41 (Plasma Edition)
DrKonqi: 6.2.5 [CoredumpBackend]
-- Information about the crash:
When inputting text inside the location field, the application crashes
instantly
The crash can be reproduced every time.
-- Backtrace (Reduced):
#5 QScopedPointer<QObjectData, QScopedPointerDeleter<QObjectData> >::get
(this=0x8) at
/usr/src/debug/qt6-qtbase-6.8.1-7.fc41.x86_64/src/corelib/tools/qscopedpointer.h:110
[...]
#8 QObject::deleteLater (this=0x0) at
/usr/src/debug/qt6-qtbase-6.8.1-7.fc41.x86_64/src/corelib/kernel/qobject.cpp:2453
#9 0x00007f7e3bcc9b48 in QDeclarativeGeocodeModel::abortRequest
(this=this at entry=0x5605517ae410) at
/usr/src/debug/qt6-qtlocation-6.8.1-2.fc41.x86_64/src/location/declarativemaps/qdeclarativegeocodemodel.cpp:181
#10 0x00007f7e3bccadfd in QDeclarativeGeocodeModel::update
(this=0x5605517ae410) at
/usr/src/debug/qt6-qtlocation-6.8.1-2.fc41.x86_64/src/location/declarativemaps/qdeclarativegeocodemodel.cpp:138
#11 QDeclarativeGeocodeModel::update (this=0x5605517ae410) at
/usr/src/debug/qt6-qtlocation-6.8.1-2.fc41.x86_64/src/location/declarativemaps/qdeclarativegeocodemodel.cpp:114
Reported using DrKonqi
This report was filed against 'kde' because the product 'merkuro-calendar'
could not be located in Bugzilla. Add it to drkonqi's mappings file!
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list