Bug 308114 - Random crash of kmail
Summary: Random crash of kmail
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.10.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 317922 325041 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-10-09 08:06 UTC by Beat Wolf
Modified: 2017-01-07 21:57 UTC (History)
2 users (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 Beat Wolf 2012-10-09 08:06:40 UTC
Application: kontact (4.9.2)
KDE Platform Version: 4.9.2
Qt Version: 4.8.2
Operating System: Linux 3.2.0-31-generic x86_64
Distribution: Ubuntu 12.04.1 LTS

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

I was using my desktop. KMail was running in the background when it suddenly crashed.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2c3ae0b7c0 (LWP 1922))]

Thread 4 (Thread 0x7f2c1e9a6700 (LWP 1934)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f2c375f9dec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f2c375f9f19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f2c32aaee9a in start_thread (arg=0x7f2c1e9a6700) at pthread_create.c:308
#4  0x00007f2c3832edbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f2c1e1a5700 (LWP 1935)):
#0  0x00007f2c32ab0f69 in __pthread_mutex_lock (mutex=0x7f2c18000a60) at pthread_mutex_lock.c:92
#1  0x00007f2c3261d5a1 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f2c325e11df in g_main_context_acquire () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f2c325e1f04 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f2c325e2164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f2c38aa4906 in QEventDispatcherGlib::processEvents (this=0x7f2c180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x00007f2c38a73e42 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007f2c38a74097 in QEventLoop::exec (this=0x7f2c1e1a4dc0, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007f2c38973057 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#9  0x00007f2c3897607b in QThreadPrivate::start (arg=0xe86410) at thread/qthread_unix.cpp:307
#10 0x00007f2c32aaee9a in start_thread (arg=0x7f2c1e1a5700) at pthread_create.c:308
#11 0x00007f2c3832edbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f2bcbfff700 (LWP 1971)):
#0  0x00007f2c3261d320 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f2c3261d599 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f2c325e11df in g_main_context_acquire () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f2c325e1f04 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f2c325e2164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f2c38aa4906 in QEventDispatcherGlib::processEvents (this=0x7f2bc40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x00007f2c38a73e42 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007f2c38a74097 in QEventLoop::exec (this=0x7f2bcbffed90, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007f2c38973057 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#9  0x00007f2c38a53b4f in QInotifyFileSystemWatcherEngine::run (this=0x14476e0) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x00007f2c3897607b in QThreadPrivate::start (arg=0x14476e0) at thread/qthread_unix.cpp:307
#11 0x00007f2c32aaee9a in start_thread (arg=0x7f2bcbfff700) at pthread_create.c:308
#12 0x00007f2c3832edbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#13 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f2c3ae0b7c0 (LWP 1922)):
[KCrash Handler]
#6  0x00007f2c39f42a30 in vtable for QMenu () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#7  0x00007f2bd5e3ea50 in MailCommon::ExpireCollectionAttribute::loadFromConfig (this=0x1a373e0, collection=...) at ../../mailcommon/expirecollectionattribute.cpp:59
#8  0x00007f2bd5e3f3da in MailCommon::ExpireCollectionAttribute::expirationCollectionAttribute (collection=..., mustDeleteExpirationAttribute=@0x7fff2c27272f: false) at ../../mailcommon/expirecollectionattribute.cpp:191
#9  0x00007f2bd5e862a2 in MailCommon::FolderCollectionMonitor::expireAllCollection (this=0x12923e0, model=0x1241400, immediate=false, parentIndex=...) at ../../mailcommon/foldercollectionmonitor.cpp:92
#10 0x00007f2bd5e863cc in MailCommon::FolderCollectionMonitor::expireAllFolders (this=<optimized out>, immediate=<optimized out>, collectionModel=<optimized out>) at ../../mailcommon/foldercollectionmonitor.cpp:70
#11 0x00007f2bd620f3cd in KMKernel::slotRunBackgroundTasks (this=0x1299a30) at ../../kmail/kmkernel.cpp:1578
#12 0x00007f2bd621cb2a in KMKernel::qt_static_metacall (_o=0x1299a30, _c=<optimized out>, _id=<optimized out>, _a=0x7fff2c272900) at ./kmkernel.moc:185
#13 0x00007f2c38a89761 in QMetaObject::activate (sender=0x13206a0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#14 0x00007f2c38a8e659 in QObject::event (this=0x13206a0, e=<optimized out>) at kernel/qobject.cpp:1157
#15 0x00007f2c3946f7b4 in notify_helper (e=0x7fff2c273010, receiver=0x13206a0, this=0xd7ccf0) at kernel/qapplication.cpp:4556
#16 QApplicationPrivate::notify_helper (this=0xd7ccf0, receiver=0x13206a0, e=0x7fff2c273010) at kernel/qapplication.cpp:4528
#17 0x00007f2c39474583 in QApplication::notify (this=0x7fff2c2732e0, receiver=0x13206a0, e=0x7fff2c273010) at kernel/qapplication.cpp:4417
#18 0x00007f2c3a1aa756 in KApplication::notify (this=0x7fff2c2732e0, receiver=0x13206a0, event=0x7fff2c273010) at ../../kdeui/kernel/kapplication.cpp:311
#19 0x00007f2c38a7530c in QCoreApplication::notifyInternal (this=0x7fff2c2732e0, receiver=0x13206a0, event=0x7fff2c273010) at kernel/qcoreapplication.cpp:915
#20 0x00007f2c38aa66d2 in sendEvent (event=0x7fff2c273010, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#21 QTimerInfoList::activateTimers (this=0xd7a160) at kernel/qeventdispatcher_unix.cpp:611
#22 0x00007f2c38aa40ed in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:186
#23 timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:180
#24 0x00007f2c325e1d53 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007f2c325e20a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x00007f2c325e2164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007f2c38aa489f in QEventDispatcherGlib::processEvents (this=0xd43c10, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#28 0x00007f2c39517cde in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#29 0x00007f2c38a73e42 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#30 0x00007f2c38a74097 in QEventLoop::exec (this=0x7fff2c273270, flags=...) at kernel/qeventloop.cpp:204
#31 0x00007f2c38a793e7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#32 0x00000000004035c9 in main (argc=3, argv=0x7fff2c273908) at ../../../kontact/src/main.cpp:219

Reported using DrKonqi
Comment 1 Jekyll Wu 2013-04-06 13:44:45 UTC
*** Bug 317922 has been marked as a duplicate of this bug. ***
Comment 2 Jekyll Wu 2013-09-18 10:21:43 UTC
*** Bug 325041 has been marked as a duplicate of this bug. ***
Comment 3 Denis Kurz 2016-09-24 19:29:46 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 4 Denis Kurz 2017-01-07 21:57: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.