Application: akonadi_imap_resource (4.8) KDE Platform Version: 4.8.3 (4.8.3) "release 5" Qt Version: 4.8.1 Operating System: Linux 3.1.10-1.9-desktop x86_64 Distribution: "openSUSE 12.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: check for all new e-mails from kontact, I get the crash report repeatedly. - Custom settings of the application: system : up to date OpenSuse Tumbleweed, uname -a : Linux 3.1.10-1.9-desktop #1 SMP PREEMPT x86_64 zypper info kontact Dépot: openSUSE-Tumbleweed Nom: kontact Version: 4.8.3-4.2 Arch: x86_64 Fabricant: obs://build.opensuse.org/openSUSE:Tumbleweed Custom setting: Nothing that is worth noting, I used free.fr configuration with also zimbra.free.fr activated. (d)imap servers from gmail.com and another source (I think based on horde) are correctely working. I move from pop.free.fr to imap, akonadi reports 100% successful sync, and I only get e-mail headers. All e-mail bodies are empty except those filtered to spam folders. I also get the same emptied body list on the zimbra server when kontact sync has been launched. The crash can be reproduced every time. -- Backtrace: Application: Free of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault [Current thread is 1 (Thread 0x7f2023975760 (LWP 14884))] Thread 3 (Thread 0x7f2012840700 (LWP 14886)): #0 0x00007f201ec38014 in pthread_mutex_lock () from /lib64/libpthread.so.0 #1 0x00007f201dccaf44 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f2022dfb2e6 in QEventDispatcherGlib::processEvents (this=0x7f200c0008c0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:426 #3 0x00007f2022dcb012 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #4 0x00007f2022dcb267 in QEventLoop::exec (this=0x7f201283fe00, flags=...) at kernel/qeventloop.cpp:204 #5 0x00007f2022ccb547 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501 #6 0x00007f20219e5119 in ?? () from /usr/lib64/libkimap.so.4 #7 0x00007f2022cce56b in QThreadPrivate::start (arg=0x88c870) at thread/qthread_unix.cpp:298 #8 0x00007f201ec35f05 in start_thread () from /lib64/libpthread.so.0 #9 0x00007f201f38310d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f200b3c5700 (LWP 14895)): #0 0x00007f201f379ff3 in poll () from /lib64/libc.so.6 #1 0x00007f201dccaa98 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f201dccaf59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f2022dfb2e6 in QEventDispatcherGlib::processEvents (this=0x7f20000008c0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:426 #4 0x00007f2022dcb012 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f2022dcb267 in QEventLoop::exec (this=0x7f200b3c4e00, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f2022ccb547 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501 #7 0x00007f20219e5119 in ?? () from /usr/lib64/libkimap.so.4 #8 0x00007f2022cce56b in QThreadPrivate::start (arg=0x893020) at thread/qthread_unix.cpp:298 #9 0x00007f201ec35f05 in start_thread () from /lib64/libpthread.so.0 #10 0x00007f201f38310d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f2023975760 (LWP 14884)): [KCrash Handler] #6 0x00007f2021a02348 in KIMAP::ExpungeJob::handleResponse(KIMAP::Message const&) () from /usr/lib64/libkimap.so.4 #7 0x00007f2021a02ad5 in KIMAP::SessionPrivate::responseReceived(KIMAP::Message const&) () from /usr/lib64/libkimap.so.4 #8 0x00007f2022de52b6 in QObject::event (this=0x88b610, e=<optimized out>) at kernel/qobject.cpp:1204 #9 0x00007f20221510d4 in notify_helper (e=0x7f200000b6f0, receiver=0x88b610, this=0x6ab270) at kernel/qapplication.cpp:4554 #10 QApplicationPrivate::notify_helper (this=0x6ab270, receiver=0x88b610, e=0x7f200000b6f0) at kernel/qapplication.cpp:4526 #11 0x00007f2022155f53 in QApplication::notify (this=0x7fff77687c10, receiver=0x88b610, e=0x7f200000b6f0) at kernel/qapplication.cpp:4415 #12 0x00007f202027f8f6 in KApplication::notify (this=0x7fff77687c10, receiver=0x88b610, event=0x7f200000b6f0) at /usr/src/debug/kdelibs-4.8.3/kdeui/kernel/kapplication.cpp:311 #13 0x00007f2022dcc22c in QCoreApplication::notifyInternal (this=0x7fff77687c10, receiver=0x88b610, event=0x7f200000b6f0) at kernel/qcoreapplication.cpp:876 #14 0x00007f2022dcfaca in sendEvent (event=0x7f200000b6f0, receiver=0x88b610) at kernel/qcoreapplication.h:231 #15 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x687920) at kernel/qcoreapplication.cpp:1500 #16 0x00007f2022dfae53 in sendPostedEvents () at kernel/qcoreapplication.h:236 #17 postEventSourceDispatch (s=0x6ad970) at kernel/qeventdispatcher_glib.cpp:279 #18 0x00007f201dcca58d in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #19 0x00007f201dccad88 in ?? () from /usr/lib64/libglib-2.0.so.0 #20 0x00007f201dccaf59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #21 0x00007f2022dfb27f in QEventDispatcherGlib::processEvents (this=0x6871e0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424 #22 0x00007f20221f476e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #23 0x00007f2022dcb012 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #24 0x00007f2022dcb267 in QEventLoop::exec (this=0x7fff77687b90, flags=...) at kernel/qeventloop.cpp:204 #25 0x00007f2022dcfdc5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148 #26 0x00007f2023437107 in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib64/libakonadi-kde.so.4 #27 0x000000000041bea6 in int Akonadi::ResourceBase::init<ImapResource>(int, char**) () #28 0x00007f201f2c923d in __libc_start_main () from /lib64/libc.so.6 #29 0x0000000000416885 in _start () Possible duplicates by query: bug 242698. Reported using DrKonqi
*** Bug 315765 has been marked as a duplicate of this bug. ***
The IMAP resource has a new maintainer, reassigning to him.
Crash backtraces of pre 4.11.3 versions are no longer useful. Please reopen if you can reproduce the issue with >= 4.11.3.