Summary: | Kontact crashes at start (Kontact::Plugin::part, K*UniqueAppHandler::newInstance, Kontact::UniqueAppHandler::newInstance) | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Michał Gawroński <dinth> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | 20120808_bugs.kde.org, 4ernov, achim_schaefer, afg2006, alinm.elena, andreiamenta, andresbajotierra, apfelmausmail, b.feildel, bernhard, bittajam, bres.sidhe, bugs.kde, bugs, bugzilla.kde, camilleinfo, cannewilson, christophe, depuxster, dhillonv10, doonze, dotby, dtrende, emaildericky, faure, felixrabeler, fgunni, fjperezor, fleog, floeschie, florian.reinhard, florian_bfr, freelancer317, fzsemmo, giecrilj, gpetetin, hammett, hh.kde.crash, iferca, james, janiktomanek, jnigaglioni, jonay.santana, j_kolberg11, karaluh, kbogert, kdebugs, kilem86, kkraft, ludo.aelbrecht+kde, m.wege, maba.gp, markusk, mars-online, martinknocik, mats, MautzLogistics, maxmin88, michael, mobilejimbo, msp, nbruce236, nikusaf, openroot, orthodoxinfidel, p92, patrick_steinmueller, pierpaolo.franco, Pogo_Dick, puleri.solaris, rapsys, rasasi78, renota, richih-kde, rmills764, rohland.max, Ronny.Standtke, salvalemany, scunizi, sedo_5, sievert, StefanGER, steffenkoch81, sylvain.garsault, teo78, thoar.varenkamp, three3q, tom, tonny.van.bommel, ugubabba, umeboshi3, underline, uwe.helms, vaninvv, virusmiurasv, winter, wtan, yandy.ding |
Priority: | NOR | Keywords: | triaged |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
bt full from trunk Valgrind output during crashed open-attempt New crash information added by DrKonqi New crash information added by DrKonqi |
Description
Michał Gawroński
2009-05-27 07:02:44 UTC
*** Bug 194683 has been marked as a duplicate of this bug. *** *** Bug 196149 has been marked as a duplicate of this bug. *** i can confirm this (random) crash on 4.2.90 with qt 4.5.1. started korganizer from cli => crash. Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 Kontact::Plugin::part (this=0xa0617b0) at /build/buildd/kdepim-4.2.90/kontactinterfaces/plugin.cpp:186 #7 0xb19c726a in KOrganizerUniqueAppHandler::newInstance (this=0xa066fc0) at /build/buildd/kdepim-4.2.90/kontact/plugins/korganizer/korg_uniqueapp.cpp:35 #8 0xb7951f39 in Kontact::UniqueAppHandler::newInstance (this=0xa066fc0, asn_id=@0xa2d10f8, args=@0xa104630) at /build/buildd/kdepim-4.2.90/kontactinterfaces/uniqueapphandler.cpp:128 #9 0xb7951fc6 in Kontact::UniqueAppHandler::qt_metacall (this=0xa066fc0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfcda2f8) at /build/buildd/kdepim-4.2.90/obj-i486-linux-gnu/kontactinterfaces/uniqueapphandler.moc:73 #10 0xb5e36e2a in QDBusConnectionPrivate::deliverCall (this=0x9cf9060, object=0xa066fc0, msg=@0xb39c228, metaTypes=@0xbfcda3a8, slotIdx=4) at qdbusintegrator.cpp:891 #11 0xb5e38042 in QDBusConnectionPrivate::activateCall (this=0x9cf9060, object=0xa066fc0, flags=272, msg=@0xb39c228) at qdbusintegrator.cpp:796 #12 0xb5e385b1 in QDBusConnectionPrivate::activateObject (this=0x9cf9060, node=@0xb39c214, msg=@0xb39c228, pathStartPos=26) at qdbusintegrator.cpp:1375 #13 0xb5e38aaa in QDBusActivateObjectEvent::placeMetaCall (this=0xb39c1e8) at qdbusintegrator.cpp:1469 #14 0xb5d2f150 in QObject::event (this=0xa066fc0, e=0xb39c1e8) at kernel/qobject.cpp:1118 #15 0xb61dcbcc in QApplicationPrivate::notify_helper (this=0x9d01840, receiver=0xa066fc0, e=0xb39c1e8) at kernel/qapplication.cpp:4057 #16 0xb61e4ede in QApplication::notify (this=0xbfcdab78, receiver=0xa066fc0, e=0xb39c1e8) at kernel/qapplication.cpp:3604 #17 0xb6e00e8d in KApplication::notify (this=0xbfcdab78, receiver=0xa066fc0, event=0xb39c1e8) at /build/buildd/kde4libs-4.2.90/kdeui/kernel/kapplication.cpp:302 #18 0xb5d1e7ab in QCoreApplication::notifyInternal (this=0xbfcdab78, receiver=0xa066fc0, event=0xb39c1e8) at kernel/qcoreapplication.cpp:610 #19 0xb5d1f405 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9ce0c08) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #20 0xb5d1f5fd in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140 #21 0xb5d4a58f in postEventSourceDispatch (s=0x9d03ac0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #22 0xb4df3b88 in IA__g_main_context_dispatch (context=0x9d03a38) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:1814 #23 0xb4df70eb in g_main_context_iterate (context=0x9d03a38, block=1, dispatch=1, self=0x9d012f0) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2448 #24 0xb4df7268 in IA__g_main_context_iteration (context=0x9d03a38, may_block=1) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2511 #25 0xb5d4a1d8 in QEventDispatcherGlib::processEvents (this=0x9d13dd0, flags={i = -1077040568}) at kernel/qeventdispatcher_glib.cpp:324 #26 0xb627e765 in QGuiEventDispatcherGlib::processEvents (this=0x9d13dd0, flags={i = -1077040520}) at kernel/qguieventdispatcher_glib.cpp:202 #27 0xb5d1cdda in QEventLoop::processEvents (this=0xbfcdaaf0, flags={i = -1077040456}) at kernel/qeventloop.cpp:149 #28 0xb5d1d21a in QEventLoop::exec (this=0xbfcdaaf0, flags={i = -1077040392}) at kernel/qeventloop.cpp:200 #29 0xb5d1f6c9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #30 0xb61dca47 in QApplication::exec () at kernel/qapplication.cpp:3526 #31 0x0804bfef in main (argc=3, argv=0xbfcdae74) at /build/buildd/kdepim-4.2.90/kontact/src/main.cpp:218 *** Bug 198107 has been marked as a duplicate of this bug. *** ok, reproduced in trunk. Not sure yet of a reliable way to trigger it. What I did so far : - Launch kontact, - browse between the different modules (except one which was running alone), - File/Quit - Start KMail #5 0xb781e6ed in Kontact::Plugin::part (this=0x89906d0) at /home/krop/kde/src/KDE/kdepim/kontactinterfaces/plugin.cpp:186 No locals. #6 0xb142ecc3 in KMailUniqueAppHandler::newInstance (this=0x8990378) at /home/krop/kde/src/KDE/kdepim/kontact/plugins/kmail/kmail_plugin.cpp:208 __PRETTY_FUNCTION__ = "virtual int KMailUniqueAppHandler::newInstance()" kmail = {<QDBusAbstractInterface> = {<QObject> = {_vptr.QObject = 0xbfd26c58, d_ptr = 0x0}, }, } reply = {m_error = {code = 3086843892, msg = {d = 0xb698d440}, nm = {d = 0xb67a1d80}, unused = 0xb698d464}, m_data = 24} #7 0xb78207f7 in Kontact::UniqueAppHandler::newInstance (this=0x8990378, asn_id=@0x95a8d80, args=@0x97181f8) at /home/krop/kde/src/KDE/kdepim/kontactinterfaces/uniqueapphandler.cpp:128 ds = {_vptr.QDataStream = 0xb66a1e18, d = 0xbfd26e48, dev = 0x92f1d60, owndev = true, noswap = false, byteorder = QDataStream::BigEndian, ver = 11, q_status = QDataStream::Ok} #8 0xb78211cd in Kontact::UniqueAppHandler::qt_metacall (this=0x8990378, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfd26e6c) at /home/krop/kde/build/KDE/kdepim/kontactinterfaces/uniqueapphandler.moc:73 _r = 141524736 #9 0xb66c7873 in QDBusConnectionPrivate::deliverCall (this=0x86ee5d8, object=0x8990378, msg=@0x9538f18, metaTypes=@0xbfd26f28, slotIdx=4) at qdbusintegrator.cpp:891 context = {connection = {d = 0x86ee5d8}, message = @0x9538f18} old = 0x0 ptr = {o = 0x8990378} params = {a = 10, s = 3, ptr = 0xbfd26e6c, { array = "\310\330\302\b\200\215Z\t\370\201q\t\230nҿo\233\\\266\boҿXoҿ\270nҿH'j\266\0\0\0\0\252\0l\266P\343;\t", q_for_alignment_1 = 674006675287627976, q_for_alignment_2 = 1.3175680849713402e-263}} auxParameters = {{p = {d = 0xb66a43f4}, d = 0xb66a43f4}} i = 3 pCount = 2 outputArgs = {{p = {d = 0x9ba4da0}, d = 0x9ba4da0}} fail = true #10 0xb66c8832 in QDBusConnectionPrivate::activateCall (this=0x86ee5d8, object=0x8990378, flags=272, msg=@0x9538f18) at qdbusintegrator.cpp:796 mo = 0xb7826d3c memberName = {d = 0x9a65b80} slotData = {flags = 272, slotIdx = 4, metaTypes = {{p = {d = 0x95a79b0}, d = 0x95a79b0}}} slotCache = {hash = {<QHash<QString, QDBusSlotCache::Data>> = {{d = 0x9fcad80, e = 0x9fcad80}}, <No data fields>}} cacheKey = {d = 0x9598e48} signature = {d = 0x939ced8} cachePropertyName = "_qdbus_slotCache" #11 0xb66c8da1 in QDBusConnectionPrivate::activateObject (this=0x86ee5d8, node=@0x9538f04, msg=@0x9538f18, pathStartPos=21) at qdbusintegrator.cpp:1370 connector = 0xb6714ff4 #12 0xb66c929a in QDBusActivateObjectEvent::placeMetaCall (this=0x9538ed8) at qdbusintegrator.cpp:1464 No locals. #13 0xb65bc970 in QObject::event (this=0x8990378, e=0x9538ed8) at kernel/qobject.cpp:1111 currentSender = {sender = 0x86ee5d8, signal = -1, ref = 1} previousSender = 0x0 #14 0xb5a837fc in QApplicationPrivate::notify_helper (this=0x8708cf0, receiver=0x8990378, e=0x9538ed8) at kernel/qapplication.cpp:4056 consumed = <value optimized out> #15 0xb5a8baee in QApplication::notify (this=0xbfd276f4, receiver=0x8990378, e=0x9538ed8) at kernel/qapplication.cpp:3603 (+more output) *** Bug 200800 has been marked as a duplicate of this bug. *** *** Bug 200968 has been marked as a duplicate of this bug. *** *** Bug 201541 has been marked as a duplicate of this bug. *** *** Bug 202260 has been marked as a duplicate of this bug. *** Well, I've reproduced it on 4.3.0 final, maybe my report (with debugfull) will also be useful... Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/libthread_db.so.1". [KCrash Handler] #5 0x00007f6a35e4469b in QWidget::show (this=0x14352c0) at /usr/include/QtGui/qwidget.h:473 #6 0x00007f6a35e4421e in Kontact::UniqueAppHandler::newInstance (this=0x16d58a0) at /usr/src/packages/kde4/4.3.0/kdepim-4.3.0/kontactinterfaces/uniqueapphandler.cpp:137 #7 0x00007f6a1dc7021a in KOrganizerUniqueAppHandler::newInstance (this=0x16d58a0) at /usr/src/packages/kde4/4.3.0/kdepim-4.3.0/kontact/plugins/korganizer/korg_uniqueapp.cpp:37 #8 0x00007f6a35e442e9 in Kontact::UniqueAppHandler::newInstance (this=0x16d58a0, asn_id=@0x1f2f160, args=@0x1f2e930) at /usr/src/packages/kde4/4.3.0/kdepim-4.3.0/kontactinterfaces/uniqueapphandler.cpp:128 #9 0x00007f6a35e4437e in Kontact::UniqueAppHandler::qt_metacall (this=0x16d58a0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffb4625620) at /usr/src/packages/kde4/4.3.0/kdepim-4.3.0/build/kontactinterfaces/uniqueapphandler.moc:73 #10 0x00007f6a328e7b43 in QDBusConnectionPrivate::deliverCall (this=0x1343aa0, object=0x16d58a0, msg=@0x25f1540, metaTypes=@0x1b570c0, slotIdx=4) at qdbusintegrator.cpp:891 #11 0x00007f6a328e8f78 in QDBusConnectionPrivate::activateCall (this=0x1343aa0, object=0x16d58a0, flags=272, msg=@0x25f1540) at qdbusintegrator.cpp:803 #12 0x00007f6a328e9403 in QDBusConnectionPrivate::activateObject (this=0x1343aa0, node=@0x25f1518, msg=@0x25f1540, pathStartPos=26) at qdbusintegrator.cpp:1370 #13 0x00007f6a328e98f8 in QDBusActivateObjectEvent::placeMetaCall (this=0x25f14d0) at qdbusintegrator.cpp:1464 #14 0x00007f6a325d0fd8 in QObject::event (this=0x16d58a0, e=0x25f14d0) at kernel/qobject.cpp:1102 #15 0x00007f6a3131e14d in QApplicationPrivate::notify_helper (this=0x1352a40, receiver=0x16d58a0, e=0x25f14d0) at kernel/qapplication.cpp:4056 #16 0x00007f6a3132490e in QApplication::notify (this=0x7fffb46264c0, receiver=0x16d58a0, e=0x25f14d0) at kernel/qapplication.cpp:4021 #17 0x00007f6a334480cb in KApplication::notify (this=0x7fffb46264c0, receiver=0x16d58a0, event=0x25f14d0) at /usr/src/packages/kde4/4.3.0/kdelibs-4.3.0/kdeui/kernel/kapplication.cpp:302 #18 0x00007f6a325bfe0b in QCoreApplication::notifyInternal (this=0x7fffb46264c0, receiver=0x16d58a0, event=0x25f14d0) at kernel/qcoreapplication.cpp:610 #19 0x00007f6a325c0dbb in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x13010c0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #20 0x00007f6a325ec343 in postEventSourceDispatch (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #21 0x00007f6a2c8492d1 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #22 0x00007f6a2c84ca4d in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #23 0x00007f6a2c84cc0b in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #24 0x00007f6a325ec06f in QEventDispatcherGlib::processEvents (this=0x1300980, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #25 0x00007f6a313bccaf in QGuiEventDispatcherGlib::processEvents (this=0x14352c0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #26 0x00007f6a325be902 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -1268620320}) at kernel/qeventloop.cpp:149 #27 0x00007f6a325becd4 in QEventLoop::exec (this=0x7fffb4626420, flags={i = -1268620240}) at kernel/qeventloop.cpp:201 #28 0x00007f6a325c10d4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #29 0x0000000000404183 in main (argc=1, argv=0x7fffb46269d8) at /usr/src/packages/kde4/4.3.0/kdepim-4.3.0/kontact/src/main.cpp:218 CC'ing David. Perhaps he knows what's happening here since he wrote much of the code referenced. *** Bug 203019 has been marked as a duplicate of this bug. *** *** Bug 204000 has been marked as a duplicate of this bug. *** *** Bug 204420 has been marked as a duplicate of this bug. *** *** Bug 205023 has been marked as a duplicate of this bug. *** *** Bug 205334 has been marked as a duplicate of this bug. *** *** Bug 193213 has been marked as a duplicate of this bug. *** *** Bug 205711 has been marked as a duplicate of this bug. *** *** Bug 206002 has been marked as a duplicate of this bug. *** *** Bug 206429 has been marked as a duplicate of this bug. *** *** Bug 206448 has been marked as a duplicate of this bug. *** *** Bug 206675 has been marked as a duplicate of this bug. *** *** Bug 206710 has been marked as a duplicate of this bug. *** *** Bug 208177 has been marked as a duplicate of this bug. *** *** Bug 208319 has been marked as a duplicate of this bug. *** *** Bug 208626 has been marked as a duplicate of this bug. *** *** Bug 208664 has been marked as a duplicate of this bug. *** *** Bug 209791 has been marked as a duplicate of this bug. *** *** Bug 212261 has been marked as a duplicate of this bug. *** *** Bug 213629 has been marked as a duplicate of this bug. *** *** Bug 214016 has been marked as a duplicate of this bug. *** *** Bug 214194 has been marked as a duplicate of this bug. *** *** Bug 214315 has been marked as a duplicate of this bug. *** *** Bug 214583 has been marked as a duplicate of this bug. *** *** Bug 214609 has been marked as a duplicate of this bug. *** *** Bug 214750 has been marked as a duplicate of this bug. *** *** Bug 215169 has been marked as a duplicate of this bug. *** *** Bug 214098 has been marked as a duplicate of this bug. *** *** Bug 215361 has been marked as a duplicate of this bug. *** *** Bug 215466 has been marked as a duplicate of this bug. *** From bug 215512: --- What I was doing when the application crashed: I accidentally closed Kontact on the window button (not File=>Quit) and wanted to reopen it by clicking on the korgac reminder systray icon. I thought that it was supposed to work that way. BTW: Kontact doesn't quit all the time when using File=>Quit so you have to kill a stale process to be able to open it again. *** Bug 215512 has been marked as a duplicate of this bug. *** *** Bug 216728 has been marked as a duplicate of this bug. *** *** Bug 217386 has been marked as a duplicate of this bug. *** *** Bug 218117 has been marked as a duplicate of this bug. *** I disabled reminders and the systray of korganizer (implied by kontact in his Journal mandatory component), now i can open all kontact from his kmail icon in the systray. don't understand the logic behind. I disabled reminders and the systray of korganizer (implied by kontact in his Journal mandatory component), now i can open all kontact from his kmail icon in the systray. don't understand the logic behind. *** Bug 217773 has been marked as a duplicate of this bug. *** From bug 218747 (KDE SC 4.4 beta1): -- Information about the crash: After I disabled everything related to korganizer in kontact and started korganizer from the system tray icon, kontact immediately crashed. Korganizer didn't start. After a restart of kontact, everything works as expected. Updated backtrace: --- [KCrash Handler] #6 0x00fdaae0 in KontactInterface::Plugin::part (this=0x9b83be8) at ../../kontactinterface/plugin.cpp:190 #7 0x02257e0a in KOrganizerUniqueAppHandler::newInstance (this=0xa5678c8) at ../../../../kontact/plugins/korganizer/korg_uniqueapp.cpp:33 #8 0x00fdc769 in KontactInterface::UniqueAppHandler::newInstance (this=0xa5678c8, asn_id=..., args=...) at ../../kontactinterface/uniqueapphandler.cpp:129 #9 0x00fdc7f4 in KontactInterface::UniqueAppHandler::qt_metacall (this=0xa5678c8, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfd99d6c) at ./uniqueapphandler.moc:79 ... *** Bug 218747 has been marked as a duplicate of this bug. *** From bug 219979: --- What I was doing when the application crashed: Kontact (Kmail) crashes (segmentation fault) when the wireless network connection drops and Kontact doesn't know the connection is being re-negotiated. *** Bug 219979 has been marked as a duplicate of this bug. *** *** Bug 201618 has been marked as a duplicate of this bug. *** *** Bug 220476 has been marked as a duplicate of this bug. *** *** Bug 220587 has been marked as a duplicate of this bug. *** *** Bug 223045 has been marked as a duplicate of this bug. *** From bug 223788: -- What I was doing when the application crashed: Kontact crashes upon trying to view my feeds. I cannot run Akregator as a stand alone application. *** Bug 223788 has been marked as a duplicate of this bug. *** *** Bug 227577 has been marked as a duplicate of this bug. *** *** Bug 228438 has been marked as a duplicate of this bug. *** *** Bug 231080 has been marked as a duplicate of this bug. *** *** Bug 229766 has been marked as a duplicate of this bug. *** *** Bug 221968 has been marked as a duplicate of this bug. *** *** Bug 220020 has been marked as a duplicate of this bug. *** *** Bug 232822 has been marked as a duplicate of this bug. *** *** Bug 232851 has been marked as a duplicate of this bug. *** *** Bug 233641 has been marked as a duplicate of this bug. *** *** Bug 240876 has been marked as a duplicate of this bug. *** *** Bug 235668 has been marked as a duplicate of this bug. *** *** Bug 235846 has been marked as a duplicate of this bug. *** *** Bug 239984 has been marked as a duplicate of this bug. *** *** Bug 234971 has been marked as a duplicate of this bug. *** *** Bug 237352 has been marked as a duplicate of this bug. *** *** Bug 234172 has been marked as a duplicate of this bug. *** *** Bug 235496 has been marked as a duplicate of this bug. *** *** Bug 237446 has been marked as a duplicate of this bug. *** *** Bug 237094 has been marked as a duplicate of this bug. *** *** Bug 236698 has been marked as a duplicate of this bug. *** *** Bug 235761 has been marked as a duplicate of this bug. *** *** Bug 235277 has been marked as a duplicate of this bug. *** *** Bug 235195 has been marked as a duplicate of this bug. *** *** Bug 241142 has been marked as a duplicate of this bug. *** *** Bug 241881 has been marked as a duplicate of this bug. *** *** Bug 242078 has been marked as a duplicate of this bug. *** *** Bug 242751 has been marked as a duplicate of this bug. *** *** Bug 242278 has been marked as a duplicate of this bug. *** *** Bug 245901 has been marked as a duplicate of this bug. *** Created attachment 51303 [details]
New crash information added by DrKonqi
First opened kontact,then closed, then start korgnization from daemon icon,then crash.
I repeated it several times
*** Bug 249430 has been marked as a duplicate of this bug. *** *** Bug 245005 has been marked as a duplicate of this bug. *** *** Bug 246527 has been marked as a duplicate of this bug. *** *** Bug 249231 has been marked as a duplicate of this bug. *** *** Bug 248611 has been marked as a duplicate of this bug. *** *** Bug 243710 has been marked as a duplicate of this bug. *** *** Bug 246414 has been marked as a duplicate of this bug. *** Did anyone run "valgrind kontact --nofork", to get a precise valgrind log of the crash? Well, assuming "kontact --nofork" crashes in the first place. Otherwise use "valgrind --trace-children=yes kontact". *** Bug 252373 has been marked as a duplicate of this bug. *** @David Faure: Do you mean this? doonze@doonze-laptop:~$ valgrind kontact --nofork ==2447== Memcheck, a memory error detector ==2447== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==2447== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for copyright info ==2447== Command: kontact --nofork ==2447== <unknown program name>(2447)/: KUniqueApplication: Can't setup D-Bus service. Probably already running. ==2447== ==2447== HEAP SUMMARY: ==2447== in use at exit: 79,632 bytes in 175 blocks ==2447== total heap usage: 3,450 allocs, 3,275 frees, 285,928 bytes allocated ==2447== ==2447== LEAK SUMMARY: ==2447== definitely lost: 0 bytes in 0 blocks ==2447== indirectly lost: 0 bytes in 0 blocks ==2447== possibly lost: 0 bytes in 0 blocks ==2447== still reachable: 79,632 bytes in 175 blocks ==2447== suppressed: 0 bytes in 0 blocks ==2447== Rerun with --leak-check=full to see details of leaked memory ==2447== ==2447== For counts of detected and suppressed errors, rerun with: -v ==2447== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 10 from 6) Created attachment 51997 [details]
bt full from trunk
ok, I could finally reproduce (don't ask how yet)
So far:
# ps x |grep kontact
10148 pts/0 Sl 1:15 kontact
# qdbus
[cut]
:1.37
org.kde.kwalletd
:1.374
org.kde.akregator
org.kde.kaddressbook
org.kde.kjots
org.kde.kmail
org.kde.kontact
org.kde.korganizer
org.kde.ktimetracker
org.kde.pim.TransportManager
:1.376
[...]
Running Kontact under valgrind doesn't give any hint (nothing more than in #98).
Kontact seems to crash when starting one of the components only:
valgrind akregator --nofork
==11812== Memcheck, a memory error detector
==11812== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==11812== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info
==11812== Command: akregator --nofork
==11812==
FAILURE (KCmdLineArgs):
The "qt" options have not be added to KCmdLineArgs!
then kontact crashes
Not sure whether this is the same bug or not, but system information is: Application: kontact (4.4.6) KDE Platform Version: 4.5.1 (KDE 4.5.1) Qt Version: 4.7.0 Operating System: Linux 2.6.34.7-0.3-default i686 Distribution: "openSUSE 11.3 (i586)" This immediately follows a large update of openSUSE. Interestingly, KMail, KOrganizer and Akregator all start immediately as stand-alone apps (I haven't tried any other components. Valgrind report follows. Created attachment 52032 [details]
Valgrind output during crashed open-attempt
During the activity there was high CPU usage and the temperature rose by ~20'C. memcheck-x86-li was apparently using 25% of my CPU
*** Bug 253472 has been marked as a duplicate of this bug. *** *** Bug 254686 has been marked as a duplicate of this bug. *** *** Bug 255044 has been marked as a duplicate of this bug. *** *** Bug 255030 has been marked as a duplicate of this bug. *** *** Bug 255029 has been marked as a duplicate of this bug. *** *** Bug 254895 has been marked as a duplicate of this bug. *** I just run into the same issue on Kubuntu 10.10 with KDE 4.5.3. Here is the backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0xb77c4730 (LWP 1791))] Thread 2 (Thread 0xb0622b70 (LWP 1863)): #0 0x0056af85 in pthread_mutex_unlock (mutex=0xa8c089c) at forward.c:184 #1 0x04e8fe58 in g_main_context_prepare (context=0xa8c0898, priority=0xb062211c) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2467 #2 0x04e90279 in g_main_context_iterate (context=0xa8c0898, block=<value optimized out>, dispatch=1, self=0xa8c0978) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2760 #3 0x04e90848 in g_main_context_iteration (context=0xa8c0898, may_block=1) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2843 #4 0x02de559f in QEventDispatcherGlib::processEvents (this=0xa8c0860, flags=...) at kernel/qeventdispatcher_glib.cpp:417 #5 0x02db5609 in QEventLoop::processEvents (this=0xb0622270, flags=) at kernel/qeventloop.cpp:149 #6 0x02db5a8a in QEventLoop::exec (this=0xb0622270, flags=...) at kernel/qeventloop.cpp:201 #7 0x02cb1b7e in QThread::exec (this=0x9bbfc08) at thread/qthread.cpp:490 #8 0x02d9435b in QInotifyFileSystemWatcherEngine::run (this=0x9bbfc08) at io/qfilesystemwatcher_inotify.cpp:248 #9 0x02cb4df9 in QThreadPrivate::start (arg=0x9bbfc08) at thread/qthread_unix.cpp:266 #10 0x00a25cc9 in start_thread (arg=0xb0622b70) at pthread_create.c:304 #11 0x0055d6ae in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb77c4730 (LWP 1791)): [KCrash Handler] #7 0x00000001 in ?? () #8 0x00837da3 in KontactInterface::Plugin::part (this=0x9fa9318) at ../../kontactinterface/plugin.cpp:191 #9 0x02c2fd1a in KOrganizerUniqueAppHandler::newInstance (this=0x9fa5838) at ../../../../kontact/plugins/korganizer/korg_uniqueapp.cpp:33 #10 0x008390e9 in KontactInterface::UniqueAppHandler::newInstance (this=0x9fa5838, asn_id=..., args=...) at ../../kontactinterface/uniqueapphandler.cpp:129 #11 0x00839174 in KontactInterface::UniqueAppHandler::qt_metacall (this=0x9fa5838, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbff720ac) at ./uniqueapphandler.moc:79 #12 0x006319dc in QDBusConnectionPrivate::deliverCall (this=0x9ac8a58, object=0x9fa5838, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:919 #13 0x00632cbf in QDBusConnectionPrivate::activateCall (this=0x9ac8a58, object=0x9fa5838, flags=272, msg=...) at qdbusintegrator.cpp:822 #14 0x0063349c in QDBusConnectionPrivate::activateObject (this=0x9ac8a58, node=..., msg=..., pathStartPos=26) at qdbusintegrator.cpp:1399 #15 0x00633a2a in QDBusActivateObjectEvent::placeMetaCall (this=0xa4591b8) at qdbusintegrator.cpp:1493 #16 0x02dc96a2 in QObject::event (this=0x9fa5838, e=0x9fa9b50) at kernel/qobject.cpp:1219 #17 0x01262fdc in QApplicationPrivate::notify_helper (this=0x9ae0a60, receiver=0x9fa5838, e=0xa4591b8) at kernel/qapplication.cpp:4396 #18 0x0126904e in QApplication::notify (this=0xbff72ac4, receiver=0x9fa5838, e=0xa4591b8) at kernel/qapplication.cpp:3798 #19 0x00f5801a in KApplication::notify (this=0xbff72ac4, receiver=0x9fa5838, event=0xa4591b8) at ../../kdeui/kernel/kapplication.cpp:310 #20 0x02db6b3b in QCoreApplication::notifyInternal (this=0xbff72ac4, receiver=0x9fa5838, event=0xa4591b8) at kernel/qcoreapplication.cpp:732 #21 0x02db9d8b in sendEvent (receiver=0x0, event_type=0, data=0x9aafed0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #22 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9aafed0) at kernel/qcoreapplication.cpp:1373 #23 0x02db9f4d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1266 #24 0x02de5a74 in sendPostedEvents (s=0x9ae2590) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220 #25 postEventSourceDispatch (s=0x9ae2590) at kernel/qeventdispatcher_glib.cpp:277 #26 0x04e8c855 in g_main_dispatch (context=0x9ae2510) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2149 #27 g_main_context_dispatch (context=0x9ae2510) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2702 #28 0x04e90668 in g_main_context_iterate (context=0x9ae2510, block=<value optimized out>, dispatch=1, self=0x9ad11e0) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2780 #29 0x04e90848 in g_main_context_iteration (context=0x9ae2510, may_block=1) at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2843 #30 0x02de5565 in QEventDispatcherGlib::processEvents (this=0x9aafb90, flags=...) at kernel/qeventdispatcher_glib.cpp:415 #31 0x01324be5 in QGuiEventDispatcherGlib::processEvents (this=0x9aafb90, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #32 0x02db5609 in QEventLoop::processEvents (this=0xbff72a24, flags=) at kernel/qeventloop.cpp:149 #33 0x02db5a8a in QEventLoop::exec (this=0xbff72a24, flags=...) at kernel/qeventloop.cpp:201 #34 0x02dba00f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #35 0x01261e07 in QApplication::exec () at kernel/qapplication.cpp:3672 #36 0x0804b132 in main (argc=3, argv=0xbff72ce4) at ../../../kontact/src/main.cpp:224 I have finally beaten this. If you haven't already done so, go through all the relevant rc files looking for references to the SpecialDates Plugin, and remove them. I thought I had already done this, but I had missed one. Removing that now allows me to use Kontact normally and completely. I believe this could use a thorough retest with the new "Kontact Desktop" which is now trunk, but should get Kontact 4.6. It fully uses the Kontact Services for all of Mail, Calendar, Contacts, Notes and Tasks. With my version I have something similiar, sometimes: Sometimes "kontact" does not give any respondse and refuses to start, if try to start korganizer then, I get a crash dialog and after it kontact starts again. kontact --version Qt: 4.6.3 KDE: 4.5.1 (KDE 4.5.1) Kontact: 4.6 pre Debian Squeeze/Sid package: kdepim 4:4.5~e5.20101112.1197730-kk4.1198061 part of the backtrace I get from the "Kontact Calender" start: Thread 1 (Thread 0xb3204710 (LWP 5899)): [KCrash Handler] #7 0x0061006d in ?? () #8 0xb773ebe9 in KontactInterface::UniqueAppHandler::newInstance (this=0x8bc372 8, asn_id=..., args=...) at ../../kontactinterface/uniqueapphandler.cpp:129 #9 0xb773ec74 in KontactInterface::UniqueAppHandler::qt_metacall (this=0x8d4614 0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfad3cb8) at ./uniqueapphandler .moc:79 #10 0xb4d0bac1 in QDBusConnectionPrivate::deliverCall (this=0x8b137a8, object=0x 8d46140, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:904 *** Bug 257170 has been marked as a duplicate of this bug. *** *** Bug 256717 has been marked as a duplicate of this bug. *** *** Bug 256534 has been marked as a duplicate of this bug. *** Created attachment 54031 [details]
New crash information added by DrKonqi
Kontact crashes when I close it, go to sleep mode, go back from sleep mode and open Kmail. The bug can be reproduces repeatedly.
Created attachment 54534 [details]
New crash information added by DrKonqi
opened kontact, it did not retrieve my email, closed kontact. was unable to open it again.
*** Bug 260348 has been marked as a duplicate of this bug. *** *** Bug 261042 has been marked as a duplicate of this bug. *** *** Bug 262516 has been marked as a duplicate of this bug. *** Update for this bug: A reliable way to reproduce the crash was given in bug 261042: -- Information about the crash: - What I was doing when the application crashed: I disabled akregator in kontact settings, watched it close and get removed from the system tray. After it was gone, I started it separately, which resulted in this crash. A patch was tested successfully. The fixing commit shall come soon® David: Can you commit your fix ? I believe Dirk is about to tag 4.6.0 SVN commit 1215945 by cgiboudeaux: Make sure the applications are unregistered when the module is unloaded. BUG: 194268 MERGE: 4.6 M +4 -1 uniqueapphandler.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1215945 SVN commit 1215946 by cgiboudeaux: Backport r1215945 from trunk to 4.6: Make sure the applications are unregistered when the module is unloaded. CCBUG: 194268 FIXED-IN: 4.6.0 M +4 -1 uniqueapphandler.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1215946 *** Bug 230500 has been marked as a duplicate of this bug. *** Please remove me from this bug ... this tracker is ugly and does not seem to allow removing myself from this bug ... *** Bug 265347 has been marked as a duplicate of this bug. *** *** Bug 267971 has been marked as a duplicate of this bug. *** *** Bug 268954 has been marked as a duplicate of this bug. *** |