Application: kontact (4.10.1) KDE Platform Version: 4.10.1 "release 552" Qt Version: 4.8.4 Operating System: Linux 3.4.28-2.20-desktop x86_64 Distribution: "openSUSE 12.2 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Not easy to describe, first time this one appear. I've kontact with kmail, orgarnizer(3 timetables), akonaNotes, akregator has opened modules. I'm using 11 offline-imap accounts. I've disabled the auto retrieve every each time on all accounts. I was browsing my emails in differents folder, reading messages and then the crash appear. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0314e22780 (LWP 2756))] Thread 3 (Thread 0x7f02fc185700 (LWP 2759)): #0 0x00007f030cc318f4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f0311620437 in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x00007f0311620469 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x00007f030cc2de0e in start_thread () from /lib64/libpthread.so.0 #4 0x00007f03123822cd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f02fb884700 (LWP 2761)): #0 0x00007f031237a14f in poll () from /lib64/libc.so.6 #1 0x00007f030ba22684 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f030ba227a4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f03137ae166 in QEventDispatcherGlib::processEvents (this=0x7f02f40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x00007f031377e97f in QEventLoop::processEvents (this=this@entry=0x7f02fb883e00, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f031377ec08 in QEventLoop::exec (this=0x7f02fb883e00, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f03136810e0 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542 #7 0x00007f03136840bc in QThreadPrivate::start (arg=0x10a3520) at thread/qthread_unix.cpp:338 #8 0x00007f030cc2de0e in start_thread () from /lib64/libpthread.so.0 #9 0x00007f03123822cd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f0314e22780 (LWP 2756)): [KCrash Handler] #6 KMime::Types::Mailbox::hasName (this=this@entry=0xc1af840) at /usr/src/debug/kdepimlibs-4.10.1/kmime/kmime_header_parsing.cpp:173 #7 0x00007f0308ea5187 in KMime::Types::Mailbox::prettyAddress (this=0xc1af840, quoting=quoting@entry=KMime::Types::Mailbox::QuoteNever) at /usr/src/debug/kdepimlibs-4.10.1/kmime/kmime_header_parsing.cpp:183 #8 0x00007f0308ea533b in KMime::Types::Mailbox::prettyAddress (this=<optimized out>) at /usr/src/debug/kdepimlibs-4.10.1/kmime/kmime_header_parsing.cpp:178 #9 0x00007f0308eb7852 in KMime::Headers::Generics::AddressList::prettyAddresses (this=this@entry=0xc1af6c0) at /usr/src/debug/kdepimlibs-4.10.1/kmime/kmime_headers.cpp:631 #10 0x00007f0308eb797f in KMime::Headers::Generics::AddressList::asUnicodeString (this=0xc1af6c0) at /usr/src/debug/kdepimlibs-4.10.1/kmime/kmime_headers.cpp:570 #11 0x00007f02b240c926 in MessageList::StorageModel::initializeMessageItem (this=0x1708710, mi=0xc0f2980, row=22863, bUseReceiver=false) at /usr/src/debug/kdepim-4.10.1/messagelist/storagemodel.cpp:256 #12 0x00007f02b23c5d98 in MessageList::Core::ModelPrivate::viewItemJobStepInternalForJobPass1Fill (this=0x17537a0, job=0x6ed7e00, tStart=...) at /usr/src/debug/kdepim-4.10.1/messagelist/core/model.cpp:2730 #13 0x00007f02b23c86e5 in MessageList::Core::ModelPrivate::viewItemJobStepInternalForJob (this=this@entry=0x17537a0, job=job@entry=0x6ed7e00, tStart=...) at /usr/src/debug/kdepim-4.10.1/messagelist/core/model.cpp:3392 #14 0x00007f02b23c8c7f in MessageList::Core::ModelPrivate::viewItemJobStepInternal (this=this@entry=0x17537a0) at /usr/src/debug/kdepim-4.10.1/messagelist/core/model.cpp:3779 #15 0x00007f02b23c943b in MessageList::Core::ModelPrivate::viewItemJobStep (this=0x17537a0) at /usr/src/debug/kdepim-4.10.1/messagelist/core/model.cpp:3965 #16 0x00007f031379512f in QMetaObject::activate (sender=0x17537d8, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3548 #17 0x00007f031379443c in QObject::event (this=0x17537d8, e=<optimized out>) at kernel/qobject.cpp:1165 #18 0x00007f0312b2985c in QApplicationPrivate::notify_helper (this=this@entry=0x10a5860, receiver=receiver@entry=0x17537d8, e=e@entry=0x7fff9256b9b0) at kernel/qapplication.cpp:4562 #19 0x00007f0312b2dcda in QApplication::notify (this=0x7fff9256bdb0, receiver=0x17537d8, e=0x7fff9256b9b0) at kernel/qapplication.cpp:4423 #20 0x00007f03141e4f36 in KApplication::notify (this=0x7fff9256bdb0, receiver=0x17537d8, event=0x7fff9256b9b0) at /usr/src/debug/kdelibs-4.10.1/kdeui/kernel/kapplication.cpp:311 #21 0x00007f031377fc2e in QCoreApplication::notifyInternal (this=0x7fff9256bdb0, receiver=0x17537d8, event=0x7fff9256b9b0) at kernel/qcoreapplication.cpp:946 #22 0x00007f03137b09d1 in sendEvent (event=0x7fff9256b9b0, receiver=<optimized out>) at kernel/qcoreapplication.h:231 #23 QTimerInfoList::activateTimers (this=0x109c560) at kernel/qeventdispatcher_unix.cpp:637 #24 0x00007f03137adae4 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:186 #25 timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:180 #26 0x00007f030ba223b5 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #27 0x00007f030ba226e8 in ?? () from /usr/lib64/libglib-2.0.so.0 #28 0x00007f030ba227a4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #29 0x00007f03137ae146 in QEventDispatcherGlib::processEvents (this=0x1065ad0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #30 0x00007f0312bc9bee in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #31 0x00007f031377e97f in QEventLoop::processEvents (this=this@entry=0x7fff9256bc20, flags=...) at kernel/qeventloop.cpp:149 #32 0x00007f031377ec08 in QEventLoop::exec (this=0x7fff9256bc20, flags=...) at kernel/qeventloop.cpp:204 #33 0x00007f03137838a8 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218 #34 0x0000000000403649 in main (argc=3, argv=0x7fff9256bef8) at /usr/src/debug/kdepim-4.10.1/kontact/src/main.cpp:219 Reported using DrKonqi
Also what I can add is that kmail is constantly dangling between online/offline status.
Created attachment 77837 [details] New crash information added by DrKonqi kontact (4.10.1) on KDE Platform 4.10.1 "release 552" using Qt 4.8.4 - What I was doing when the application crashed: Browse folder, deleting mail, then trying to read new one. Special, one message was mark as unread ( in left column) but none visible in the list. So I pick one message hit space until the end, to let kmail open the next unread. When it was at the end of the message, trying to open the unread one the crash occur. Duplicata notice, due to drkonqi, attached if it same but with new version :-) -- Backtrace (Reduced): #6 0x00007f7bac195864 in MessageList::StorageModel::initializeMessageItem (this=0x4259890, mi=0x5512ea0, row=2296, bUseReceiver=false) at /usr/src/debug/kdepim-4.10.1/messagelist/storagemodel.cpp:251 #7 0x00007f7bac14ed98 in MessageList::Core::ModelPrivate::viewItemJobStepInternalForJobPass1Fill (this=0x1e54d90, job=0x51c7b50, tStart=...) at /usr/src/debug/kdepim-4.10.1/messagelist/core/model.cpp:2730 #8 0x00007f7bac1516e5 in MessageList::Core::ModelPrivate::viewItemJobStepInternalForJob (this=this@entry=0x1e54d90, job=job@entry=0x51c7b50, tStart=...) at /usr/src/debug/kdepim-4.10.1/messagelist/core/model.cpp:3392 #9 0x00007f7bac151c7f in MessageList::Core::ModelPrivate::viewItemJobStepInternal (this=this@entry=0x1e54d90) at /usr/src/debug/kdepim-4.10.1/messagelist/core/model.cpp:3779 #10 0x00007f7bac15243b in MessageList::Core::ModelPrivate::viewItemJobStep (this=0x1e54d90) at /usr/src/debug/kdepim-4.10.1/messagelist/core/model.cpp:3965
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.
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.