Bug 449295 - Kontact crashes
Summary: Kontact crashes
Status: REPORTED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-01-28 16:33 UTC by martin.strecker
Modified: 2022-01-28 17:48 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description martin.strecker 2022-01-28 16:33:42 UTC
Application: kontact (5.14.2 (20.04.2))

Qt Version: 5.12.7
Frameworks Version: 5.76.0
Operating System: Linux 5.3.18-150300.59.43-default x86_64
Windowing system: X11
Distribution: openSUSE Leap 15.3

-- Information about the crash:
- What I was doing when the application crashed:

The Kontact window was open when the crash occurred, but I did not interact with Kontact at the moment of the crash - I was writing a text in another window (Thunderbird). 

This error has occurred several times, and often the pattern is the same (crash while not interacting with Kontact), and the crash seems completely random and not related to what I do on the machine (no heavy use of CPU,  memory or network).

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#4  0x00007fee3bb04e1a in operator== (s1=..., s2=...) at tools/qstring.cpp:3402
#5  0x00007fedcd81329c in KCalendarCore::MemoryCalendar::Private::forIncidences<KCalendarCore::Incidence, QString>(QMultiHash<QString, QSharedPointer<KCalendarCore::Incidence> > const&, QString const&, std::function<void (KCalendarCore::Incidence::Ptr const&)>&&) const (op=..., key=..., incidences=..., this=<optimized out>) at /usr/src/debug/kcalendarcore-5.76.0-bp153.2.2.1.x86_64/src/memorycalendar.cpp:101
#6  KCalendarCore::MemoryCalendar::deleteIncidenceInstances (this=<optimized out>, incidence=...) at /usr/src/debug/kcalendarcore-5.76.0-bp153.2.2.1.x86_64/src/memorycalendar.cpp:243
#7  0x00007fedcd81775f in KCalendarCore::MemoryCalendar::deleteIncidence (this=0x55ab6359cbc0, incidence=...) at /usr/src/debug/kcalendarcore-5.76.0-bp153.2.2.1.x86_64/src/memorycalendar.cpp:231
#8  0x00007fedcdfcfc73 in CalendarSupport::EventArchiver::archiveIncidences (this=this@entry=0x7fff8cb7e130, calendar=..., changer=changer@entry=0x55ab60c3fb50, limitDate=..., widget=widget@entry=0x55ab60dd6d60, incidences=..., withGUI=<optimized out>) at /usr/src/debug/calendarsupport-20.04.2-bp153.2.2.1.x86_64/src/eventarchiver.cpp:235
#9  0x00007fedcdfd18a7 in CalendarSupport::EventArchiver::run (this=this@entry=0x7fff8cb7e130, calendar=..., changer=changer@entry=0x55ab60c3fb50, limitDate=..., widget=widget@entry=0x55ab60dd6d60, withGUI=withGUI@entry=false, errorIfNone=false) at /usr/src/debug/calendarsupport-20.04.2-bp153.2.2.1.x86_64/src/eventarchiver.cpp:154
#10 0x00007fedcdfd21f9 in CalendarSupport::EventArchiver::runAuto (this=this@entry=0x7fff8cb7e130, calendar=..., changer=changer@entry=0x55ab60c3fb50, widget=widget@entry=0x55ab60dd6d60, withGUI=withGUI@entry=false) at /usr/src/debug/calendarsupport-20.04.2-bp153.2.2.1.x86_64/src/eventarchiver.cpp:102
#11 0x00007feda56a374c in ActionManager::slotAutoArchive (this=0x55ab60c73630) at /usr/src/debug/korganizer-20.04.2-bp153.2.2.1.x86_64/src/actionmanager.cpp:1670
#12 0x00007fee3bc85fcf in QtPrivate::QSlotObjectBase::call (a=0x7fff8cb7e290, r=0x55ab60c73630, this=0x55ab60d92570) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394
#13 QMetaObject::activate (sender=sender@entry=0x55ab60db13c0, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff8cb7e290) at kernel/qobject.cpp:3784
#14 0x00007fee3bc865c7 in QMetaObject::activate (sender=sender@entry=0x55ab60db13c0, m=m@entry=0x7fee3c104d20 <QTimer::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff8cb7e290) at kernel/qobject.cpp:3657
#15 0x00007fee3bc92dd7 in QTimer::timeout (this=this@entry=0x55ab60db13c0, _t1=...) at .moc/moc_qtimer.cpp:204
#16 0x00007fee3bc93138 in QTimer::timerEvent (this=0x55ab60db13c0, e=<optimized out>) at kernel/qtimer.cpp:255
#17 0x00007fee3bc86a1b in QObject::event (this=0x55ab60db13c0, e=<optimized out>) at kernel/qobject.cpp:1283
#18 0x00007fee3cadbf9c in QApplicationPrivate::notify_helper (this=this@entry=0x55ab603ed460, receiver=receiver@entry=0x55ab60db13c0, e=e@entry=0x7fff8cb7e600) at kernel/qapplication.cpp:3701
#19 0x00007fee3cae35b0 in QApplication::notify (this=0x7fff8cb7e980, receiver=0x55ab60db13c0, e=0x7fff8cb7e600) at kernel/qapplication.cpp:3447
#20 0x00007fee3bc563a8 in QCoreApplication::notifyInternal2 (receiver=0x55ab60db13c0, event=0x7fff8cb7e600) at kernel/qcoreapplication.cpp:1088
#21 0x00007fee3bcb2899 in QTimerInfoList::activateTimers (this=0x55ab6042bcc0) at kernel/qtimerinfo_unix.cpp:643
#22 0x00007fee3bcb3099 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:182
#23 idleTimerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:229
#24 0x00007fee34b39694 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#25 0x00007fee34b39a30 in ?? () from /usr/lib64/libglib-2.0.so.0
#26 0x00007fee34b39abc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#27 0x00007fee3bcb342f in QEventDispatcherGlib::processEvents (this=0x55ab604facb0, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#28 0x00007fee3bc545fa in QEventLoop::exec (this=this@entry=0x7fff8cb7e850, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#29 0x00007fee3bc5d800 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1389
#30 0x000055ab5f05a785 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/kontact-20.04.2-bp153.2.2.1.x86_64/src/main.cpp:229
[Inferior 1 (process 11174) detached]

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

Possible duplicates by query: bug 443771, bug 440841, bug 425842, bug 422092, bug 419229.

Reported using DrKonqi