Application: akonadi_imap_resource (4.14) KDE Platform Version: 4.14.9 Qt Version: 4.8.6 Operating System: Linux 3.16.7-21-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Nothing. It just popped out the crash message. The same happens with the windows client (http://mirror.kolabsys.com/pub/upload/windows/K3-Kontact-Beta-latest.exe) The crash can be reproduced every time. -- Backtrace: Application: imap.mykolab.com vom Typ IMAP-E-Mail-Server (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f948b61f7c0 (LWP 2697))] Thread 2 (Thread 0x7f9477f0d700 (LWP 3662)): #0 0x00007f9486f8bc5d in poll () at /lib64/libc.so.6 #1 0x00007f9485f13be4 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007f9485f13cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007f948ac6d0de in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #4 0x00007f948ac3ee6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #5 0x00007f948ac3f165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #6 0x00007f948ab3c0bf in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x00007f948ab3e79f in () at /usr/lib64/libQtCore.so.4 #8 0x00007f94865f80a4 in start_thread () at /lib64/libpthread.so.0 #9 0x00007f9486f9408d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f948b61f7c0 (LWP 2697)): [KCrash Handler] #5 0x0000000000000054 in () #6 0x00007f948ac55314 in QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) () at /usr/lib64/libQtCore.so.4 #7 0x00007f948b12a7ce in () at /usr/lib64/libakonadi-kde.so.4 #8 0x00007f948b1306c8 in () at /usr/lib64/libakonadi-kde.so.4 #9 0x00007f948ac541fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #10 0x00007f948b13a99e in () at /usr/lib64/libakonadi-kde.so.4 #11 0x00007f948b13b8bd in () at /usr/lib64/libakonadi-kde.so.4 #12 0x00007f948ac5859e in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4 #13 0x00007f9489fd976c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #14 0x00007f9489fdfcad in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #15 0x00007f94880efe0a in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5 #16 0x00007f948ac402ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4 #17 0x00007f948ac4357d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQtCore.so.4 #18 0x00007f948ac6d8fe in () at /usr/lib64/libQtCore.so.4 #19 0x00007f9485f13a04 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #20 0x00007f9485f13c48 in () at /usr/lib64/libglib-2.0.so.0 #21 0x00007f9485f13cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #22 0x00007f948ac6d0be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #23 0x00007f948a076676 in () at /usr/lib64/libQtGui.so.4 #24 0x00007f948ac3ee6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #25 0x00007f948ac3f165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #26 0x00007f948ac445b9 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4 #27 0x00007f948b129f83 in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () at /usr/lib64/libakonadi-kde.so.4 #28 0x0000000000419f53 in _start () Reported using DrKonqi
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.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 oportunity 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.