[kontact] [Bug 288141] Kontact crash on exit

Hauke Laging hauke at laging.de
Sun Dec 21 03:00:42 GMT 2014


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

Hauke Laging <hauke at laging.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hauke at laging.de

--- Comment #32 from Hauke Laging <hauke at laging.de> ---
I have probably the same problem – for years now. kontact crashes when exiting
(probably due to kmail). This is annoying because the IMAP folder settings
(like when to check for new mail) are not saved. Open mail creating windows are
restored, though.

After my upgrade from openSUSE 13.1 to 13.2 kmail was completely broken so I
deleted the whole akonadi database and created the kmail IMAP accounts again.
To my surprise some of the other configuration (like the identities) was still
there. I am also surprised that kmail still crashes. So it seems not related to
the IMAP stuff. I must admit though that I didn't think of closing kmail before
adding the IMAP accounts just for crash testing.

This is the crash data I get:

Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd7128ae800 (LWP 3267))]

Thread 4 (Thread 0x7fd6f522b700 (LWP 3268)):
#0  0x00007fd709ec105f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x00007fd70d652686 in WTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib64/libQtWebKit.so.4
#2  0x00007fd70d6526b9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) ()
from /usr/lib64/libQtWebKit.so.4
#3  0x00007fd709ebd0a4 in start_thread () from /lib64/libpthread.so.0
#4  0x00007fd70fe307fd in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fd6b4910700 (LWP 3269)):
#0  0x00007fd709ec105f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x00007fd70d3c4e7d in JSC::BlockAllocator::blockFreeingThreadMain() () from
/usr/lib64/libQtWebKit.so.4
#2  0x00007fd70d67a1e6 in WTF::wtfThreadEntryPoint(void*) () from
/usr/lib64/libQtWebKit.so.4
#3  0x00007fd709ebd0a4 in start_thread () from /lib64/libpthread.so.0
#4  0x00007fd70fe307fd in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fd6a4a9d700 (LWP 3288)):
#0  0x00007fd70fe2449d in read () from /lib64/libc.so.6
#1  0x00007fd709932750 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007fd7098f1714 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x00007fd7098f1b7b in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x00007fd7098f1cec in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x00007fd7105ab0de in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib64/libQtCore.so.4
#6  0x00007fd71057ce6f in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/libQtCore.so.4
#7  0x00007fd71057d165 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/libQtCore.so.4
#8  0x00007fd71047a0bf in QThread::exec() () from /usr/lib64/libQtCore.so.4
#9  0x00007fd71047c79f in ?? () from /usr/lib64/libQtCore.so.4
#10 0x00007fd709ebd0a4 in start_thread () from /lib64/libpthread.so.0
#11 0x00007fd70fe307fd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fd7128ae800 (LWP 3267)):
[KCrash Handler]
#5  0x00007fd711a35bd0 in vtable for QPaintDevice () from
/usr/lib64/libQtGui.so.4
#6  0x000000000040382f in ?? ()
#7  0x00007fd70fd6cb05 in __libc_start_main () from /lib64/libc.so.6
#8  0x0000000000403c97 in _start ()

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


More information about the Kdepim-bugs mailing list