https://bugs.kde.org/show_bug.cgi?id=458849
Bug ID: 458849
Summary: Segfault when clicking on other event while loading
location of event
Product: kalendar
Version: 22.08.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: claudio.cam...@gmail.com
Reporter: jasperbakk...@gmail.com
CC: c...@carlschwan.eu
Target Milestone: ---
SUMMARY
After clicking on an event that includes a location the location is loaded. But
after clicking on another event while kalendar is still loading the location it
segfaults. The KDE crash handler was unable to generate a backtrace so I tried
using gdb, I've never used it before so I hope the information is useful :).
The bug doesn't occur when maps are turned off. Is there any other information
I could provide that could be useful?
STEPS TO REPRODUCE
1. Create an event with location data and have map viewing enabled
2. Click on the event
3. While the location is still being loaded (you have to be pretty quick) click
on another event
OBSERVED RESULT
Kalendar segfaults
EXPECTED RESULT
The other event should be displayed without kalendar crashing
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5
Kernel Version: 5.19.7-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-10300H CPU @ 2.50GHz
Memory: 7,6 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
ADDITIONAL INFORMATION
Backtrace:
(gdb) bt
#0 0x00007f6d106a14dc in ?? () from /usr/lib/libc.so.6
#1 0x00007f6d10651998 in raise () from /usr/lib/libc.so.6
#2 0x00007f6d0ea40868 in KCrash::defaultCrashHandler(int) () from
/usr/lib/libKF5Crash.so.5
#3 <signal handler called>
#4 0x00007f6d00b0205e in QDeclarativeGeocodeModel::~QDeclarativeGeocodeModel()
() from /usr/lib/libQt5Location.so.5
#5 0x00007f6d00ca694b in ?? () from
/usr/lib/qt/qml/QtLocation/libdeclarative_location.so
#6 0x00007f6d0eeb42e5 in QObjectPrivate::deleteChildren() () from
/usr/lib/libQt5Core.so.5
#7 0x00007f6d0eeb4a79 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#8 0x00007f6d00ca6a2b in ?? () from
/usr/lib/qt/qml/QtLocation/libdeclarative_location.so
#9 0x00007f6d0eeb42e5 in QObjectPrivate::deleteChildren() () from
/usr/lib/libQt5Core.so.5
#10 0x00007f6d0eeb4a79 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#11 0x00007f6d00ca6beb in ?? () from
/usr/lib/qt/qml/QtLocation/libdeclarative_location.so
#12 0x00007f6d0eeb111a in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#13 0x00007f6d0fb78b3c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#14 0x00007f6d0ee8d978 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#15 0x00007f6d0ee8e483 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#16 0x00007f6d0eed4478 in ?? () from /usr/lib/libQt5Core.so.5
#17 0x00007f6d0cfe0b2b in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#18 0x00007f6d0d036e79 in ?? () from /usr/lib/libglib-2.0.so.0
#19 0x00007f6d0cfde252 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#20 0x00007f6d0eed825c in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQt5Core.so.5
#21 0x00007f6d0ee8611c in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/libQt5Core.so.5
#22 0x00007f6d0ee90c49 in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#23 0x00005629d4c41a9a in ?? ()
#24 0x00007f6d1063c2d0 in ?? () from /usr/lib/libc.so.6
#25 0x00007f6d1063c38a in __libc_start_main () from /usr/lib/libc.so.6
#26 0x00005629d4c42a45 in ?? ()
--
You are receiving this mail because:
You are watching all bug changes.
