Bug 360442 - Kontact crashed when clicked item in Summary-Upcoming events
Summary: Kontact crashed when clicked item in Summary-Upcoming events
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-12 17:51 UTC by richard virden
Modified: 2018-02-01 09:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description richard virden 2016-03-12 17:51:30 UTC
Application: kontact (4.14.9)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 3.16.7-35-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: On Kontact-Summary page, clicked on link text of final item in a list of 7 upcoming events. This was on the first use of Kontact after log-on and there was no crash after reloading the application and clicking on the same entry and other entries.

The crash does not seem to be reproducible.

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

Thread 4 (Thread 0x7f14071ea700 (LWP 2667)):
#0  0x00007f141be4f03f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f141f5f5686 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4
#2  0x00007f141f5f56b9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4
#3  0x00007f141be4b0a4 in start_thread () from /lib64/libpthread.so.0
#4  0x00007f1421dd800d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f13c68cf700 (LWP 2668)):
#0  0x00007f141be4f03f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f141f367e7d in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib64/libQtWebKit.so.4
#2  0x00007f141f61d1e6 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib64/libQtWebKit.so.4
#3  0x00007f141be4b0a4 in start_thread () from /lib64/libpthread.so.0
#4  0x00007f1421dd800d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f13b2b97700 (LWP 2786)):
#0  0x00007f1421dcfbdd in poll () from /lib64/libc.so.6
#1  0x00007f141b87fbe4 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f141b87fcec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f14225530de in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#4  0x00007f1422524e6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#5  0x00007f1422525165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#6  0x00007f14224220bf in QThread::exec() () from /usr/lib64/libQtCore.so.4
#7  0x00007f142242479f in ?? () from /usr/lib64/libQtCore.so.4
#8  0x00007f141be4b0a4 in start_thread () from /lib64/libpthread.so.0
#9  0x00007f1421dd800d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f1424856800 (LWP 2666)):
[KCrash Handler]
#5  0x00007f1422f34700 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#6  0x00007f1422f3adea in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#7  0x00007f1423c4ce0a in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#8  0x00007f14225262ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#9  0x00007f1422f3a5e3 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib64/libQtGui.so.4
#10 0x00007f1422fabc9b in ?? () from /usr/lib64/libQtGui.so.4
#11 0x00007f1422faa70c in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/libQtGui.so.4
#12 0x00007f1422fd15c2 in ?? () from /usr/lib64/libQtGui.so.4
#13 0x00007f141b87fa04 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#14 0x00007f141b87fc48 in ?? () from /usr/lib64/libglib-2.0.so.0
#15 0x00007f141b87fcec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#16 0x00007f14225530be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#17 0x00007f1422fd1676 in ?? () from /usr/lib64/libQtGui.so.4
#18 0x00007f1422524e6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#19 0x00007f1422525165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#20 0x00007f142252a5b9 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#21 0x00000000004037f2 in ?? ()
#22 0x00007f1421d14b05 in __libc_start_main () from /lib64/libc.so.6
#23 0x0000000000403c97 in _start ()

Possible duplicates by query: bug 360426, bug 360370, bug 360228, bug 360227, bug 360107.

Reported using DrKonqi
Comment 1 Denis Kurz 2017-06-23 21:28:56 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 2 Denis Kurz 2018-02-01 09:51:38 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.