Application: kontact (4.4.3) KDE Platform Version: 4.4.3 (KDE 4.4.3) Qt Version: 4.6.2 Operating System: Linux 2.6.33.2-tp42-toi-3.1-lowmem-free-991-992-04964-gf00c7ec-dirty i686 Distribution: Debian GNU/Linux testing (squeeze) -- Information about the crash: I told KMail to receive new mail from my POP3 accounts. I marked a mail as spam and before KMail completed the filter action switched to inbox to look for new mail. KMail was slow due to background cron jobs (updating mlocate database). I had this twice with KDE 4.4.3. I don't remember having it with KDE 4.4.2. I run KMail within Kontact. It might be a duplicate of some of the bugs I told DrKonqi, but the backtrace looks slightly different. I don't know why the entry point in libglib is not resolved. I have debug package installed. I am using: martin@shambhala:~> apt-show-versions | egrep "(kontact/|kmail/|libqt4-gui/|kdelibs|kdepim|libglib)" kdelibs-bin/sid uptodate 4:4.4.3-1 kdelibs-data/squeeze uptodate 4:3.5.10.dfsg.1-3 kdelibs4c2a/squeeze uptodate 4:3.5.10.dfsg.1-3 kdelibs5/sid uptodate 4:4.4.3-1 kdelibs5-data/sid uptodate 4:4.4.3-1 kdelibs5-dbg/sid uptodate 4:4.4.3-1 kdelibs5-dev/sid uptodate 4:4.4.3-1 kdelibs5-plugins/sid uptodate 4:4.4.3-1 kdepim/sid uptodate 4:4.4.3-1 kdepim-dbg/sid uptodate 4:4.4.3-1 kdepim-groupware/sid uptodate 4:4.4.3-1 kdepim-kresources/sid uptodate 4:4.4.3-1 kdepim-runtime/sid uptodate 4:4.4.3-1 kdepim-runtime-dbg/sid uptodate 4:4.4.3-1 kdepim-strigi-plugins/sid uptodate 4:4.4.3-1 kdepim-wizards/sid uptodate 4:4.4.3-1 kdepimlibs-dbg/sid uptodate 4:4.4.3-1 kdepimlibs-kio-plugins/sid uptodate 4:4.4.3-1 kdepimlibs5/sid uptodate 4:4.4.3-1 kmail/sid uptodate 4:4.4.3-1 kontact/sid uptodate 4:4.4.3-1 libglib2.0-0/squeeze uptodate 2.24.0-1 libglib2.0-data/squeeze uptodate 2.24.0-1 libglib2.0-dev/squeeze uptodate 2.24.0-1 libglibmm-2.4-1c2a/squeeze uptodate 2.24.1-1 libkdepim4/sid uptodate 4:4.4.3-1 libqt4-gui/squeeze uptodate 4:4.6.2-4 On an IBM ThinkPad T42. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0xafd1643e in KMCommand::slotStart (this=0x15899dd8) at ../../kmail/kmcommands.cpp:261 #7 0xafd0d9ab in KMCommand::qt_metacall (this=0x15899dd8, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfce863c) at ./kmcommands.moc:92 #8 0xafd0e032 in KMFilterActionCommand::qt_metacall (this=0x15899dd8, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfce863c) at ./kmcommands.moc:1681 #9 0xb6db2aea in QMetaObject::metacall (object=0x15899dd8, cl=399745640, idx=8, argv=0xbfce863c) at kernel/qmetaobject.cpp:237 #10 0xb6dc10b5 in QMetaObject::activate (sender=0xc203b30, m=0xb6ebf2e8, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293 #11 0xb6dc8d17 in QSingleShotTimer::timeout (this=0xc203b30) at .moc/release-shared/qtimer.moc:82 #12 0xb6dc8e2c in QSingleShotTimer::timerEvent (this=0xc203b30) at kernel/qtimer.cpp:308 #13 0xb6dbdf34 in QObject::event (this=0xc203b30, e=0x18a3edc0) at kernel/qobject.cpp:1212 #14 0xb62f3bec in QApplicationPrivate::notify_helper (this=0x86d4ca0, receiver=0xc203b30, e=0xbfce8b70) at kernel/qapplication.cpp:4300 #15 0xb62fa75e in QApplication::notify (this=0xbfce8ed4, receiver=0xc203b30, e=0xbfce8b70) at kernel/qapplication.cpp:3704 #16 0xb72fb7da in KApplication::notify (this=0xbfce8ed4, receiver=0xc203b30, event=0xbfce8b70) at ../../kdeui/kernel/kapplication.cpp:302 #17 0xb6dad8eb in QCoreApplication::notifyInternal (this=0xbfce8ed4, receiver=0xc203b30, event=0xbfce8b70) at kernel/qcoreapplication.cpp:704 #18 0xb6ddc946 in QCoreApplication::sendEvent (this=0x86eed2c) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #19 QTimerInfoList::activateTimers (this=0x86eed2c) at kernel/qeventdispatcher_unix.cpp:603 #20 0xb6dd9604 in timerSourceDispatch (source=0x86eecf8) at kernel/qeventdispatcher_glib.cpp:184 #21 0xb424f2e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #22 0xb4253000 in ?? () from /lib/libglib-2.0.so.0 #23 0xb4253198 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #24 0xb6dd92f5 in QEventDispatcherGlib::processEvents (this=0x86b48c0, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #25 0xb63b2255 in QGuiEventDispatcherGlib::processEvents (this=0x86b48c0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #26 0xb6dabf09 in QEventLoop::processEvents (this=0xbfce8e34, flags=) at kernel/qeventloop.cpp:149 #27 0xb6dac35a in QEventLoop::exec (this=0xbfce8e34, flags=...) at kernel/qeventloop.cpp:201 #28 0xb6db04ef in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #29 0xb62f3c87 in QApplication::exec () at kernel/qapplication.cpp:3579 #30 0x0804b472 in main (argc=1, argv=0xbfce90d4) at ../../../kontact/src/main.cpp:224 This bug may be a duplicate of or related to bug 163071, bug 203459, bug 203105. Possible duplicates by query: bug 223722, bug 218362, bug 203459, bug 203105. Reported using DrKonqi
I don´t see this anymore with recent KDE versions, currently KDE SC 4.7.4 with KDEPIM 4.4.5. Thus closing as "WORKSFORME" since I do not see a fix targeted at this in the comments. Feel free to adapt resolution to "FIXED" if it seems to be more suitable to you.