Bug 230828 - Kontact crashed after selecting unread message for reading
Summary: Kontact crashed after selecting unread message for reading
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-15 13:50 UTC by Dave Thacker
Modified: 2017-06-24 00:26 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 Dave Thacker 2010-03-15 13:50:18 UTC
Application that crashed: kontact
Version of the application: 4.3.5
KDE Version: 4.3.5 (KDE 4.3.5)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-20-generic x86_64
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
I was reading new email in a folder set up under my inbox.  I had read about 5-6 messages so far.  When I clicked on the next unread message, kontact crashed.   Other apps runing at the time: Firefox, Folding@home, a few terminals

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5  KConfigIniBackend::writeConfig (this=<value optimized out>, locale=<value optimized out>, entryMap=..., options=<value optimized out>, data=<value optimized out>)
    at ../../kdecore/config/kconfigini.cpp:424
#6  0x00007f1029d6bcbb in KConfig::sync (this=0xeb89a0) at ../../kdecore/config/kconfig.cpp:338
#7  0x00007f101410a2d0 in GlobalSettings::qt_metacall (this=0xf787c0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=<value optimized out>) at ./globalsettings.moc:66
#8  0x00007f10299f6ddc in QMetaObject::activate (sender=0xedbf40, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3113
#9  0x00007f10299f0d83 in QObject::event (this=0xedbf40, e=0xfdc1f8) at kernel/qobject.cpp:1075
#10 0x00007f102a305efc in QApplicationPrivate::notify_helper (this=0x890d10, receiver=0xedbf40, e=0x7fff280840a0) at kernel/qapplication.cpp:4056
#11 0x00007f102a30d1ce in QApplication::notify (this=0x7fff28084400, receiver=0xedbf40, e=0x7fff280840a0) at kernel/qapplication.cpp:4021
#12 0x00007f102af3cf46 in KApplication::notify (this=0x7fff28084400, receiver=0xedbf40, event=0x7fff280840a0) at ../../kdeui/kernel/kapplication.cpp:302
#13 0x00007f10299e1c2c in QCoreApplication::notifyInternal (this=0x7fff28084400, receiver=0xedbf40, event=0x7fff280840a0) at kernel/qcoreapplication.cpp:610
#14 0x00007f1029a0c862 in QCoreApplication::sendEvent (this=0x895c20) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#15 QTimerInfoList::activateTimers (this=0x895c20) at kernel/qeventdispatcher_unix.cpp:572
#16 0x00007f1029a0a25d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#17 0x00007f1023259bce in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#18 0x00007f102325d598 in ?? () from /lib/libglib-2.0.so.0
#19 0x00007f102325d6c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#20 0x00007f1029a0a1a6 in QEventDispatcherGlib::processEvents (this=0x860cb0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#21 0x00007f102a39a4be in QGuiEventDispatcherGlib::processEvents (this=0xe, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#22 0x00007f10299e0532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#23 0x00007f10299e0904 in QEventLoop::exec (this=0x7fff28084340, flags=) at kernel/qeventloop.cpp:201
#24 0x00007f10299e2ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#25 0x0000000000403f47 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 Christophe Marin 2010-03-26 22:28:30 UTC
Were you able to reproduce this crash with KDE 4.4.0 or 4.4.1 ?
Comment 2 Christoph Feck 2013-09-12 21:44:19 UTC
This crash report is at least 3 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources.

If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED)