Bug 354768 - Crash while clicking through settings dialouge
Summary: Crash while clicking through settings dialouge
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-11-03 01:42 UTC by sedrubal
Modified: 2018-02-01 09:48 UTC (History)
0 users

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 sedrubal 2015-11-03 01:42:42 UTC
Application: kontact (4.14.9)
KDE Platform Version: 4.14.11
Qt Version: 4.8.6
Operating System: Linux 4.2.3-200.fc22.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

I clicked through the settings dialouge of Kcontact, "Mail" app was disabled and I activated it so see the mail-settings. When I clicked on "Composer" it crashed.

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".
81	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f8a910bc900 (LWP 4221))]

Thread 4 (Thread 0x7f8a252fd700 (LWP 4222)):
#0  0x00007f8a8b82b540 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f8a901fdf61 in JSC::BlockAllocator::blockFreeingThreadMain() (this=0x19ae1f8) at /usr/src/debug/webkit-qtwebkit-23/Source/JavaScriptCore/heap/BlockAllocator.cpp:128
#2  0x00007f8a904fc6d6 in WTF::wtfThreadEntryPoint(void*) (param=0x19a0700) at /usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/ThreadingPthreads.cpp:196
#3  0x00007f8a8b826555 in start_thread (arg=0x7f8a252fd700) at pthread_create.c:333
#4  0x00007f8a8a54bb9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f8a16241700 (LWP 4226)):
#0  0x00007f8a8a5402fd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f8a87583dbc in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f8a100013e0, timeout=<optimized out>, context=0x7f8a100009a0) at gmain.c:4103
#2  0x00007f8a87583dbc in g_main_context_iterate (context=context@entry=0x7f8a100009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3803
#3  0x00007f8a87583ecc in g_main_context_iteration (context=0x7f8a100009a0, may_block=1) at gmain.c:3869
#4  0x00007f8a8b2644ee in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7f8a100008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#5  0x00007f8a8b232791 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7f8a16240cd0, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007f8a8b232b05 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7f8a16240cd0, flags=...) at kernel/qeventloop.cpp:204
#7  0x00007f8a8b122289 in QThread::exec() (this=<optimized out>) at thread/qthread.cpp:538
#8  0x00007f8a8b124aac in QThreadPrivate::start(void*) (arg=0x272a0f0) at thread/qthread_unix.cpp:349
#9  0x00007f8a8b826555 in start_thread (arg=0x7f8a16241700) at pthread_create.c:333
#10 0x00007f8a8a54bb9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f8a0d465700 (LWP 4397)):
#0  0x00007f8a8b82b540 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f8a7ead8b5a in QTWTF::TCMalloc_PageHeap::scavengerThread() (this=0x7f8a7eddbf00 <QTWTF::pageheap_memory>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x00007f8a7ead8b89 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) (context=<optimized out>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x00007f8a8b826555 in start_thread (arg=0x7f8a0d465700) at pthread_create.c:333
#4  0x00007f8a8a54bb9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f8a910bc900 (LWP 4221)):
[KCrash Handler]
#6  0x00007f8a1d441a2b in PimCommon::AutoCorrection::autocorrectEntries() const () at /lib64/libpimcommon.so.4
#7  0x00007f8a1d44a2f2 in PimCommon::AutoCorrectionWidget::loadAutoCorrectionAndException() () at /lib64/libpimcommon.so.4
#8  0x00007f8a1d44a9c9 in PimCommon::AutoCorrectionWidget::loadConfig() () at /lib64/libpimcommon.so.4
#9  0x00007f8a18597e01 in ConfigModuleWithTabs::load() () at /lib64/libkmailprivate.so.4
#10 0x00007f8a8d168849 in KCModule::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=<optimized out>, _id=<optimized out>, _a=<optimized out>, _c=<optimized out>) at ./kcmodule.moc:65
#11 0x00007f8a8b24de61 in QObject::event(QEvent*) (this=this@entry=0x4a41170, e=e@entry=0x4262e70) at kernel/qobject.cpp:1222
#12 0x00007f8a8c3a47ac in QWidget::event(QEvent*) (this=0x4a41170, event=0x4262e70) at kernel/qwidget.cpp:8859
#13 0x00007f8a8c3503ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x17b6880, receiver=receiver@entry=0x4a41170, e=e@entry=0x4262e70) at kernel/qapplication.cpp:4565
#14 0x00007f8a8c357206 in QApplication::notify(QObject*, QEvent*) (this=this@entry=0x7ffddb49c6d0, receiver=receiver@entry=0x4a41170, e=e@entry=0x4262e70) at kernel/qapplication.cpp:4351
#15 0x00007f8a8d0cc54a in KApplication::notify(QObject*, QEvent*) (this=0x7ffddb49c6d0, receiver=0x4a41170, event=0x4262e70) at ../../kdeui/kernel/kapplication.cpp:311
#16 0x00007f8a8b233f1d in QCoreApplication::notifyInternal(QObject*, QEvent*) (this=0x7ffddb49c6d0, receiver=receiver@entry=0x4a41170, event=event@entry=0x4262e70) at kernel/qcoreapplication.cpp:953
#17 0x00007f8a8b237536 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (event=0x4262e70, receiver=0x4a41170) at kernel/qcoreapplication.h:231
#18 0x00007f8a8b237536 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x1766c60) at kernel/qcoreapplication.cpp:1577
#19 0x00007f8a8b237813 in QCoreApplication::sendPostedEvents(QObject*, int) (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1470
#20 0x00007f8a8b26435e in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) () at kernel/qcoreapplication.h:236
#21 0x00007f8a8b26435e in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x17b6570) at kernel/qeventdispatcher_glib.cpp:300
#22 0x00007f8a87583a8a in g_main_context_dispatch (context=0x17b6bd0) at gmain.c:3122
#23 0x00007f8a87583a8a in g_main_context_dispatch (context=context@entry=0x17b6bd0) at gmain.c:3737
#24 0x00007f8a87583e20 in g_main_context_iterate (context=context@entry=0x17b6bd0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3808
#25 0x00007f8a87583ecc in g_main_context_iteration (context=0x17b6bd0, may_block=1) at gmain.c:3869
#26 0x00007f8a8b2644ce in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x1768530, flags=...) at kernel/qeventdispatcher_glib.cpp:450
#27 0x00007f8a8c3f6626 in QGuiEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#28 0x00007f8a8b232791 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffddb49c5e0, flags=...) at kernel/qeventloop.cpp:149
#29 0x00007f8a8b232b05 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffddb49c5e0, flags=...) at kernel/qeventloop.cpp:204
#30 0x00007f8a8b2386a9 in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1225
#31 0x0000000000403787 in main ()

Reported using DrKonqi
Comment 1 Denis Kurz 2017-06-23 20:22:17 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those 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:48:12 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.