Application: akonadi_imap_resource (4.14) KDE Platform Version: 4.14.9 Qt Version: 4.8.6 Operating System: Linux 3.16.7-29-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Kmail asked me about bad certificates from my mail provider and I accepted it. - Unusual behavior I noticed: Not really unusual, but I was doing some backup of my data so the hard drive was on "stress". Not sure it could be related. -- Backtrace: Application: la ressource « dupeloux.fr » de type Serveur de courriers électroniques IMAP (akonadi_imap_resource), signal: Bus error Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f389de967c0 (LWP 2352))] Thread 2 (Thread 0x7f388a1c7700 (LWP 8508)): #0 0x00007f38997f3c5d in poll () at /lib64/libc.so.6 #1 0x00007f389877bbe4 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007f389877bcec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007f389d4dc0de in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #4 0x00007f389d4ade6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #5 0x00007f389d4ae165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #6 0x00007f389d3ab0bf in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x00007f389d3ad79f in () at /usr/lib64/libQtCore.so.4 #8 0x00007f3898e600a4 in start_thread () at /lib64/libpthread.so.0 #9 0x00007f38997fc08d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f389de967c0 (LWP 2352)): [KCrash Handler] #5 0x00007f389d4b9626 in QMetaObject::invokeMethod(QObject*, char const*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () at /usr/lib64/libQtCore.so.4 #6 0x00007f389b10bf18 in () at /usr/lib64/libkimap.so.4 #7 0x00007f389d4c759e in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4 #8 0x00007f389c84876c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #9 0x00007f389c84ecad in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #10 0x00007f389a95ee0a in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5 #11 0x00007f389d4af2ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4 #12 0x00007f389d4b257d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQtCore.so.4 #13 0x00007f389d4dc8fe in () at /usr/lib64/libQtCore.so.4 #14 0x00007f389877ba04 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #15 0x00007f389877bc48 in () at /usr/lib64/libglib-2.0.so.0 #16 0x00007f389877bcec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #17 0x00007f389d4dc0be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #18 0x00007f389c8e5676 in () at /usr/lib64/libQtGui.so.4 #19 0x00007f389d4ade6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #20 0x00007f389d4ae165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #21 0x00007f389d4b35b9 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4 #22 0x00007f389d998f83 in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () at /usr/lib64/libakonadi-kde.so.4 #23 0x0000000000419f53 in _start () Reported using DrKonqi
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.