Version: (using KDE 4.0.83) Installed from: Debian testing/unstable Packages OS: Linux Recent updates of KDE has caused kontact to not start (or start very late). There is some dbus connection error. But eventually I've also started seeing crashes.
Application: Kontact (kontact), signal SIGSEGV Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb4d54720 (LWP 7516)] [New Thread 0xb07feb90 (LWP 7794)] [KCrash handler] #6 0xb708ac8f in KJob::kill (this=0x92e1fa8, verbosity=KJob::EmitResult) at /tmp/buildd/kde4libs-4.0.84+svn828328/kdecore/jobs/kjob.cpp:106 #7 0xb7c80c62 in KAbstractWidgetJobTracker::slotStop (this=0x9acabf8, job=0x92e1fa8) at /tmp/buildd/kde4libs-4.0.84+svn828328/kdeui/jobs/kabstractwidgetjobtracker.cpp:129 #8 0xb7c81942 in KWidgetJobTracker::Private::ProgressWidget::_k_stop ( this=0x9ca15f0) at /tmp/buildd/kde4libs-4.0.84+svn828328/kdeui/jobs/kwidgetjobtracker.cpp:629 #9 0xb7c82aab in KWidgetJobTracker::Private::ProgressWidget::qt_metacall ( this=0x9ca15f0, _c=QMetaObject::InvokeMetaMethod, _id=13, _a=0xbfab061c) at /tmp/buildd/kde4libs-4.0.84+svn828328/obj-i486-linux-gnu/kdeui/kwidgetjobtracker_p.moc:101 #10 0xb6ee0090 in QMetaObject::activate (sender=0x9cc7af0, from_signal_index=29, to_signal_index=30, argv=0xbfab061c) at kernel/qobject.cpp:3010 #11 0xb6ee0490 in QMetaObject::activate (sender=0x9cc7af0, m=0xb7aabc44, from_local_signal_index=2, to_local_signal_index=3, argv=0xbfab061c) at kernel/qobject.cpp:3100 #12 0xb78e2da1 in QAbstractButton::clicked (this=0x9cc7af0, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:185 #13 0xb7638789 in QAbstractButtonPrivate::emitClicked (this=0x9cc7b40) at widgets/qabstractbutton.cpp:543 #14 0xb763a2f4 in QAbstractButtonPrivate::click (this=0x9cc7b40) at widgets/qabstractbutton.cpp:536 #15 0xb763a586 in QAbstractButton::mouseReleaseEvent (this=0x9cc7af0, e=0xbfab0cbc) at widgets/qabstractbutton.cpp:1112 #16 0xb73594f2 in QWidget::event (this=0x9cc7af0, event=0xbfab0cbc) at kernel/qwidget.cpp:6927 #17 0xb763862e in QAbstractButton::event (this=0x9cc7af0, e=0xbfab0cbc) at widgets/qabstractbutton.cpp:1074 #18 0xb76de570 in QPushButton::event (this=0x9cc7af0, e=0xbfab0cbc) at widgets/qpushbutton.cpp:658 #19 0xb730166c in QApplicationPrivate::notify_helper (this=0x9061a28, receiver=0x9cc7af0, e=0xbfab0cbc) at kernel/qapplication.cpp:3772 #20 0xb7309df1 in QApplication::notify (this=0xbfab158c, receiver=0x9cc7af0, e=0xbfab0cbc) at kernel/qapplication.cpp:3501 #21 0xb7c8dfdd in KApplication::notify (this=0xbfab158c, receiver=0x9cc7af0, event=0xbfab0cbc) at /tmp/buildd/kde4libs-4.0.84+svn828328/kdeui/kernel/kapplication.cpp:311 #22 0xb6ecb541 in QCoreApplication::notifyInternal (this=0xbfab158c, receiver=0x9cc7af0, event=0xbfab0cbc) at kernel/qcoreapplication.cpp:587 #23 0xb730907e in QApplicationPrivate::sendMouseEvent (receiver=0x9cc7af0, event=0xbfab0cbc, alienWidget=0x9cc7af0, nativeWidget=0x9ca15f0, buttonDown=0xb7ab77d0, lastMouseReceiver=@0xb7ab77d4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #24 0xb73725fd in QETWidget::translateMouseEvent (this=0x9ca15f0, event=0xbfab11ac) at kernel/qapplication_x11.cpp:4133 #25 0xb73713cf in QApplication::x11ProcessEvent (this=0xbfab158c, event=0xbfab11ac) at kernel/qapplication_x11.cpp:3255 #26 0xb739ad14 in x11EventSourceDispatch (s=0x90645e0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148 #27 0xb570c978 in IA__g_main_context_dispatch (context=0x9063a58) at /build/buildd/glib2.0-2.16.3/glib/gmain.c:2009 #28 0xb570fbce in g_main_context_iterate (context=0x9063a58, block=1, dispatch=1, self=0x9060808) at /build/buildd/glib2.0-2.16.3/glib/gmain.c:2642 #29 0xb571011c in IA__g_main_context_iteration (context=0x9063a58, may_block=1) at /build/buildd/glib2.0-2.16.3/glib/gmain.c:2705 #30 0xb6ef5b48 in QEventDispatcherGlib::processEvents (this=0x905ca78, flags= {i = -1079307432}) at kernel/qeventdispatcher_glib.cpp:325 #31 0xb739a415 in QGuiEventDispatcherGlib::processEvents (this=0x905ca78, flags={i = -1079307384}) at kernel/qguieventdispatcher_glib.cpp:204 #32 0xb6ec9c2a in QEventLoop::processEvents (this=0xbfab1400, flags= {i = -1079307320}) at kernel/qeventloop.cpp:149 #33 0xb6ec9dea in QEventLoop::exec (this=0xbfab1400, flags={i = -1079307256}) at kernel/qeventloop.cpp:200 #34 0xb6ecc495 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #35 0xb73014e7 in QApplication::exec () at kernel/qapplication.cpp:3304 #36 0x0804bd9e in main (argc=1, argv=0xbfab1784) at /tmp/buildd/kdepim-4.0.84/kontact/src/main.cpp:210 #37 0xb6b60450 in __libc_start_main () from /lib/i686/cmov/libc.so.6 #38 0x0804a511 in _start () #0 0xb7f98424 in __kernel_vsyscall ()
Please don't mix the issues. This backtrace is unrelated and the issue was resolved. (bug 165912). Run kontact from a console and paste the dbus error.
rrs@learner:~$ kontact kontact(28581) KWallet::Wallet::openWallet: Pass a valid window to KWallet::Wallet::openWallet(). kontact(28581) KDBusServiceStarter::findServiceFor: DBus service is available now, as "org.kde.kmail" kontact(28581) ViewManager::setActiveView: entering ViewManager::setActiveView kontact(28581) KStatusBar::removeItem: KStatusBar::removeItem: bad item id: 1 kontact(28581) KStatusBar::removeItem: KStatusBar::removeItem: bad item id: 2 kontact(28581) KStatusBar::removeItem: KStatusBar::removeItem: bad item id: 1 kontact(28581) KStatusBar::removeItem: KStatusBar::removeItem: bad item id: 2 kontact(28581) KDBusServiceStarter::findServiceFor: DBus service is available now, as "org.kde.kmail" kontact(28581) Kolab::Incidence::loadAttribute: Saving unhandled tag "inline-attachment" <unknown program name>(28580)/: Communication problem with "kontact" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or thenetwork connection was broken." "
I've re-installed KDE 4.1 and this issue is back again. On a fresh user account this issue is not seen. But for the user, which was running kDE3 earlier, this issue is there. I find the following in .xsession-errors rrs@learner:~$ grep -i kmail .xsession-errors kopete(4599) KDBusServiceStarter::findServiceFor: DBus service is available now, as "org.kde.kmail" korgac(4629) KDBusServiceStarter::findServiceFor: DBus service is available now, as "org.kde.kmail" krunner(4533) KDBusServiceStarter::findServiceFor: DBus service is available now, as "org.kde.kmail"
rrs@learner:~$ kontact kontact(10129) KWallet::Wallet::openWallet: Pass a valid window to KWallet::Wallet::openWallet(). kontact(10129) KDBusServiceStarter::findServiceFor: DBus service is available now, as "org.kde.kmail" kontact(10129) KDBusServiceStarter::findServiceFor: DBus service is available now, as "org.kde.kmail" kontact(10129) Kolab::Incidence::loadAttribute: Saving unhandled tag "inline-attachment" <unknown program name>(10128)/: Communication problem with "kontact" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "
I'm closing this bug as I don't see the problem with the latest KDEPIM.