Bug 336564

Summary: new IMAP account, crash on first sync
Product: [Frameworks and Libraries] Akonadi Reporter: Mathieu Jobin <opensource>
Component: IMAP resourceAssignee: Christian Mollekopf <chrigi_1>
Status: RESOLVED UNMAINTAINED    
Severity: crash CC: kdepim-bugs, vkrause
Priority: NOR Keywords: drkonqi
Version: 4.13   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Mathieu Jobin 2014-06-22 03:53:14 UTC
Application: akonadi_imap_resource (4.13)
KDE Platform Version: 4.13.1
Qt Version: 4.8.6
Operating System: Linux 3.13.0-24-generic x86_64
Distribution: Ubuntu 14.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:

created a new imap account. I should note that I have more 14 configured IMAP account
and being able to access my emails in KMail has become almost impossible... I'm only hoping and expecting kmail to backup my mail...
but it's unusable at the moment

anyhow, my 14th account just crashed with the attached stacktrace

I should also note, it's a brand new IMAP account, there should not be any mail or folder in that account expect for maybe 1 mail and default standard folders.

thanks

-- Backtrace:
Application: Mathieu Jobin.com(14) of type IMAP E-Mail Server (akonadi_imap_resource), signal: Bus error
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd8e4df77c0 (LWP 10652))]

Thread 2 (Thread 0x7fd8d084d700 (LWP 10657)):
#0  __GI___pthread_getspecific (key=3) at pthread_getspecific.c:31
#1  0x00007fd8df2bb3b0 in g_thread_self () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fd8df29509c in g_main_context_acquire () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fd8df295ea5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fd8df2960ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fd8e41c47be in QEventDispatcherGlib::processEvents (this=0x7fd8cc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0x00007fd8e41960af in QEventLoop::processEvents (this=this@entry=0x7fd8d084cde0, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007fd8e41963a5 in QEventLoop::exec (this=this@entry=0x7fd8d084cde0, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007fd8e4092c5f in QThread::exec (this=this@entry=0xf918c0) at thread/qthread.cpp:537
#9  0x00007fd8e4177823 in QInotifyFileSystemWatcherEngine::run (this=0xf918c0) at io/qfilesystemwatcher_inotify.cpp:265
#10 0x00007fd8e409532f in QThreadPrivate::start (arg=0xf918c0) at thread/qthread_unix.cpp:349
#11 0x00007fd8dfbbf182 in start_thread (arg=0x7fd8d084d700) at pthread_create.c:312
#12 0x00007fd8e07a530d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7fd8e4df77c0 (LWP 10652)):
[KCrash Handler]
#5  QMetaObject::invokeMethod (obj=0x3ff0000000000000, member=<optimized out>, type=Qt::AutoConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1166
#6  0x00007fd8e2de10f8 in ?? () from /usr/lib/libkimap.so.4
#7  0x00007fd8e41afc1e in QObject::event (this=0x1c742b0, e=<optimized out>) at kernel/qobject.cpp:1194
#8  0x00007fd8e3530e2c in QApplicationPrivate::notify_helper (this=this@entry=0xce19a0, receiver=receiver@entry=0x1c742b0, e=e@entry=0x7fd8c420dc90) at kernel/qapplication.cpp:4567
#9  0x00007fd8e35374a0 in QApplication::notify (this=0x7fff35638d10, receiver=0x1c742b0, e=0x7fd8c420dc90) at kernel/qapplication.cpp:4353
#10 0x00007fd8e166cd1a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#11 0x00007fd8e41974dd in QCoreApplication::notifyInternal (this=0x7fff35638d10, receiver=receiver@entry=0x1c742b0, event=event@entry=0x7fd8c420dc90) at kernel/qcoreapplication.cpp:953
#12 0x00007fd8e419ab3d in sendEvent (event=0x7fd8c420dc90, receiver=0x1c742b0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#13 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0xcb4220) at kernel/qcoreapplication.cpp:1577
#14 0x00007fd8e419afe3 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1470
#15 0x00007fd8e41c4f83 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#16 postEventSourceDispatch (s=0xcf5240) at kernel/qeventdispatcher_glib.cpp:287
#17 0x00007fd8df295e04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007fd8df296048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fd8df2960ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fd8e41c47a1 in QEventDispatcherGlib::processEvents (this=0xcb5700, flags=...) at kernel/qeventdispatcher_glib.cpp:434
#21 0x00007fd8e35d2bb6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#22 0x00007fd8e41960af in QEventLoop::processEvents (this=this@entry=0x7fff35638c80, flags=...) at kernel/qeventloop.cpp:149
#23 0x00007fd8e41963a5 in QEventLoop::exec (this=this@entry=0x7fff35638c80, flags=...) at kernel/qeventloop.cpp:204
#24 0x00007fd8e419bb79 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225
#25 0x00007fd8e48eb243 in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib/libakonadi-kde.so.4
#26 0x00000000004215c3 in _start ()

The reporter indicates this bug may be a duplicate of or related to bug 335776.

Possible duplicates by query: bug 336555, bug 336534, bug 336497, bug 336472, bug 336411.

Reported using DrKonqi
Comment 1 Denis Kurz 2016-09-24 20:30:57 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 21:44:17 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.