Bug 300375

Summary: KMail sometimes gets into a somehow "disconnected" state
Product: [Frameworks and Libraries] Akonadi Reporter: Sunito <complete28>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: crash CC: complete28
Priority: NOR    
Version: 4.8   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Sunito 2012-05-21 04:53:08 UTC
Application: kmail (4.8.2)
KDE Platform Version: 4.8.2 (4.8.2)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-24-generic x86_64
Distribution: Ubuntu 12.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
This time I tried to overcome this "disconnected" state be 
restarting Akonadi. Although this resulted in this crash,
for me it was much better, because my mail had been put in the
outbox-folder, so I was able to send it after restarting KMail.

- Unusual behavior I noticed:
The state that I call "disconnected" here.
I have observed this state about 10 times now, but I'm still
unable to tell any condition that would be connected with 
KMail getting into the state.
It has two main symptoms:
* The annoying symptom is, that when I press the "send" button on a
newly written mail, KMail will not send the mail but only grey it out.
If I try to close the window, I will be asked if I want to abandon the
mail, if I refuse, it will continue to hang.
* KMail won't display any mail content, hanging with
"fetching folder content, please wait" (exact message, in 
German: "Abholen des Ordnerinhalts Bitte warten ...")

The crash can be reproduced some of the time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6e2e5587c0 (LWP 8921))]

Thread 3 (Thread 0x7f6e0bdc5700 (LWP 9053)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f6e20852dec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f6e20852f19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f6e29384e9a in start_thread (arg=0x7f6e0bdc5700) at pthread_create.c:308
#4  0x00007f6e2b8b54bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f6e0b4bc700 (LWP 9054)):
#0  0x00007f6e2b8a9b03 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f6e2415eff6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f6e2415f124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f6e2c240426 in QEventDispatcherGlib::processEvents (this=0x7f6e040008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f6e2c20fc82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f6e2c20fed7 in QEventLoop::exec (this=0x7f6e0b4bbdc0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f6e2c10efa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007f6e2c111fcb in QThreadPrivate::start (arg=0x217c8a0) at thread/qthread_unix.cpp:298
#8  0x00007f6e29384e9a in start_thread (arg=0x7f6e0b4bc700) at pthread_create.c:308
#9  0x00007f6e2b8b54bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f6e2e5587c0 (LWP 8921)):
[KCrash Handler]
#6  QHash<long long, QHashDummyValue>::duplicateNode (node=<optimized out>, newNode=0x35eb130) at ./collectionfetchjob.moc:110
#7  0x00007f6e2c12dc27 in QHashData::detach_helper2 (this=0x247c7c0, node_duplicate=0x7f6e28456900 <QHash<long long, QHashDummyValue>::duplicateNode(QHashData::Node*, void*)>, node_delete=0x7f6e28440940 <QHash<long long, QHashDummyValue>::deleteNode2(QHashData::Node*)>, nodeSize=<optimized out>, nodeAlign=8) at tools/qhash.cpp:239
#8  0x00007f6e284a6b62 in QHash<long long, QHashDummyValue>::detach_helper (this=0x224a570) at /usr/include/qt4/QtCore/qhash.h:584
#9  0x00007f6e284a6bcf in detach (this=0x224a570) at /usr/include/qt4/QtCore/qhash.h:303
#10 QHash<long long, QHashDummyValue>::remove (this=0x224a570, akey=<optimized out>) at /usr/include/qt4/QtCore/qhash.h:788
#11 0x00007f6e284a03ca in remove (value=@0x7fffe7f32650: 573, this=0x224a570) at /usr/include/qt4/QtCore/qset.h:89
#12 Akonadi::EntityTreeModelPrivate::fetchJobDone (this=0x224a530, job=0x1df8320) at ../../akonadi/entitytreemodel_p.cpp:1210
#13 0x00007f6e2c225281 in QMetaObject::activate (sender=0x1df8320, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffe7f327c0) at kernel/qobject.cpp:3547
#14 0x00007f6e2d996822 in KJob::result (this=<optimized out>, _t1=0x1df8320) at ./kjob.moc:208
#15 0x00007f6e2d996860 in KJob::emitResult (this=0x1df8320) at ../../kdecore/jobs/kjob.cpp:318
#16 0x00007f6e284d86d0 in Akonadi::JobPrivate::handleResponse (this=<optimized out>, tag=..., data=...) at ../../akonadi/job.cpp:66
#17 0x00007f6e2850e566 in Akonadi::SessionPrivate::dataReceived (this=0x239f390) at ../../akonadi/session.cpp:218
#18 0x00007f6e2c225281 in QMetaObject::activate (sender=0x2596ff0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#19 0x00007f6e2c225281 in QMetaObject::activate (sender=0x24f1398, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#20 0x00007f6e2a8bc68f in QAbstractSocketPrivate::canReadNotification (this=0x24f0f30) at socket/qabstractsocket.cpp:654
#21 0x00007f6e2a8c4201 in event (this=<optimized out>, e=<optimized out>) at socket/qnativesocketengine.cpp:1151
#22 QReadNotifier::event (this=<optimized out>, e=<optimized out>) at socket/qnativesocketengine.cpp:1148
#23 0x00007f6e2c733894 in notify_helper (e=0x7fffe7f33140, receiver=0x284dbd0, this=0x176e500) at kernel/qapplication.cpp:4559
#24 QApplicationPrivate::notify_helper (this=0x176e500, receiver=0x284dbd0, e=0x7fffe7f33140) at kernel/qapplication.cpp:4531
#25 0x00007f6e2c738713 in QApplication::notify (this=0x7fffe7f33470, receiver=0x284dbd0, e=0x7fffe7f33140) at kernel/qapplication.cpp:4420
#26 0x00007f6e2df6cb46 in KApplication::notify (this=0x7fffe7f33470, receiver=0x284dbd0, event=0x7fffe7f33140) at ../../kdeui/kernel/kapplication.cpp:311
#27 0x00007f6e2c210e9c in QCoreApplication::notifyInternal (this=0x7fffe7f33470, receiver=0x284dbd0, event=0x7fffe7f33140) at kernel/qcoreapplication.cpp:876
#28 0x00007f6e2c23fa97 in sendEvent (event=0x7fffe7f33140, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#29 socketNotifierSourceDispatch (source=0x1777d30) at kernel/qeventdispatcher_glib.cpp:110
#30 0x00007f6e2415ec9a in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x00007f6e2415f060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x00007f6e2415f124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#33 0x00007f6e2c2403bf in QEventDispatcherGlib::processEvents (this=0x171ab00, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#34 0x00007f6e2c7dbd5e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#35 0x00007f6e2c20fc82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#36 0x00007f6e2c20fed7 in QEventLoop::exec (this=0x7fffe7f33350, flags=...) at kernel/qeventloop.cpp:204
#37 0x00007f6e2c214f67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#38 0x0000000000402bd3 in main (argc=<optimized out>, argv=<optimized out>) at ../../kmail/main.cpp:145

Possible duplicates by query: bug 294028, bug 283768, bug 280630.

Reported using DrKonqi
Comment 1 Denis Kurz 2016-09-24 20:42:42 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:47:37 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.