Version: 1.10.0 (using KDE 4.1.0) OS: Linux Installed from: Mandriva RPMs kmail crashes on imap folder refesh, usually this happens when returning from hibernation this happens all the time, there's about 50% probability that it crashed when resuming system
Created attachment 27729 [details] crash log
Pasted backtrace from comment 1: Application: Kontact (kontact), signal SIGABRT (no debugging symbols found) Using host libthread_db library "/lib/i686/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1265342768 (LWP 7976)] [New Thread -1330508912 (LWP 8075)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #6 0xffffe410 in __kernel_vsyscall () #7 0xb6a0f5d5 in raise () from /lib/i686/libc.so.6 #8 0xb6a11021 in abort () from /lib/i686/libc.so.6 #9 0xb6a0870e in __assert_fail () from /lib/i686/libc.so.6 #10 0xb68574ed in QObject::disconnectNotify () from /opt/kde4/lib/libkio.so.5 #11 0xb685c137 in KIO::Scheduler::qt_metacall () from /opt/kde4/lib/libkio.so.5 #12 0xb768a3dc in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #13 0xb768ab05 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #14 0xb76c92d5 in QTimer::timeout () from /usr/lib/libQtCore.so.4 #15 0xb7691a50 in QTimer::timerEvent () from /usr/lib/libQtCore.so.4 #16 0xb7685eda in QObject::event () from /usr/lib/libQtCore.so.4 #17 0xb6d3d651 in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #18 0xb6d413e9 in QApplication::notify () from /usr/lib/libQtGui.so.4 #19 0xb7b9c011 in KApplication::notify () from /opt/kde4/lib/libkdeui.so.5 #20 0xb7674d25 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #21 0xb76a3ebe in QObject::disconnectNotify () from /usr/lib/libQtCore.so.4 #22 0xb76a16be in QObject::disconnectNotify () from /usr/lib/libQtCore.so.4 #23 0xb5367a30 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #24 0xb536ad05 in QObject::disconnectNotify () from /usr/lib/libglib-2.0.so.0 #25 0xb536b218 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #26 0xb76a1c3a in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #27 0xb6dd38aa in QObject::disconnectNotify () from /usr/lib/libQtGui.so.4 #28 0xb7673fe1 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #29 0xb7674169 in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #30 0xb767621e in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #31 0xb6d3cd94 in QApplication::exec () from /usr/lib/libQtGui.so.4 #32 0x0804ba3f in _start () #0 0xffffe410 in __kernel_vsyscall ()
Can you still reproduce this bug again with a recent KDE version ( 4.1.3 / 4.2beta1 / 4.2svn)? Thanks :)
No news from the bug reporter, closing. Please reopen this bug report if you experience the same bug again with a recent KDE (4.1.4 / 4.2.0 / 4.2svn / 4.3svn) and if you can post more information about the bug. Thanks :)