Bug 329505

Summary:	Kontact crashed when I was interacting with Summary
Product:	[Applications] kontact	Reporter:	Fiorenzo <fiorenzo.desantis>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	fiorenzo.desantis
Priority:	NOR	Keywords:	drkonqi
Version:	4.11.4
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Fiorenzo 2014-01-01 19:28:16 UTC

Application: kontact (4.11.4)
KDE Platform Version: 4.11.4
Qt Version: 4.8.5
Operating System: Linux 3.12.5-302.fc20.x86_64 x86_64
Distribution: "Fedora release 20 (Heisenbug)"

-- Information about the crash:
- What I was doing when the application crashed:

I just opened Kontact and from Summary I clicked on the link INBOX to go to my gmail imap inbox to check new emails

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
81	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f38111aa8c0 (LWP 4986))]

Thread 3 (Thread 0x7f37c6000700 (LWP 4987)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x0000003b93cbd23d in JSC::BlockAllocator::blockFreeingThreadMain() () from /lib64/libQtWebKit.so.4
#2  0x0000003b93fafc56 in WTF::wtfThreadEntryPoint(void*) () from /lib64/libQtWebKit.so.4
#3  0x0000003e1b807f33 in start_thread (arg=0x7f37c6000700) at pthread_create.c:309
#4  0x0000003e1b0f4ead in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f37b7fff700 (LWP 5000)):
#0  0x0000003e1b0eaa8d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x0000003fbe0495b4 in g_main_context_iterate.isra.24 () from /lib64/libglib-2.0.so.0
#2  0x0000003fbe0496dc in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#3  0x0000003a607b31a6 in QEventDispatcherGlib::processEvents (this=0x7f37ac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#4  0x0000003a6078312f in QEventLoop::processEvents (this=this@entry=0x7f37b7ffed10, flags=...) at kernel/qeventloop.cpp:149
#5  0x0000003a6078347d in QEventLoop::exec (this=this@entry=0x7f37b7ffed10, flags=...) at kernel/qeventloop.cpp:204
#6  0x0000003a60679bdf in QThread::exec (this=<optimized out>) at thread/qthread.cpp:536
#7  0x0000003a6067c3df in QThreadPrivate::start (arg=0x27b4830) at thread/qthread_unix.cpp:338
#8  0x0000003e1b807f33 in start_thread (arg=0x7f37b7fff700) at pthread_create.c:309
#9  0x0000003e1b0f4ead in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f38111aa8c0 (LWP 4986)):
[KCrash Handler]
#6  QApplication::notify (this=this@entry=0x7fff73a39060, receiver=receiver@entry=0x4bf4110, e=e@entry=0x7fff73a387f0) at kernel/qapplication.cpp:4089
#7  0x0000003b89e4a9ca in KApplication::notify (this=0x7fff73a39060, receiver=0x4bf4110, event=0x7fff73a387f0) at /usr/src/debug/kdelibs-4.11.4/kdeui/kernel/kapplication.cpp:311
#8  0x0000003a607845ed in QCoreApplication::notifyInternal (this=0x7fff73a39060, receiver=receiver@entry=0x4bf4110, event=event@entry=0x7fff73a387f0) at kernel/qcoreapplication.cpp:949
#9  0x0000003a61fd0017 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:231
#10 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x4bf4110, event=event@entry=0x7fff73a387f0, alienWidget=alienWidget@entry=0x4bf4110, nativeWidget=nativeWidget@entry=0x3303d90, buttonDown=buttonDown@entry=0x3a62ada278 <qt_button_down>, lastMouseReceiver=..., spontaneous=spontaneous@entry=true) at kernel/qapplication.cpp:3173
#11 0x0000003a620457cb in QETWidget::translateMouseEvent (this=this@entry=0x3303d90, event=event@entry=0x7fff73a38b60) at kernel/qapplication_x11.cpp:4538
#12 0x0000003a6204423c in QApplication::x11ProcessEvent (this=0x7fff73a39060, event=event@entry=0x7fff73a38b60) at kernel/qapplication_x11.cpp:3661
#13 0x0000003a6206bc34 in x11EventSourceDispatch (s=0x2455f70, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148
#14 0x0000003fbe0492a6 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#15 0x0000003fbe049628 in g_main_context_iterate.isra.24 () from /lib64/libglib-2.0.so.0
#16 0x0000003fbe0496dc in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#17 0x0000003a607b3185 in QEventDispatcherGlib::processEvents (this=0x244d790, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#18 0x0000003a6206bdb6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#19 0x0000003a6078312f in QEventLoop::processEvents (this=this@entry=0x7fff73a38f50, flags=...) at kernel/qeventloop.cpp:149
#20 0x0000003a6078347d in QEventLoop::exec (this=this@entry=0x7fff73a38f50, flags=...) at kernel/qeventloop.cpp:204
#21 0x0000003a607889bb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221
#22 0x00000000004037ea in main ()

Possible duplicates by query: bug 329504, bug 329496, bug 329492, bug 329480, bug 329474.

Reported using DrKonqi

Comment 1 Fiorenzo 2014-01-02 16:11:01 UTC

it has just happened again, when I clicked INBOX from Summary

the workaround seems to be to not use Summary at all

Comment 2 Fiorenzo 2014-01-04 10:13:29 UTC

it apparently happens only when you have more than one new email in your inbox

Comment 3 Denis Kurz 2016-09-24 19:25:56 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 4 Denis Kurz 2017-01-07 22:27:29 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.