Bug 359976 - Kontact crashed while start
Summary: Kontact crashed while start
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-03-01 22:17 UTC by Vlastimil Kriz
Modified: 2018-02-01 09:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Vlastimil Kriz 2016-03-01 22:17:04 UTC 
Application: kontact (4.14.10)
KDE Platform Version: 4.14.17
Qt Version: 4.8.6
Operating System: Linux 4.1.15-8-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
KMail cannot show content the of mails ("Retrieving Folder Contents, Please wait ...") so I close it and start again - than it crashed

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

Thread 4 (Thread 0x7f3d3655b700 (LWP 17994)):
#0  0x00007f3d4c19a03f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f3d51320eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4
#2  0x00007f3d51320ee9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4
#3  0x00007f3d4c1960a4 in start_thread () from /lib64/libpthread.so.0
#4  0x00007f3d52110fed in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f3d35d3a700 (LWP 17995)):
#0  0x00007f3d4c19a03f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f3d51093b3d in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib64/libQtWebKit.so.4
#2  0x00007f3d51348a06 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib64/libQtWebKit.so.4
#3  0x00007f3d4c1960a4 in start_thread () from /lib64/libpthread.so.0
#4  0x00007f3d52110fed in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f3ce2902700 (LWP 18003)):
#0  0x00007fff6dbe6b26 in clock_gettime ()
#1  0x00007f3d5211dc3d in clock_gettime () from /lib64/libc.so.6
#2  0x00007f3d5282c097 in do_gettime (frac=0x7f3ce2901b70, sec=0x7f3ce2901b68) at tools/qelapsedtimer_unix.cpp:127
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:144
#4  0x00007f3d52907775 in updateCurrentTime (this=0x7f3cdc0030e0) at kernel/qeventdispatcher_unix.cpp:354
#5  QTimerInfoList::timerWait (this=0x7f3cdc0030e0, tm=...) at kernel/qeventdispatcher_unix.cpp:460
#6  0x00007f3d52905e8c in timerSourcePrepareHelper (src=<optimized out>, timeout=0x7f3ce2901c24) at kernel/qeventdispatcher_glib.cpp:143
#7  0x00007f3d52905f35 in timerSourcePrepare (source=<optimized out>, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:176
#8  0x00007f3d4bbc94ad in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0
#9  0x00007f3d4bbc9d80 in ?? () from /usr/lib64/libglib-2.0.so.0
#10 0x00007f3d4bbc9f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#11 0x00007f3d52905fde in QEventDispatcherGlib::processEvents (this=0x7f3cdc0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#12 0x00007f3d528d7d4f in QEventLoop::processEvents (this=this@entry=0x7f3ce2901de0, flags=...) at kernel/qeventloop.cpp:149
#13 0x00007f3d528d8045 in QEventLoop::exec (this=this@entry=0x7f3ce2901de0, flags=...) at kernel/qeventloop.cpp:204
#14 0x00007f3d527d54df in QThread::exec (this=<optimized out>) at thread/qthread.cpp:538
#15 0x00007f3d527d7bbf in QThreadPrivate::start (arg=0x2488ab0) at thread/qthread_unix.cpp:349
#16 0x00007f3d4c1960a4 in start_thread () from /lib64/libpthread.so.0
#17 0x00007f3d52110fed in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f3d54c41800 (LWP 17993)):
[KCrash Handler]
#6  Kontact::MainWindow::activateInitialPluginModule (this=0x223ad30) at /usr/src/debug/kdepim-4.14.10/kontact/src/mainwindow.cpp:329
#7  0x000000000040410a in KontactApp::newInstance (this=0x7fff6da4d4f0) at /usr/src/debug/kdepim-4.14.10/kontact/src/main.cpp:148
#8  0x00007f3d5400203a in ?? () from /usr/lib64/libkdeui.so.5
#9  0x00007f3d540020b5 in ?? () from /usr/lib64/libkdeui.so.5
#10 0x00007f3d540022c3 in ?? () from /usr/lib64/libkdeui.so.5
#11 0x00007f3d4ea28d4d in QDBusConnectionPrivate::deliverCall (this=this@entry=0x2061cb0, object=object@entry=0x221d360, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:951
#12 0x00007f3d4ea29f4b in QDBusConnectionPrivate::activateCall (this=this@entry=0x2061cb0, object=0x221d360, flags=flags@entry=337, msg=...) at qdbusintegrator.cpp:863
#13 0x00007f3d4ea2a9bd in QDBusConnectionPrivate::activateObject (this=0x2061cb0, node=..., msg=..., pathStartPos=<optimized out>) at qdbusintegrator.cpp:1427
#14 0x00007f3d4ea2aa8b in QDBusActivateObjectEvent::placeMetaCall (this=0x42b6420) at qdbusintegrator.cpp:1541
#15 0x00007f3d528f149e in QObject::event (this=this@entry=0x7fff6da4d4f0, e=e@entry=0x42b6420) at kernel/qobject.cpp:1231
#16 0x00007f3d528dd61c in QCoreApplication::event (this=this@entry=0x7fff6da4d4f0, e=e@entry=0x42b6420) at kernel/qcoreapplication.cpp:1765
#17 0x00007f3d532e8763 in QApplication::event (this=0x7fff6da4d4f0, e=0x42b6420) at kernel/qapplication.cpp:2544
#18 0x00007f3d532e379c in QApplicationPrivate::notify_helper (this=this@entry=0x207e080, receiver=receiver@entry=0x7fff6da4d4f0, e=e@entry=0x42b6420) at kernel/qapplication.cpp:4565
#19 0x00007f3d532e9cdd in QApplication::notify (this=0x7fff6da4d4f0, receiver=0x7fff6da4d4f0, e=0x42b6420) at kernel/qapplication.cpp:4351
#20 0x00007f3d53ffae1a in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#21 0x00007f3d528d918d in QCoreApplication::notifyInternal (this=0x7fff6da4d4f0, receiver=receiver@entry=0x7fff6da4d4f0, event=event@entry=0x42b6420) at kernel/qcoreapplication.cpp:953
#22 0x00007f3d528dc45d in sendEvent (event=0x42b6420, receiver=0x7fff6da4d4f0) at kernel/qcoreapplication.h:231
#23 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x1ff2240) at kernel/qcoreapplication.cpp:1577
#24 0x00007f3d528dc903 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1470
#25 0x00007f3d529067fe in sendPostedEvents () at kernel/qcoreapplication.h:236
#26 postEventSourceDispatch (s=0x2082670) at kernel/qeventdispatcher_glib.cpp:300
#27 0x00007f3d4bbc9c84 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#28 0x00007f3d4bbc9ed8 in ?? () from /usr/lib64/libglib-2.0.so.0
#29 0x00007f3d4bbc9f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#30 0x00007f3d52905fbe in QEventDispatcherGlib::processEvents (this=0x1ff7ae0, flags=...) at kernel/qeventdispatcher_glib.cpp:450
#31 0x00007f3d533806a6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#32 0x00007f3d528d7d4f in QEventLoop::processEvents (this=this@entry=0x7fff6da4d3f0, flags=...) at kernel/qeventloop.cpp:149
#33 0x00007f3d528d8045 in QEventLoop::exec (this=this@entry=0x7fff6da4d3f0, flags=...) at kernel/qeventloop.cpp:204
#34 0x00007f3d528dd499 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225
#35 0x00007f3d532e1f6c in QApplication::exec () at kernel/qapplication.cpp:3823
#36 0x00000000004037f2 in main (argc=1, argv=0x7fff6da4d638) at /usr/src/debug/kdepim-4.14.10/kontact/src/main.cpp:219

The reporter indicates this bug may be a duplicate of or related to bug 350822.

Possible duplicates by query: bug 351876, bug 350822.

Reported using DrKonqi
Comment 1 Vlastimil Kriz 2016-03-01 22:34:06 UTC 
The problem with non visible content of mails in one box ("Retrieving Folder Contents, Please wait ...") was caused with non-confirmed dialogue window about un-trustable certificate, that I didn't notice, because it did not pop-up over the other opened windows. (When I confirm the dialogue, it also caused crash).
Comment 2 Denis Kurz 2017-06-23 21:28:06 UTC 
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those Framework-based versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 3 Denis Kurz 2018-02-01 09:50:59 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.