Bug 258162

Summary: Crash while leaving
Product: [Frameworks and Libraries] Akonadi Reporter: Gerhard Decher <gerdech>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: crash    
Priority: NOR    
Version: 4.4   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Gerhard Decher 2010-11-28 12:13:13 UTC
Application: kontact (4.4.2)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-26-generic i686
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
I started Kontact, switched thru the Modules and Noticed that the Akonadi for the Contacts-Module was not startet. After then switching off Kontact i got the Crash - Info! With a second Start of Kontact i saw everything working Okay!

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0x03061d1b in QWidgetPrivate::setEnabled_helper (this=0x99f19f0, enable=false) at kernel/qwidget.cpp:3119
#7  0x03062022 in QWidget::setEnabled (this=0x99ec198, enable=false) at kernel/qwidget.cpp:3065
#8  0x04533873 in KJotsComponent::DelayedInitialization (this=0x9725f10) at ../../kjots/kjotscomponent.cpp:435
#9  0x04512bdc in KJotsComponent::qt_metacall (this=0x9725f10, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfbf26cc) at moc_kjotscomponent.cpp:142
#10 0x01166c9a in QMetaObject::metacall (object=0x9725f10, cl=QMetaObject::ReadProperty, idx=33, argv=0xbfbf26cc) at kernel/qmetaobject.cpp:237
#11 0x011753d5 in QMetaObject::activate (sender=0x99e8750, m=0x1274188, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293
#12 0x0117cfe7 in QSingleShotTimer::timeout (this=0x99e8750) at .moc/release-shared/qtimer.moc:82
#13 0x0117d0fc in QSingleShotTimer::timerEvent (this=0x99e8750) at kernel/qtimer.cpp:308
#14 0x01172254 in QObject::event (this=0x99e8750, e=0x521) at kernel/qobject.cpp:1212
#15 0x030024dc in QApplicationPrivate::notify_helper (this=0x8b48ac8, receiver=0x99e8750, e=0xbfbf2c00) at kernel/qapplication.cpp:4300
#16 0x0300905e in QApplication::notify (this=0xbfbf3014, receiver=0x99e8750, e=0xbfbf2c00) at kernel/qapplication.cpp:3704
#17 0x007fdf2a in KApplication::notify (this=0xbfbf3014, receiver=0x99e8750, event=0xbfbf2c00) at ../../kdeui/kernel/kapplication.cpp:302
#18 0x01161a3b in QCoreApplication::notifyInternal (this=0xbfbf3014, receiver=0x99e8750, event=0xbfbf2c00) at kernel/qcoreapplication.cpp:704
#19 0x01190d66 in QCoreApplication::sendEvent (this=0x8b4dc34) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#20 QTimerInfoList::activateTimers (this=0x8b4dc34) at kernel/qeventdispatcher_unix.cpp:603
#21 0x0118d8e4 in timerSourceDispatch (source=0x8b4dc00) at kernel/qeventdispatcher_glib.cpp:184
#22 0x0206f5e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#23 0x020732d8 in ?? () from /lib/libglib-2.0.so.0
#24 0x020734b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#25 0x0118d5d5 in QEventDispatcherGlib::processEvents (this=0x8b28588, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#26 0x030c2135 in QGuiEventDispatcherGlib::processEvents (this=0x8b28588, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#27 0x01160059 in QEventLoop::processEvents (this=0x8d44d38, flags=) at kernel/qeventloop.cpp:149
#28 0x011604aa in QEventLoop::exec (this=0x8d44d38, flags=...) at kernel/qeventloop.cpp:201
#29 0x00b69b9b in Akonadi::Control::Private::exec (this=0x8d056f8) at ../../akonadi/control.cpp:137
#30 0x00b6a11e in Akonadi::Control::start () at ../../akonadi/control.cpp:206
#31 0x00b6a373 in Akonadi::Control::start (parent=0x0) at ../../akonadi/control.cpp:233
#32 0x0804b451 in main (argc=1, argv=0xbfbf3234) at ../../../kontact/src/main.cpp:204

Reported using DrKonqi
Comment 1 Denis Kurz 2016-09-24 20:38:53 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:22:04 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.