Bug 334929

Summary:	imap resource has a pending task and crashes repetitively
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Feth Arezki <feth>
Component:	IMAP resource	Assignee:	Christian Mollekopf <chrigi_1>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	kdepim-bugs, vkrause
Priority:	NOR	Keywords:	drkonqi
Version:	4.12
Target Milestone:	---
Platform:	Debian unstable
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Feth Arezki 2014-05-17 09:00:40 UTC

Application: akonadi_imap_resource (4.12)
KDE Platform Version: 4.12.4
Qt Version: 4.8.6
Operating System: Linux 3.14-1-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
I once asked for a few mails to be moved from an imap inbox to a subfolder (spams).
Now the imap resource always crashes and relaunches. Even after restarting my computer.
In akonadiconsole, it shows that the resource is busy (0%) moving the mails.
Canceling the move/going offline does not help. Even shutting down the network + restarting akonadi doesn't (it just triggers another drkonqui for that imap resource).

The crash can be reproduced every time.

-- Backtrace:
Application: la ressource « tuttu2 » de type  (akonadi_imap_resource), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f55ff727780 (LWP 4372))]

Thread 2 (Thread 0x7f55eb51b700 (LWP 4439)):
#0  0x00007f55fb0b38ed in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f55f9de5fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f55f9de60ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f55feb36676 in QEventDispatcherGlib::processEvents (this=0x7f55e40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#4  0x00007f55feb07fef in QEventLoop::processEvents (this=this@entry=0x7f55eb51ae60, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f55feb082e5 in QEventLoop::exec (this=this@entry=0x7f55eb51ae60, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f55fea04bef in QThread::exec (this=<optimized out>) at thread/qthread.cpp:538
#7  0x00007f55fea072bf in QThreadPrivate::start (arg=0x19e2470) at thread/qthread_unix.cpp:349
#8  0x00007f55fa70f062 in start_thread (arg=0x7f55eb51b700) at pthread_create.c:312
#9  0x00007f55fb0bebfd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f55ff727780 (LWP 4372)):
[KCrash Handler]
#6  0x00007f55fb00e3a9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7  0x00007f55fb0114c8 in __GI_abort () at abort.c:89
#8  0x00007f55fb5f9d55 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007f55fb5f7dd6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007f55fb5f7e21 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x00007f55fb5f8086 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x00007f55feb084d6 in QEventLoop::exec (this=this@entry=0x7fff39679be0, flags=...) at kernel/qeventloop.cpp:218
#13 0x00007f55feb0dab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225
#14 0x00007f55ff24af63 in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib/libakonadi-kde.so.4
#15 0x000000000041fab3 in _start ()

Possible duplicates by query: bug 334556, bug 334522, bug 334087, bug 333735, bug 333332.

Reported using DrKonqi

Comment 1 Feth Arezki 2014-05-17 09:21:29 UTC

Additional info. I start akonadiconsole :

% akonadiconsole 
QDBusObjectPath Akonadi::Server::NotificationManager::subscribeV2(const QString&, bool) Akonadi::Server::NotificationManager(0x19b8060) "akonadiconsole_12725_hwLvY3" true 
QDBusObjectPath Akonadi::Server::NotificationManager::subscribeV2(const QString&, bool) Akonadi::Server::NotificationManager(0x19b8060) "akonadiconsole_12725_ABR34W" true 
QDBusObjectPath Akonadi::Server::NotificationManager::subscribeV2(const QString&, bool) Akonadi::Server::NotificationManager(0x19b8060) "akonadiconsole_12725_h0fxo6" true 
QDBusObjectPath Akonadi::Server::NotificationManager::subscribeV2(const QString&, bool) Akonadi::Server::NotificationManager(0x19b8060) "akonadiconsole_12725_vLXRF1" true 
QDBusObjectPath Akonadi::Server::NotificationManager::subscribeV2(const QString&, bool) Akonadi::Server::NotificationManager(0x19b8060) "akonadiconsole_12725_hRqJ4A" true 
akonadiconsole(12725) KDirWatch::removeDir: doesn't know "/home/feth/.kde/share/apps/messageviewer/themes/" 
akonadiconsole(12725) KDirWatch::removeDir: doesn't know "/usr/share/kde4/apps/messageviewer/themes/" 
akonadiconsole(12725) MonitorItem::MonitorItem: "Invalid object path: /subscriber/plasma-desktop_3868_65T18D" 
Database "akonadi" opened using driver "QMYSQL" 
Database "akonadi" opened using driver "QMYSQL" 

tuttu2 is showing "Déplacement des éléments de «INBOX» vers «spam» (0%)"

the text console spits a lot of 

"Cannot connect to agent instance with identifier 'akonadi_imap_resource_11', error message: 'Could not get owner of name 'org.freedesktop.Akonadi.Resource.akonadi_imap_resource_11': no such name'"
"Cannot connect to agent instance with identifier 'akonadi_imap_resource_11', error message: 'Could not get owner of name 'org.freedesktop.Akonadi.Resource.akonadi_imap_resource_11': no such name'"

if I right click "abort activity", it says 

akonadiconsole(12725)/libakonadi Akonadi::AgentInstance::abortCurrentTask: Unable to obtain agent interface

Comment 2 Dominik Haumann 2014-06-07 13:17:06 UTC

Do you still have this issue? Could you try to update to KDE 4.13 ?

Comment 3 Feth Arezki 2014-06-18 19:53:46 UTC

(In reply to comment #2)
> Do you still have this issue? Could you try to update to KDE 4.13 ?

Now running 4.13.1. I believe I still have akonadi issues, but certainly this one vanished. Thanks !

Comment 4 Denis Kurz 2016-09-24 20:31:07 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 5 Denis Kurz 2017-01-07 22:48:18 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.