Bug 334098

Hello,

I get a segfault on my system with akonadi_imap_resource. I do not remember 
that I did anything particular change in akonadi, kmail, or my IMAP server, 
recently. I have not yet tried to setup a new imap account.

I would be happy to provide debug information on this issue, if it helps to 
make akonadi more robust, otherwise I just try to setup a new imap account.

I developer information I get in the KDE Crash Handler (do I need to install 
additional -dbg packages or run with KDE_DEBUG?):

Application: bokomoko of type IMAP E-Mail Server (akonadi_imap_resource), 
signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-
gnu/i686/cmov/libthread_db.so.1".
[Current thread is 1 (Thread 0xb49da740 (LWP 16105))]

Thread 2 (Thread 0xb1c5ab40 (LWP 16903)):
#0  g_mutex_get_impl (mutex=0xb13004e0) at 
/build/glib2.0-54cgmj/glib2.0-2.40.0/./glib/gthread-posix.c:119
#1  0xb54dd558 in g_mutex_unlock (mutex=mutex@entry=0xb13004e0) at 
/build/glib2.0-54cgmj/glib2.0-2.40.0/./glib/gthread-posix.c:228
#2  0xb5497eef in g_main_context_check (context=context@entry=0xb13004e0, 
max_priority=2147483647, fds=fds@entry=0xb102dce0, n_fds=n_fds@entry=1) at 
/build/glib2.0-54cgmj/glib2.0-2.40.0/./glib/gmain.c:3642
#3  0xb54984aa in g_main_context_iterate (context=context@entry=0xb13004e0, 
block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at 
/build/glib2.0-54cgmj/glib2.0-2.40.0/./glib/gmain.c:3731
#4  0xb5498658 in g_main_context_iteration (context=0xb13004e0, may_block=1) 
at /build/glib2.0-54cgmj/glib2.0-2.40.0/./glib/gmain.c:3795
#5  0xb733777f in QEventDispatcherGlib::processEvents (this=0xb1300468, 
flags=...) at kernel/qeventdispatcher_glib.cpp:427
#6  0xb7306503 in QEventLoop::processEvents (this=this@entry=0xb1c5a288, 
flags=...) at kernel/qeventloop.cpp:149
#7  0xb7306829 in QEventLoop::exec (this=this@entry=0xb1c5a288, flags=...) at 
kernel/qeventloop.cpp:204
#8  0xb71f241d in QThread::exec (this=this@entry=0xa0104d8) at 
thread/qthread.cpp:537
#9  0xb71f256b in QThread::run (this=0xa0104d8) at thread/qthread.cpp:604
#10 0xb71f4daf in QThreadPrivate::start (arg=0xa0104d8) at 
thread/qthread_unix.cpp:349
#11 0xb55cded9 in start_thread (arg=0xb1c5ab40) at pthread_create.c:312
#12 0xb577726e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129

