[Bug 275736] Sending mail hangs if KWallet has been closed and reopened by another application

[Matt Whitlock]

https://bugs.kde.org/show_bug.cgi?id=275736

--- Comment #9 from Matt Whitlock <kde at mattwhitlock.name> ---
I'm seeing this hang right now. I have a message sitting in my Outbox in KMail.
KMail is responsive. Akonadi is running. Akonadi Console says the "Mail
Dispatcher Agent" is "Ready to dispatch messages." I can click "Send Queued
Messages" in the File menu of KMail, and nothing happens. If I attach to the
akonadi_maildispatcher_agent process in gdb, I can see that it has one thread,
which is parked in its event loop, waiting for events to come in:

#0  0x00007ffe7e7c6078 in *__GI___poll (fds=0x1b75ad0, nfds=5, timeout=2390494)
at ../sysdeps/unix/sysv/linux/poll.c:83
#1  0x00007ffe7d036cf5 in g_main_context_poll (n_fds=5, fds=0x1b75ad0,
timeout=2390494, context=0x1aa0130, 
    priority=<optimized out>) at gmain.c:3440
#2  g_main_context_iterate (context=0x1aa0130, block=<optimized out>,
dispatch=1, self=<optimized out>) at gmain.c:3141
#3  0x00007ffe7d036e65 in g_main_context_iterate (dispatch=1, block=1,
context=0x1aa0130, self=<optimized out>)
    at gmain.c:3113
#4  g_main_context_iteration (context=0x1aa0130, may_block=1) at gmain.c:3207
#5  0x00007ffe815cee3f in QEventDispatcherGlib::processEvents (this=0x1a7a740,
flags=...)
    at kernel/qeventdispatcher_glib.cpp:424
#6  0x00007ffe7f22442e in QGuiEventDispatcherGlib::processEvents
(this=<optimized out>, flags=...)
    at kernel/qguieventdispatcher_glib.cpp:204
#7  0x00007ffe8159ea42 in QEventLoop::processEvents (this=<optimized out>,
flags=...) at kernel/qeventloop.cpp:149
#8  0x00007ffe8159ecf5 in QEventLoop::exec (this=0x7fffb9c72a00, flags=...) at
kernel/qeventloop.cpp:204
#9  0x00007ffe815a374b in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1187
#10 0x00007ffe81bda736 in Akonadi::AgentBase::init (r=0x1c80110)
    at
/var/tmp/portage/kde-base/kdepimlibs-4.8.4/work/kdepimlibs-4.8.4/akonadi/agentbase.cpp:564
#11 0x000000000040d590 in Akonadi::AgentBase::init<MailDispatcherAgent>
(argc=<optimized out>, argv=<optimized out>)
    at /usr/include/KDE/Akonadi/../../akonadi/agentbase.h:342
#12 0x00007ffe7e7064bd in __libc_start_main (main=0x40a130 <main(int, char**)>,
argc=3, ubp_av=0x7fffb9c72c88, 
    init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>,
stack_end=0x7fffb9c72c78) at libc-start.c:226
#13 0x000000000040a1f5 in _start ()

If I attach to the "kdeinit4: kwalletd" process, I can see that it, too, has
one thread, which is parked in its event loop:

#0  0x00007f542abda078 in *__GI___poll (fds=0x131be60, nfds=6, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:83
#1  0x00007f5427896cf5 in g_main_context_poll (n_fds=6, fds=0x131be60,
timeout=-1, context=0x119c210, 
    priority=<optimized out>) at gmain.c:3440
#2  g_main_context_iterate (context=0x119c210, block=<optimized out>,
dispatch=1, self=<optimized out>) at gmain.c:3141
#3  0x00007f5427896e65 in g_main_context_iterate (dispatch=1, block=1,
context=0x119c210, self=<optimized out>)
    at gmain.c:3113
#4  g_main_context_iteration (context=0x119c210, may_block=1) at gmain.c:3207
#5  0x00007f542c22de3f in QEventDispatcherGlib::processEvents (this=0x11a6950,
flags=...)
    at kernel/qeventdispatcher_glib.cpp:424
#6  0x00007f542b42242e in QGuiEventDispatcherGlib::processEvents
(this=<optimized out>, flags=...)
    at kernel/qguieventdispatcher_glib.cpp:204
#7  0x00007f542c1fda42 in QEventLoop::processEvents (this=<optimized out>,
flags=...) at kernel/qeventloop.cpp:149
#8  0x00007f542c1fdcf5 in QEventLoop::exec (this=0x7fff6b7fef90, flags=...) at
kernel/qeventloop.cpp:204
#9  0x00007f542c20274b in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1187
#10 0x00007f541a89505f in kdemain (argc=1, argv=0x114a660)
    at
/var/tmp/portage/kde-base/kwalletd-4.8.4/work/kwalletd-4.8.4/kwalletd/main.cpp:68
#11 0x0000000000409084 in launch (argc=<optimized out>, _name=0x1157658
"/usr/bin/kwalletd", args=<optimized out>, cwd=0x0, 
    envc=<optimized out>, envs=<optimized out>, reset_env=false, tty=0x0,
avoid_loops=false, 
    startup_id_str=0x1157685 "Crushinator;1343434237;514746;4479_TIME0")
    at
/var/tmp/portage/kde-base/kdelibs-4.8.4-r1/work/kdelibs-4.8.4/kinit/kinit.cpp:734
#12 0x000000000040a376 in handle_launcher_request (sock=7, who=<optimized out>)
    at
/var/tmp/portage/kde-base/kdelibs-4.8.4-r1/work/kdelibs-4.8.4/kinit/kinit.cpp:1226
#13 0x000000000040a8b3 in handle_requests (waitForPid=0)
    at
/var/tmp/portage/kde-base/kdelibs-4.8.4-r1/work/kdelibs-4.8.4/kinit/kinit.cpp:1419
#14 0x0000000000405a9e in main (argc=2, argv=0x7fff6b800040,
envp=0x7fff6b800310)
    at
/var/tmp/portage/kde-base/kdelibs-4.8.4-r1/work/kdelibs-4.8.4/kinit/kinit.cpp:1907

CPU usage is minimal. Perhaps it's a stand-off?

When I right-clicked on "Mail Dispatcher Agent" in the Akonadi Console and
chose "Restart Agent," it immediately sent the message that had been waiting in
my Outbox.

-- 
You are receiving this mail because:
You are the assignee for the bug.