Bug 298328 - Crash on Kontact Startup
Summary: Crash on Kontact Startup
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.8.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 296353 298854 302939 302970 303233 303290 304391 306003 310695 313028 313365 315612 320449 322264 323845 324131 327687 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-04-17 23:28 UTC by Scott Kitterman
Modified: 2018-02-01 09:44 UTC (History)
17 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (8.39 KB, text/plain)
2012-05-09 15:09 UTC, Scott Kitterman
Details
New crash information added by DrKonqi (6.40 KB, text/plain)
2012-11-29 20:47 UTC, Kai Krakow
Details
New crash information added by DrKonqi (7.20 KB, text/plain)
2014-09-17 14:48 UTC, Raúl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Kitterman 2012-04-17 23:28:00 UTC
Application: kontact (4.8.2)
KDE Platform Version: 4.8.2 (4.8.2)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-23-generic-pae i686
Distribution: Ubuntu precise (development branch)

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

Crash was immediately on startup before I even saw the U/I start to draw.  Akonadi was in a stopped state when Kontact was launched.  The backtrace seems similar, but not identical to the backtrace in the suggested dupe.  I'm not enough of an expert at reading backtraces to know if it's a dupe or not.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb210f980 (LWP 2789))]

Thread 4 (Thread 0xafaf9b40 (LWP 2790)):
#0  0xb76e4424 in __kernel_vsyscall ()
#1  0xb391896b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0
#2  0xb601d3dc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0xb579b263 in WTF::TCMalloc_PageHeap::scavengerThread (this=0xb5ec7940) at wtf/FastMalloc.cpp:2495
#4  0xb579b37f in WTF::TCMalloc_PageHeap::runScavengerThread (context=0xb5ec7940) at wtf/FastMalloc.cpp:1618
#5  0xb3914d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#6  0xb600face in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 3 (Thread 0xaf1d8b40 (LWP 2791)):
#0  0xb3666dcd in clock_gettime () from /lib/i386-linux-gnu/librt.so.1
#1  0xb6276315 in do_gettime (frac=0xaf1d8040, sec=0xaf1d8038) at tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0xb6360226 in QTimerInfoList::updateCurrentTime (this=0xae802074) at kernel/qeventdispatcher_unix.cpp:343
#4  0xb635fe16 in timerSourceCheckHelper (src=0xae802040) at kernel/qeventdispatcher_glib.cpp:150
#5  timerSourceCheckHelper (src=0xae802040) at kernel/qeventdispatcher_glib.cpp:144
#6  0xb3841a6b in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0xb3842002 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#8  0xb38421c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#9  0xb635f8e7 in QEventDispatcherGlib::processEvents (this=0xae800468, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#10 0xb632b50d in QEventLoop::processEvents (this=0xaf1d8270, flags=...) at kernel/qeventloop.cpp:149
#11 0xb632b7a9 in QEventLoop::exec (this=0xaf1d8270, flags=...) at kernel/qeventloop.cpp:204
#12 0xb621494c in QThread::exec (this=0x95f1190) at thread/qthread.cpp:501
#13 0xb6214a3b in QThread::run (this=0x95f1190) at thread/qthread.cpp:568
#14 0xb6217de0 in QThreadPrivate::start (arg=0x95f1190) at thread/qthread_unix.cpp:298
#15 0xb3914d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#16 0xb600face in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 2 (Thread 0xac565b40 (LWP 2811)):
#0  0xb3666dcd in clock_gettime () from /lib/i386-linux-gnu/librt.so.1
#1  0xb6276315 in do_gettime (frac=0xac564fb0, sec=0xac564fa8) at tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0xb6360226 in QTimerInfoList::updateCurrentTime (this=0xabc02074) at kernel/qeventdispatcher_unix.cpp:343
#4  0xb636057a in QTimerInfoList::timerWait (this=0xabc02074, tm=...) at kernel/qeventdispatcher_unix.cpp:450
#5  0xb635ee23 in timerSourcePrepareHelper (src=<optimized out>, timeout=0xac5650bc) at kernel/qeventdispatcher_glib.cpp:136
#6  0xb635eebd in timerSourcePrepare (source=0xabc02040, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#7  0xb3841762 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#8  0xb3841f6f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#9  0xb38421c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0xb635f8e7 in QEventDispatcherGlib::processEvents (this=0xabc00468, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#11 0xb632b50d in QEventLoop::processEvents (this=0xac565240, flags=...) at kernel/qeventloop.cpp:149
#12 0xb632b7a9 in QEventLoop::exec (this=0xac565240, flags=...) at kernel/qeventloop.cpp:204
#13 0xb621494c in QThread::exec (this=0x9a73f30) at thread/qthread.cpp:501
#14 0xb6308b5d in QInotifyFileSystemWatcherEngine::run (this=0x9a73f30) at io/qfilesystemwatcher_inotify.cpp:248
#15 0xb6217de0 in QThreadPrivate::start (arg=0x9a73f30) at thread/qthread_unix.cpp:298
#16 0xb3914d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#17 0xb600face in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb210f980 (LWP 2789)):
[KCrash Handler]
#7  0xb767bb8b in QString (other=..., this=0xbfc43f64) at /usr/include/qt4/QtCore/qstring.h:725
#8  KontactInterface::Plugin::identifier (this=0x97ffc70) at ../../kontactinterface/plugin.cpp:101
#9  0xb76abee0 in activateInitialPluginModule (this=0x95d9580) at ../../../kontact/src/mainwindow.cpp:320
#10 Kontact::MainWindow::activateInitialPluginModule (this=0x95d9580) at ../../../kontact/src/mainwindow.cpp:315
#11 0xb76abfd5 in Kontact::MainWindow::setInitialActivePluginModule (this=0x95d9580, module=...) at ../../../kontact/src/mainwindow.cpp:297
#12 0x0804b768 in KontactApp::newInstance (this=0xbfc44c14) at ../../../kontact/src/main.cpp:147
#13 0xb741fc67 in KUniqueApplicationAdaptor::newInstance (this=0x96e7058, asn_id=..., args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:442
#14 0xb741fd18 in qt_static_metacall (_a=0xbfc441fc, _id=0, _o=0x96e7058, _c=<optimized out>) at ./kuniqueapplication_p.moc:58
#15 KUniqueApplicationAdaptor::qt_static_metacall (_o=0x96e7058, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfc441fc) at ./kuniqueapplication_p.moc:52
#16 0xb741fe8c in KUniqueApplicationAdaptor::qt_metacall (this=0x96e7058, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0xbfc441fc) at ./kuniqueapplication_p.moc:102
#17 0xb4158a38 in QDBusConnectionPrivate::deliverCall (this=0x95d9800, object=0x96e7058, msg=..., metaTypes=..., slotIdx=-1077657756) at qdbusintegrator.cpp:947
#18 0xb4159c80 in QDBusConnectionPrivate::activateCall (this=0x95d9800, object=0x96e7058, flags=337, msg=...) at qdbusintegrator.cpp:857
#19 0xb415a44b in QDBusConnectionPrivate::activateObject (this=0x95d9800, node=..., msg=..., pathStartPos=-1077656752) at qdbusintegrator.cpp:1443
#20 0xb415a7e8 in QDBusActivateObjectEvent::placeMetaCall (this=0x131d5520) at qdbusintegrator.cpp:1537
#21 0xb6347c7b in QObject::event (this=0xbfc44c14, e=0x131d5520) at kernel/qobject.cpp:1195
#22 0xb632cf8a in QCoreApplication::event (this=0xbfc44c14, e=0x131d5520) at kernel/qcoreapplication.cpp:1688
#23 0xb68995ad in QApplication::event (this=0xbfc44c14, e=0x131d5520) at kernel/qapplication.cpp:2541
#24 0xb6894ed4 in notify_helper (e=0x131d5520, receiver=0xbfc44c14, this=0x95e8cf0) at kernel/qapplication.cpp:4559
#25 QApplicationPrivate::notify_helper (this=0x95e8cf0, receiver=0xbfc44c14, e=0x131d5520) at kernel/qapplication.cpp:4531
#26 0xb689a30d in QApplication::notify (this=0x131d5520, receiver=0xbfc44c14, e=0x131d5520) at kernel/qapplication.cpp:4288
#27 0xb7419b21 in KApplication::notify (this=0xbfc44c14, receiver=0xbfc44c14, event=0x131d5520) at ../../kdeui/kernel/kapplication.cpp:311
#28 0xb632c97e in QCoreApplication::notifyInternal (this=0xbfc44c14, receiver=0xbfc44c14, event=0x131d5520) at kernel/qcoreapplication.cpp:876
#29 0xb6330ad8 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#30 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x95bfab8) at kernel/qcoreapplication.cpp:1500
#31 0xb6330e0c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1393
#32 0xb635f494 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#33 postEventSourceDispatch (s=0x95eba38) at kernel/qeventdispatcher_glib.cpp:279
#34 0xb3841cda in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#35 0xb38420e5 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#36 0xb38421c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#37 0xb635f887 in QEventDispatcherGlib::processEvents (this=0x95c0800, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#38 0xb694daaa in QGuiEventDispatcherGlib::processEvents (this=0x95c0800, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#39 0xb632b50d in QEventLoop::processEvents (this=0xbfc44b74, flags=...) at kernel/qeventloop.cpp:149
#40 0xb632b7a9 in QEventLoop::exec (this=0xbfc44b74, flags=...) at kernel/qeventloop.cpp:204
#41 0xb6330eba in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#42 0xb6892a74 in QApplication::exec () at kernel/qapplication.cpp:3820
#43 0x0804ac91 in main (argc=<error reading variable: Cannot access memory at address 0x8>, argv=<error reading variable: Cannot access memory at address 0xc>) at ../../../kontact/src/main.cpp:218