Thread 1 (Thread 0xb49da740 (LWP 16105)):
[KCrash Handler]
#7  0x0808d59e in ?? ()
#8  0x0808dbd3 in ?? ()
#9  0xb731cd55 in QMetaObject::activate (sender=sender@entry=0x9fd5f00, 
m=m@entry=0xb5bf44ac <KJob::staticMetaObject>, 
local_signal_index=local_signal_index@entry=3, argv=argv@entry=0xbfd67a28) at 
kernel/qobject.cpp:3539
#10 0xb5a4f675 in KJob::result (this=this@entry=0x9fd5f00, 
_t1=_t1@entry=0x9fd5f00) at ./kjob.moc:207
#11 0xb5a4f6c2 in KJob::emitResult (this=0x9fd5f00) at 
../../kdecore/jobs/kjob.cpp:318
#12 0xb653c42e in KIMAP::Job::handleErrorReplies(KIMAP::Message const&) () 
from /usr/lib/libkimap.so.4
#13 0xb6561989 in KIMAP::SearchJob::handleResponse(KIMAP::Message const&) () 
from /usr/lib/libkimap.so.4
#14 0xb65552f6 in KIMAP::SessionPrivate::responseReceived(KIMAP::Message 
const&) () from /usr/lib/libkimap.so.4
#15 0xb6557d6b in ?? () from /usr/lib/libkimap.so.4
#16 0xb73194ea in QMetaCallEvent::placeMetaCall (this=0xb1040d30, 
object=0xa066308) at kernel/qobject.cpp:524
#17 0xb73213bb in QObject::event (this=0xa066308, e=0xb1040d30) at 
kernel/qobject.cpp:1194
#18 0xb68128a4 in QApplicationPrivate::notify_helper (this=0x9ed8b40, 
receiver=0xa066308, e=0xb1040d30) at kernel/qapplication.cpp:4567
#19 0xb68193a3 in QApplication::notify (this=0xbfd68274, 
receiver=receiver@entry=0xa066308, e=e@entry=0xb1040d30) at 
kernel/qapplication.cpp:4353
#20 0xb5de7074 in KApplication::notify (this=0xbfd68274, receiver=0xa066308, 
event=0xb1040d30) at ../../kdeui/kernel/kapplication.cpp:311
#21 0xb7307b4a in QCoreApplication::notifyInternal (this=0xbfd68274, 
receiver=receiver@entry=0xa066308, event=event@entry=0xb1040d30) at 
kernel/qcoreapplication.cpp:953
#22 0xb730b405 in sendEvent (event=0xb1040d30, receiver=0xa066308) at 
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#23 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, 
event_type=event_type@entry=0, data=0x9ea3280) at 
kernel/qcoreapplication.cpp:1577
#24 0xb730b92c in QCoreApplication::sendPostedEvents 
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at 
kernel/qcoreapplication.cpp:1470
#25 0xb7337f8e in sendPostedEvents () at 
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#26 postEventSourceDispatch (s=s@entry=0x9ec5330) at 
kernel/qeventdispatcher_glib.cpp:280
#27 0xb5498313 in g_main_dispatch (context=0x9ed8c50, context@entry=0x9ec5330) 
at /build/glib2.0-54cgmj/glib2.0-2.40.0/./glib/gmain.c:3064
#28 g_main_context_dispatch (context=context@entry=0x9ed8c50) at 
/build/glib2.0-54cgmj/glib2.0-2.40.0/./glib/gmain.c:3663
#29 0xb5498598 in g_main_context_iterate (context=context@entry=0x9ed8c50, 
block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at 
/build/glib2.0-54cgmj/glib2.0-2.40.0/./glib/gmain.c:3734
#30 0xb5498658 in g_main_context_iteration (context=0x9ed8c50, may_block=1) at 
/build/glib2.0-54cgmj/glib2.0-2.40.0/./glib/gmain.c:3795
#31 0xb733775f in QEventDispatcherGlib::processEvents 
(this=this@entry=0x9ea3dc8, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#32 0xb68c3dde in QGuiEventDispatcherGlib::processEvents (this=0x9ea3dc8, 
flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#33 0xb7306503 in QEventLoop::processEvents (this=this@entry=0xbfd681e8, 
flags=...) at kernel/qeventloop.cpp:149
#34 0xb7306829 in QEventLoop::exec (this=this@entry=0xbfd681e8, flags=...) at 
kernel/qeventloop.cpp:204
#35 0xb730c61e in QCoreApplication::exec () at 
kernel/qcoreapplication.cpp:1225
#36 0xb6810d34 in QApplication::exec () at kernel/qapplication.cpp:3828
#37 0xb763f158 in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from 
/usr/lib/libakonadi-kde.so.4
#38 0x0806347d in _start ()

Thanks,
Rainer

Reproducible: Always

Steps to Reproduce:
Happens right after login, no further action needed.




The problem depends on the user configuration, i.e. I see it right now only for one user, for another user I do not see the crash. Even if both users use the same server (not same mail account on the server).