Application that crashed: kontact Version of the application: 4.3.0 KDE Version: 4.3.00 (KDE 4.3.0) Qt Version: 4.5.1 Operating System: Linux 2.6.30-gentoo-r4 x86_64 What I was doing when the application crashed: Kontact crashes after saving remote calenda -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 0x00007f521dd8e024 in KCal::IncidenceBase::uid () from /usr/lib64/libkcal.so.4 #6 0x00007f521de08d79 in KCal::ResourceCached::clearChange () from /usr/lib64/libkcal.so.4 #7 0x00007f52005990af in KCal::ResourceRemote::slotSaveJobResult () from /usr/lib64/libkcal_resourceremote.so.4 #8 0x00007f5200599558 in KCal::ResourceRemote::qt_metacall () from /usr/lib64/libkcal_resourceremote.so.4 #9 0x00007f521a49cec5 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4 #10 0x00007f521aaae612 in KJob::result () from /usr/lib64/libkdecore.so.5 #11 0x00007f521aaae98f in KJob::emitResult () from /usr/lib64/libkdecore.so.5 #12 0x00007f521c7c500b in KIO::FileCopyJob::slotResult () from /usr/lib64/libkio.so.5 #13 0x00007f521c7c16b4 in KIO::FileCopyJob::qt_metacall () from /usr/lib64/libkio.so.5 #14 0x00007f521a49cec5 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4 #15 0x00007f521aaae612 in KJob::result () from /usr/lib64/libkdecore.so.5 #16 0x00007f521aaae98f in KJob::emitResult () from /usr/lib64/libkdecore.so.5 #17 0x00007f521c7bde88 in KIO::SimpleJob::slotFinished () from /usr/lib64/libkio.so.5 #18 0x00007f521c7bfb63 in KIO::TransferJob::slotFinished () from /usr/lib64/libkio.so.5 #19 0x00007f521c7c0bc5 in KIO::TransferJob::qt_metacall () from /usr/lib64/libkio.so.5 #20 0x00007f521a49cec5 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4 #21 0x00007f521c87c489 in KIO::SlaveInterface::dispatch () from /usr/lib64/libkio.so.5 #22 0x00007f521c879061 in KIO::SlaveInterface::dispatch () from /usr/lib64/libkio.so.5 #23 0x00007f521c86bdd3 in KIO::Slave::gotInput () from /usr/lib64/libkio.so.5 #24 0x00007f521c86dfd8 in KIO::Slave::qt_metacall () from /usr/lib64/libkio.so.5 #25 0x00007f521a49cec5 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4 #26 0x00007f521c78a1cf in ?? () from /usr/lib64/libkio.so.5 #27 0x00007f521c78a62a in KIO::Connection::qt_metacall () from /usr/lib64/libkio.so.5 #28 0x00007f521a499901 in QObject::event () from /usr/lib64/qt4/libQtCore.so.4 #29 0x00007f521afd7ebd in QApplicationPrivate::notify_helper () from /usr/lib64/qt4/libQtGui.so.4 #30 0x00007f521afe077a in QApplication::notify () from /usr/lib64/qt4/libQtGui.so.4 #31 0x00007f521bd99cab in KApplication::notify () from /usr/lib64/libkdeui.so.5 #32 0x00007f521a48ace3 in QCoreApplication::notifyInternal () from /usr/lib64/qt4/libQtCore.so.4 #33 0x00007f521a48b5e6 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib64/qt4/libQtCore.so.4 #34 0x00007f521a4aff13 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #35 0x00007f52156264b2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #36 0x00007f5215629795 in ?? () from /usr/lib/libglib-2.0.so.0 #37 0x00007f5215629c9b in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #38 0x00007f521a4afbbf in QEventDispatcherGlib::processEvents () from /usr/lib64/qt4/libQtCore.so.4 #39 0x00007f521b05e29f in ?? () from /usr/lib64/qt4/libQtGui.so.4 #40 0x00007f521a4896e2 in QEventLoop::processEvents () from /usr/lib64/qt4/libQtCore.so.4 #41 0x00007f521a489875 in QEventLoop::exec () from /usr/lib64/qt4/libQtCore.so.4 #42 0x00007f521a48b874 in QCoreApplication::exec () from /usr/lib64/qt4/libQtCore.so.4 #43 0x0000000000404b51 in _start () Reported using DrKonqi
Please provide better backtrace (reemerge kdelibs and maybe some kdepim packages with debug symbols). On gentoo, follow http://www.gentoo.org/proj/en/qa/backtraces.xm You can find more info about per-package features and cflags here: http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=tree;f=Documentation/env;hb=master
Probably the same as bug 189740. Do you agree Maciej ? Thanks
I have no idea really, may be similar scenario but backtrace is bit different. I'd wait for reporter to provide better one. @fleg Please drop in #gentoo-kde if you're uncertain how to obtain valid one.
No response. Marking as NEEDSINFO
Closing the old crash reports which don't have a useful backtrace. Thanks.