This bug may be a duplicate of or related to bug 193514.

Possible duplicates by query: bug 297233, bug 296199, bug 287446, bug 284289, bug 281644.

Reported using DrKonqi
Comment 1 Christophe Marin 2012-04-18 22:37:14 UTC
Is the crash reproducible if you stop akonadi then start kontact ?

if yes, did you configure kontact to start on a particular module ?
Comment 2 Scott Kitterman 2012-04-18 22:40:25 UTC
It has happened a few times.  It was not reliably reproducable, but IIRC it did happen with akonadi stopped.  At the time, Kontact was starting in Kmail.
Comment 3 Christophe Marin 2012-05-01 15:42:39 UTC
*** Bug 298854 has been marked as a duplicate of this bug. ***
Comment 4 Scott Kitterman 2012-05-09 15:09:00 UTC
Created attachment 70978 [details]
New crash information added by DrKonqi

kontact (4.8.2) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

- What I was doing when the application crashed:

Kontact crashed on startup.

- Unusual behavior I noticed:

Akonadi was not running when I started Kontact (I'd stopped it manually).  I don't believe I've seen this when Akonadi was running before Kontact.

-- Backtrace (Reduced):
#7  0xb76b0b8b in QString (other=..., this=0xbfa32054) at /usr/include/qt4/QtCore/qstring.h:725
#8  KontactInterface::Plugin::identifier (this=0x986d2f8) at ../../kontactinterface/plugin.cpp:101
#9  0xb76e0ee0 in activateInitialPluginModule (this=0x9584fc0) at ../../../kontact/src/mainwindow.cpp:320
#10 Kontact::MainWindow::activateInitialPluginModule (this=0x9584fc0) at ../../../kontact/src/mainwindow.cpp:315
#11 0xb76e0fd5 in Kontact::MainWindow::setInitialActivePluginModule (this=0x9584fc0, module=...) at ../../../kontact/src/mainwindow.cpp:297
Comment 5 Jekyll Wu 2012-07-03 08:49:00 UTC
*** Bug 302939 has been marked as a duplicate of this bug. ***
Comment 6 Jekyll Wu 2012-07-03 13:26:42 UTC
*** Bug 296353 has been marked as a duplicate of this bug. ***
Comment 7 Jekyll Wu 2012-07-03 16:16:32 UTC
*** Bug 302970 has been marked as a duplicate of this bug. ***
Comment 8 Jekyll Wu 2012-07-09 12:21:49 UTC
*** Bug 303233 has been marked as a duplicate of this bug. ***
Comment 9 Jekyll Wu 2012-07-10 11:04:11 UTC
*** Bug 303290 has been marked as a duplicate of this bug. ***
Comment 10 Jekyll Wu 2012-08-01 19:10:58 UTC
*** Bug 304391 has been marked as a duplicate of this bug. ***
Comment 11 Kai Krakow 2012-11-29 20:47:20 UTC
Created attachment 75537 [details]
New crash information added by DrKonqi

kontact (4.9.3) on KDE Platform 4.9.3 using Qt 4.8.2

- What I was doing when the application crashed:

Not sure if Akonadi was running (as the reporter wrote) but it often happens after first attempt of launching Kontact after KDE login.

-- Backtrace (Reduced):
#6  Kontact::MainWindow::activateInitialPluginModule (this=0xdb8a40) at /var/tmp/portage/kde-base/kontact-4.9.3/work/kontact-4.9.3/kontact/src/mainwindow.cpp:322
#7  0x00000000004035ba in KontactApp::newInstance (this=0x7fffa767f3c0) at /var/tmp/portage/kde-base/kontact-4.9.3/work/kontact-4.9.3/kontact/src/main.cpp:148
#8  0x00007f5566d8be52 in KUniqueApplicationAdaptor::newInstance (this=0xd4f2d0, asn_id=<optimized out>, args=...) at /var/tmp/portage/kde-base/kdelibs-4.9.3/work/kdelibs-4.9.3/kdeui/kernel/kuniqueapplication.cpp:442
#9  0x00007f5566d8bed4 in KUniqueApplicationAdaptor::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=0x7fffa767e3b0) at /var/tmp/portage/kde-base/kdelibs-4.9.3/work/kdelibs-4.9.3_build/kdeui/kuniqueapplication_p.moc:58
#10 0x00007f5566d8c00b in KUniqueApplicationAdaptor::qt_metacall (this=0xd4f2d0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fffa767e3b0) at /var/tmp/portage/kde-base/kdelibs-4.9.3/work/kdelibs-4.9.3_build/kdeui/kuniqueapplication_p.moc:102
Comment 12 Jekyll Wu 2013-02-28 17:09:44 UTC
*** Bug 315612 has been marked as a duplicate of this bug. ***
Comment 13 Jekyll Wu 2013-02-28 17:10:19 UTC
*** Bug 313028 has been marked as a duplicate of this bug. ***
Comment 14 Jekyll Wu 2013-02-28 17:11:16 UTC
*** Bug 306003 has been marked as a duplicate of this bug. ***
Comment 15 Jekyll Wu 2013-05-30 01:00:20 UTC
*** Bug 320449 has been marked as a duplicate of this bug. ***
Comment 16 Jekyll Wu 2013-08-21 19:22:58 UTC
*** Bug 322264 has been marked as a duplicate of this bug. ***
Comment 17 Jekyll Wu 2013-08-21 19:23:43 UTC
*** Bug 313365 has been marked as a duplicate of this bug. ***
Comment 18 Jekyll Wu 2013-08-21 19:24:05 UTC
*** Bug 323845 has been marked as a duplicate of this bug. ***
Comment 19 Jekyll Wu 2013-08-28 03:45:50 UTC
*** Bug 324131 has been marked as a duplicate of this bug. ***
Comment 20 Jekyll Wu 2013-11-16 15:51:56 UTC
*** Bug 327687 has been marked as a duplicate of this bug. ***
Comment 21 Jekyll Wu 2013-12-21 14:00:50 UTC
*** Bug 310695 has been marked as a duplicate of this bug. ***
Comment 22 Raúl 2014-09-17 14:48:08 UTC
Created attachment 88724 [details]
New crash information added by DrKonqi

kontact (4.14) on KDE Platform 4.14.0 using Qt 4.8.6

Bump on kontact 4.14.0 and Qt4 4.8.6+git64-g5dc8b2b (Debian sid).

-- Backtrace (Reduced):
#6  QString (other=..., this=this@entry=0x7fff02632ac0) at /usr/include/qt4/QtCore/qstring.h:725
#7  KontactInterface::Plugin::identifier (this=0xafd2590) at ../../kontactinterface/plugin.cpp:103
#8  0x00007f5643465648 in Kontact::MainWindow::activateInitialPluginModule (this=0x12ee8e0) at ../../../kontact/src/mainwindow.cpp:329
#9  0x0000000000403e7a in KontactApp::newInstance (this=0x7fff02633780) at ../../../kontact/src/main.cpp:148
#10 0x00007f564300c62a in KUniqueApplicationAdaptor::newInstance (this=0x1289650, asn_id=..., args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:442
Comment 23 Denis Kurz 2017-06-23 20:19:24 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 24 Denis Kurz 2018-02-01 09:44:45 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.