Bug 350831 - akonadi crashing upon accessing IMAP server
Summary: akonadi crashing upon accessing IMAP server
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 1.13.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
Keywords: drkonqi
Depends on:
Reported: 2015-07-31 18:58 UTC by Friedemann Schorer
Modified: 2018-02-01 09:50 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Friedemann Schorer 2015-07-31 18:58:41 UTC
Application: akonadi_kolab_resource (4.14)
KDE Platform Version: 4.14.8
Qt Version: 4.8.6
Operating System: Linux 3.19.0-25-generic x86_64
Distribution: Ubuntu 15.04

-- Information about the crash:
- What I was doing when the application crashed:
started Kontact, all accounts configured a while ago

I'm having troubles with my LAN, so I had to set the domain I use in /etc/hosts manually, because my FritzBox router won't let access me the DynDNS domain from within the LAN (works fine from outside)
After restarting the computer completely I tried to open my mails but akonadi keeps crashing (akonadictl restart didn't resolve the problem).

The crash can be reproduced every time.

-- Backtrace:
Application: IMAP @ schorers.org of type Kolab Groupware Server (akonadi_kolab_resource), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5a439ef7c0 (LWP 5292))]

Thread 3 (Thread 0x7f5a296bb700 (LWP 5379)):
#0  0x00007f5a3e81f8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f5a3d78debc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f5a3d78dfcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f5a4301587e in QEventDispatcherGlib::processEvents (this=0x7f5a240008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x00007f5a42fe4d21 in QEventLoop::processEvents (this=this@entry=0x7f5a296bae10, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f5a42fe5085 in QEventLoop::exec (this=this@entry=0x7f5a296bae10, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f5a42ed8e89 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:538
#7  0x00007f5a42edb6ff in QThreadPrivate::start (arg=0x20600b0) at thread/qthread_unix.cpp:349
#8  0x00007f5a3de796aa in start_thread (arg=0x7f5a296bb700) at pthread_create.c:333
#9  0x00007f5a3e82aeed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f5a28eba700 (LWP 5381)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x00007f5a42edbc34 in wait (time=30000, this=0x7f5a24012040) at thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=this@entry=0x7f5a24011e60, mutex=mutex@entry=0x7f5a24011c78, time=30000) at thread/qwaitcondition_unix.cpp:158
#3  0x00007f5a42ecec6d in QThreadPoolThread::run (this=0x7f5a24011e50) at concurrent/qthreadpool.cpp:142
#4  0x00007f5a42edb6ff in QThreadPrivate::start (arg=0x7f5a24011e50) at thread/qthread_unix.cpp:349
#5  0x00007f5a3de796aa in start_thread (arg=0x7f5a28eba700) at pthread_create.c:333
#6  0x00007f5a3e82aeed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f5a439ef7c0 (LWP 5292)):
[KCrash Handler]
#6  0x00007f5a3e759267 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
#7  0x00007f5a3e75aeca in __GI_abort () at abort.c:89
#8  0x00007f5a3ed6506d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007f5a3ed62ee6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007f5a3ed62f31 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x00007f5a3ed63199 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x00007f5a42fe528b in QEventLoop::exec (this=this@entry=0x7ffe582d97e0, flags=...) at kernel/qeventloop.cpp:218
#13 0x00007f5a42feab09 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1227
#14 0x00007f5a4232bc1c in QApplication::exec () at kernel/qapplication.cpp:3828
#15 0x00007f5a434dad7c in Akonadi::ResourceBase::init (r=r@entry=0x1fe7a60) at ../../akonadi/resourcebase.cpp:583
#16 0x0000000000430dbe in Akonadi::ResourceBase::init<KolabResource> (argc=<optimized out>, argv=<optimized out>) at /usr/include/akonadi/resourcebase.h:193
#17 0x00007f5a3e744a40 in __libc_start_main (main=0x41a510 <main(int, char**)>, argc=3, argv=0x7ffe582d9988, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe582d9978) at libc-start.c:289
#18 0x000000000041aa59 in _start ()

Possible duplicates by query: bug 350759, bug 350726, bug 350334, bug 350209, bug 350208.

Reported using DrKonqi
Comment 1 Friedemann Schorer 2015-07-31 21:32:20 UTC
I issued 'akonadictl restart' on the command line, afterwards I got this multiple times:

KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
KCrash: Connect sock_file=/home/frschorer/.kde/socket-tpx220/kdeinit4__0
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "akonadi_kolab_resource_0_4276_hLdmxg" now serving: () 
QSocketNotifier: Invalid socket 13 and type 'Read', disabling...
Unable to start Dr. Konqi
Not forwarding the crash to Apport.
ProcessControl: Application '/usr/bin/akonadi_kolab_resource' returned with exit code 255 (Unknown error)
Database "akonadi" opened using driver "QMYSQL" 
QDBusObjectPath Akonadi::Server::NotificationManager::subscribeV2(const QString&, bool) Akonadi::Server::NotificationManager(0xa902a0) "akonadi_kolab_resource_0_4284_2XbDoE" true 
QDBusObjectPath Akonadi::Server::NotificationManager::subscribeV3(const QString&, bool, bool) Akonadi::Server::NotificationManager(0xa902a0) "akonadi_kolab_resource_0_4284_2XbDoE" true false 
SearchManager::registerInstance( "akonadi_kolab_resource_0" ) 
Registering search instance  "akonadi_kolab_resource_0" 
akonadi_kolab_resource_0(4284)/libakonadi Akonadi::EntityListCache<T, FetchJob, FetchScope_>::processResult: "Item query returned empty result set" 
Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

terminate called after throwing an instance of 'Akonadi::PayloadException'
  what():  Akonadi::PayloadException: No payload set
KCrash: Application 'akonadi_kolab_resource' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
Unregistering search instance "akonadi_kolab_resource_0" 
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "akonadi_kolab_resource_0_4284_2XbDoE" now serving: () 
KCrash: Connect sock_file=/home/frschorer/.kde/socket-tpx220/kdeinit4__0
Lost connection to resource "org.freedesktop.Akonadi.Resource.akonadi_kolab_resource_0" , discarding cached interface 

This appears every time I close the error message which states that the IMAP handler has crashed.
Comment 2 Friedemann Schorer 2015-07-31 21:34:43 UTC
Using kubuntu backports ppa additionally to stock Ubuntu repositories
Comment 3 Friedemann Schorer 2015-07-31 21:38:24 UTC
Uhh, my brain hurts...

Forgot to mention: 
my computer now resolves the domain correctly, i.e. nslookup returns the LAN-IP of my server, all relevant ports do respond. So I doubt it's a server issue.
The server runs an instance of Kolab 3.4, using Courier and Postfix
Comment 4 Denis Kurz 2017-06-23 20:17:14 UTC
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.
Comment 5 Denis Kurz 2018-02-01 09:50:06 UTC
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.