Bug 328869

Summary:	kontact crash
Product:	[Applications] kontact	Reporter:	Jannis Liapis <ahepas1999>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	Keywords:	drkonqi
Priority:	NOR
Version:	4.11.3
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Jannis Liapis 2013-12-16 14:49:56 UTC

Application: kontact (4.11.3)
KDE Platform Version: 4.11.3
Qt Version: 4.8.5
Operating System: Linux 3.11.6-4-desktop x86_64
Distribution: "openSUSE 13.1 (Bottle) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:I wasn't doing something in particular...I just rebooted my laptop when the crash occured...propably when it was loading stuff upon startup.

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

Thread 4 (Thread 0x7f3a8c53d700 (LWP 1703)):
#0  0x00007f3aa04bd0af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f3aa3c53f76 in ?? () from /usr/lib64/libQtWebKit.so.4
#2  0x00007f3aa3c53fa9 in ?? () from /usr/lib64/libQtWebKit.so.4
#3  0x00007f3aa04b90db in start_thread () from /lib64/libpthread.so.0
#4  0x00007f3aa63e590d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f3a4bc32700 (LWP 1711)):
#0  0x00007f3aa04bd0af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f3aa39c62cd in ?? () from /usr/lib64/libQtWebKit.so.4
#2  0x00007f3aa3c7bad6 in ?? () from /usr/lib64/libQtWebKit.so.4
#3  0x00007f3aa04b90db in start_thread () from /lib64/libpthread.so.0
#4  0x00007f3aa63e590d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f3a3e921700 (LWP 1727)):
#0  0x00007f3a9fef5e28 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0
#1  0x00007f3a9fef6523 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f3a9fef670c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f3aa6b62d76 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#4  0x00007f3aa6b34d0f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#5  0x00007f3aa6b35005 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#6  0x00007f3aa6a33fef in QThread::exec() () from /usr/lib64/libQtCore.so.4
#7  0x00007f3aa6a3668f in ?? () from /usr/lib64/libQtCore.so.4
#8  0x00007f3aa04b90db in start_thread () from /lib64/libpthread.so.0
#9  0x00007f3aa63e590d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f3aa8ea6880 (LWP 1683)):
[KCrash Handler]
#6  0x00007f3a43caed76 in operator bool (this=0x50) at /usr/include/ksharedptr.h:106
#7  KMKernel::config (this=0x2a99ba0) at /usr/src/debug/kdepim-4.11.3/kmail/kmkernel.cpp:1527
#8  0x00007f3a438d145e in MailCommon::ExpireCollectionAttribute::loadFromConfig (this=this@entry=0x2ffc180, collection=...) at /usr/src/debug/kdepim-4.11.3/mailcommon/collectionpage/expirecollectionattribute.cpp:59
#9  0x00007f3a438d1b47 in MailCommon::ExpireCollectionAttribute::expirationCollectionAttribute (collection=..., mustDeleteExpirationAttribute=@0x7fff6bf811f0: false) at /usr/src/debug/kdepim-4.11.3/mailcommon/collectionpage/expirecollectionattribute.cpp:191
#10 0x00007f3a43920a38 in MailCommon::FolderCollectionMonitor::expireAllCollection (this=0x2aad920, model=0x2aa2580, immediate=immediate@entry=false, parentIndex=...) at /usr/src/debug/kdepim-4.11.3/mailcommon/folder/foldercollectionmonitor.cpp:94
#11 0x00007f3a43920b7c in MailCommon::FolderCollectionMonitor::expireAllFolders (this=<optimized out>, immediate=immediate@entry=false, collectionModel=<optimized out>) at /usr/src/debug/kdepim-4.11.3/mailcommon/folder/foldercollectionmonitor.cpp:72
#12 0x00007f3a43cae6dd in KMKernel::slotRunBackgroundTasks (this=0x2a99ba0) at /usr/src/debug/kdepim-4.11.3/kmail/kmkernel.cpp:1601
#13 0x00007f3a43cc156d in KMKernel::qt_static_metacall (_o=0x7fff6bf81060, _c=44669856, _id=-1502972368, _a=0x7fff6bf813d0) at /usr/src/debug/kdepim-4.11.3/build/kmail/kmkernel.moc:206
#14 0x00007f3aa6b49d68 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4
#15 0x00007f3aa6b4df31 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#16 0x00007f3aa75468ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#17 0x00007f3aa754ce70 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#18 0x00007f3aa825d18a in KApplication::notify (this=0x7fff6bf81bf0, receiver=0x2b1a050, event=0x7fff6bf81870) at /usr/src/debug/kdelibs-4.11.3/kdeui/kernel/kapplication.cpp:311
#19 0x00007f3aa6b360ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#20 0x00007f3aa6b6583c in ?? () from /usr/lib64/libQtCore.so.4
#21 0x00007f3aa6b62b59 in ?? () from /usr/lib64/libQtCore.so.4
#22 0x00007f3a9fef6316 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#23 0x00007f3a9fef6668 in ?? () from /usr/lib64/libglib-2.0.so.0
#24 0x00007f3a9fef670c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#25 0x00007f3aa6b62d55 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#26 0x00007f3aa75e3936 in ?? () from /usr/lib64/libQtGui.so.4
#27 0x00007f3aa6b34d0f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x00007f3aa6b35005 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#29 0x00007f3aa6b3a13b in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#30 0x0000000000403960 in ?? ()
#31 0x00007f3aa631fbe5 in __libc_start_main () from /lib64/libc.so.6
#32 0x0000000000403e29 in _start ()

Reported using DrKonqi

Comment 1 Denis Kurz 2016-09-24 19:27:30 UTC

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.

Comment 2 Denis Kurz 2017-01-07 22:23:29 UTC

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.