akonadi_imap_resource is reported by akonadictl as crashing after an IMAP password is provided. The password should be obtained from the wallet, but a password dialog appears instead. After akonadi is started, the IMAP password dialog appears 3 times, before akonadictl reports akonadi_imap_resource has failed too often and won't be restarted. If the IMAP password dialog is cancelled, when kmail is started the IMAP password dialog re-appears and when the password is provided a backtrace appears in akonadictl. 'valgrind akonadi_imap_resource' reports: ==6517== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) The fault has begun since upgrading from 16.12.3 to 17.04.0 (the issue persists in 17.04.1), though I'm not certain whether the fault occurred immediately after the upgrade.
Created attachment 105513 [details] akonadictl --verbose start
Created attachment 105514 [details] kmail launch (akonadictl --verbose)
Created attachment 105515 [details] kmail launch (konsole)
Created attachment 105516 [details] akonadi_imap_resource dialog (akonadictl --verbose)
Created attachment 105517 [details] agent_config_akonadi_imap_resource_0
Created attachment 105518 [details] akonadi_imap_resource_0rc
Having re-installed the full kontact/kmail/korganizer suite to 16.12.3, kmail successfully started, but akonadi_imap_resource prompted for a password, following which a successful authentication and download was achieved. (does this mean 17.04.[01] corrupted the kwallet entries?) Full re-install:- gentoo emerge =kontact-16.12.3 =korganizer-16.12.3 =kmail-16.12.3 =kmail-account-wizard-16.12.3 =kldap-16.12.3 =eventviews-16.12.3 =kcalcore-16.12.3 =akonadi-contacts-16.12.3 =kimap-16.12.3 =kmbox-16.12.3 =akonadi-search-16.12.3 =akonadi-calendar-16.12.3 =kdepim-apps-libs-16.12.3 =kdepim-runtime-16.12.3 =messagelib-16.12.3 =libkdepim-16.12.3 =eventviews-16.12.3 =calendarsupport-16.12.3 =pimcommon-16.12.3 =incidenceeditor-16.12.3 =libksieve-16.12.3 =mailcommon-16.12.3 =libgravatar-16.12.3 =kalarmcal-16.12.3 =kcontacts-16.12.3 =kontactinterface-16.12.3 =kpimtextedit-16.12.3 =grantleetheme-16.12.3 =kcalcore-16.12.3 =kidentitymanagement-16.12.3 =kcalutils-16.12.3 =libktnef-16.12.3 =libkleo-16.12.3-r1
Created attachment 105571 [details] akonadictl --verbose start (16.12.3)
Created attachment 105572 [details] akonadictl --verbose fsck (16.12.3)
Created attachment 105573 [details] kmail launch (16.12.3 - konsole)
Created attachment 105574 [details] akonadi_imap_resource dialog (16.12.3 - akonadictl --verbose)
Any chance to get a crash backtrace from DrKonqi?
I am seeing something similar starting today with KDE neon. Backtrace: Reading symbols from /usr/bin/akonadi_imap_resource...Reading symbols from /usr/lib/debug/.build-id/f0/a1a2580cdb0c1ad082f8751d53f1d876c2d7b1.debug...done. done. warning: core file may not match specified executable file. [New LWP 18316] [New LWP 18319] [New LWP 18322] [New LWP 18325] [New LWP 18344] [New LWP 18326] [New LWP 18321] [New LWP 18324] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_6'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0000000000463eb9 in RetrieveItemsTask::listFlagsForImapSet (this=this@entry=0x234b9c0, set=...) at /workspace/build/resources/imap/retrieveitemstask.cpp:597 597 /workspace/build/resources/imap/retrieveitemstask.cpp: No such file or directory. [Current thread is 1 (Thread 0x7f035df81980 (LWP 18316))] (gdb) bt #0 0x0000000000463eb9 in RetrieveItemsTask::listFlagsForImapSet (this=this@entry=0x234b9c0, set=...) at /workspace/build/resources/imap/retrieveitemstask.cpp:597 #1 0x00000000004642a4 in RetrieveItemsTask::onRetrievalDone (this=0x234b9c0, job=0x2342270) at /workspace/build/resources/imap/retrieveitemstask.cpp:584 #2 0x00007f037c22e1f6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x00007f037d3dd212 in KJob::result(KJob*, KJob::QPrivateSignal) () from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #4 0x00007f037d3deb51 in KJob::finishJob(bool) () from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #5 0x000000000048f7bb in BatchFetcher::onHeadersFetchDone (this=0x2342270, job=0x2348810) at /workspace/build/resources/imap/batchfetcher.cpp:226 #6 0x00007f037c22e1f6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x00007f037d3dd212 in KJob::result(KJob*, KJob::QPrivateSignal) () from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #8 0x00007f037d3deb51 in KJob::finishJob(bool) () from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #9 0x00007f037ff22945 in KIMAP::Job::handleErrorReplies(KIMAP::Message const&) () from /usr/lib/x86_64-linux-gnu/libKF5IMAP.so.5 #10 0x00007f037fef8719 in KIMAP::FetchJob::handleResponse(KIMAP::Message const&) () from /usr/lib/x86_64-linux-gnu/libKF5IMAP.so.5 #11 0x00007f037ff3f4c0 in KIMAP::SessionPrivate::responseReceived(KIMAP::Message const&) () from /usr/lib/x86_64-linux-gnu/libKF5IMAP.so.5 #12 0x00007f037c22ed99 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x00007f037cc4fecc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x00007f037cc578c6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x00007f037c2030c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x00007f037c20578b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x00007f037c256333 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x00007f03764e2197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x00007f03764e23f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x00007f03764e249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x00007f037c25673f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x00007f037c2010ba in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x00007f037c2096cc in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00007f037ec5207e in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib/x86_64-linux-gnu/libKF5AkonadiAgentBase.so.5 #25 0x0000000000420555 in Akonadi::ResourceBase::init<ImapResource> (argc=3, argv=<optimized out>) at /usr/include/KF5/AkonadiAgentBase/resourcebase.h:196 #26 0x00007f037b646830 in __libc_start_main (main=0x420390 <main(int, char**)>, argc=3, argv=0x7fffd1db9038, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffd1db9028) at ../csu/libc-start.c:291 #27 0x00000000004203f9 in _start ()
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!