Bug 218151

Summary: Kontact starts twice then crashes
Product: [Applications] kontact Reporter: Ralph Holz <ralph-bugskde>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra, kon_chr2000-linux
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Ralph Holz 2009-12-10 19:53:55 UTC
Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-15-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
I am almost certain I only clicked kontact once to start. In any case, two instances were running. When trying to close one, the other instance crashed.

This seems to be a duplicate, as indicated.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0x062e2a61 in KMKernel::messageCountChanged (this=0x0) at ../../kmail/kmkernel.cpp:2435
#7  0x0615cc55 in KMail::FolderViewItem::updateCounts (this=0xa122e28) at ../../kmail/folderview.cpp:2893
#8  0x0615cfd8 in KMail::FolderView::updateCountsForChildren (this=0xa0ddc90, it=0xa0d6e48, tStart=...) at ../../kmail/folderview.cpp:865
#9  0x0615d06e in KMail::FolderView::slotUpdateCounts (this=0xa0ddc90) at ../../kmail/folderview.cpp:898
#10 0x0615da38 in KMail::FolderView::qt_metacall (this=0xa0ddc90, _c=QMetaObject::InvokeMetaMethod, _id=145, _a=0xbfdf0eac) at ./folderview.moc:211
#11 0x0616609a in KMail::FavoriteFolderView::qt_metacall (this=0xa0ddc90, _c=QMetaObject::InvokeMetaMethod, _id=145, _a=0xbfdf0eac) at ./favoritefolderview.moc:65
#12 0x00d1c263 in QMetaObject::activate (sender=0xa0e01c8, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#13 0x00d1cec2 in QMetaObject::activate (sender=0xa0e01c8, m=0xdf7904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#14 0x00d56667 in QTimer::timeout (this=0xa0e01c8) at .moc/release-shared/moc_qtimer.cpp:128
#15 0x00d219ae in QTimer::timerEvent (this=0xa0e01c8, e=0xbfdf1340) at kernel/qtimer.cpp:261
#16 0x00d163bf in QObject::event (this=0xa0e01c8, e=0xbfdf1340) at kernel/qobject.cpp:1075
#17 0x0110df54 in QApplicationPrivate::notify_helper (this=0x9205348, receiver=0xa0e01c8, e=0xbfdf1340) at kernel/qapplication.cpp:4056
#18 0x0111567c in QApplication::notify (this=0xbfdf16a4, receiver=0xa0e01c8, e=0xbfdf1340) at kernel/qapplication.cpp:3603
#19 0x00639bfa in KApplication::notify (this=0xbfdf16a4, receiver=0xa0e01c8, event=0xbfdf1340) at ../../kdeui/kernel/kapplication.cpp:302
#20 0x00d066cb in QCoreApplication::notifyInternal (this=0xbfdf16a4, receiver=0xa0e01c8, event=0xbfdf1340) at kernel/qcoreapplication.cpp:610
#21 0x00d337ce in QCoreApplication::sendEvent (this=0x91fc534) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#22 QTimerInfoList::activateTimers (this=0x91fc534) at kernel/qeventdispatcher_unix.cpp:572
#23 0x00d310e0 in timerSourceDispatch (source=0x91fc500) at kernel/qeventdispatcher_glib.cpp:165
#24 0x01da2e78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#25 0x01da6720 in ?? () from /lib/libglib-2.0.so.0
#26 0x01da6853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#27 0x00d3102c in QEventDispatcherGlib::processEvents (this=0x91db9f8, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#28 0x011aebe5 in QGuiEventDispatcherGlib::processEvents (this=0x91db9f8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#29 0x00d04c79 in QEventLoop::processEvents (this=0xbfdf1604, flags=) at kernel/qeventloop.cpp:149
#30 0x00d050ca in QEventLoop::exec (this=0xbfdf1604, flags=...) at kernel/qeventloop.cpp:201
#31 0x00d0753f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#32 0x0110ddd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#33 0x0804b4e6 in main (argc=3, argv=0xbfdf18c4) at ../../../kontact/src/main.cpp:218

This bug may be a duplicate of or related to bug 201193

Reported using DrKonqi
Comment 1 Dario Andres 2009-12-10 22:38:00 UTC
The root issue is being tracked at bug 185544. Thanks

*** This bug has been marked as a duplicate of bug 185544 ***
Comment 2 Dario Andres 2010-01-18 21:58:02 UTC
*** Bug 223308 has been marked as a duplicate of this bug. ***