Bug 200942 - Crash when marking folder as read
Summary: Crash when marking folder as read
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 201466 206406 208796 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-07-21 02:01 UTC by Alec Moskvin
Modified: 2012-08-19 11:04 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 Alec Moskvin 2009-07-21 02:01:08 UTC
Application that crashed: kontact
Version of the application: 4.3.0 rc2
KDE Version: 4.2.96 (KDE 4.2.96 (KDE 4.3 RC2))
Qt Version: 4.5.2
Operating System: Linux 2.6.30.1 i686

What I was doing when the application crashed:
I right-clicked a folder and selected "Mark as Read."

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  QEventLoop::exec (this=0xa43d160, flags={i = -1075117600}) at ../../include/QtCore/../../src/corelib/tools/qvector.h:129
#7  0xb1fdd299 in KMAccount::runPrecommand (this=0x9844b70, precommand=@0x9844b84) at /var/tmp/portage/kde-base/kmail-4.2.96/work/kmail-4.2.96/kmail/kmaccount.cpp:407
#8  0xb2077a9b in KMAcctLocal::preProcess (this=0x9844b70) at /var/tmp/portage/kde-base/kmail-4.2.96/work/kmail-4.2.96/kmail/kmacctlocal.cpp:134
#9  0xb2078860 in KMAcctLocal::processNewMail (this=0x9844b70) at /var/tmp/portage/kde-base/kmail-4.2.96/work/kmail-4.2.96/kmail/kmacctlocal.cpp:70
#10 0xb206d933 in KMail::AccountManager::processNextCheck (this=0x981b1e0, _newMail=false) at /var/tmp/portage/kde-base/kmail-4.2.96/work/kmail-4.2.96/kmail/accountmanager.cpp:230
#11 0xb206e400 in KMail::AccountManager::singleCheckMail (this=0x981b1e0, account=0x9844b70, interactive=false)
    at /var/tmp/portage/kde-base/kmail-4.2.96/work/kmail-4.2.96/kmail/accountmanager.cpp:157
#12 0xb1fd9bfe in KMAccount::mailCheck (this=0x9844b70) at /var/tmp/portage/kde-base/kmail-4.2.96/work/kmail-4.2.96/kmail/kmaccount.cpp:445
#13 0xb1fda143 in KMAccount::qt_metacall (this=0x9844b70, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfeb0568)
    at /var/tmp/portage/kde-base/kmail-4.2.96/work/kmail-4.2.96_build/kmail/kmaccount.moc:147
#14 0xb6fab461 in QMetaObject::activate (sender=0x984b240, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x1) at kernel/qobject.cpp:3101
#15 0xb6faba23 in QMetaObject::activate (sender=0x984b240, m=0xb7044924, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3178
#16 0xb6fe3298 in QTimer::timeout (this=0x984b240) at .moc/release-shared/moc_qtimer.cpp:128
#17 0xb6fb22ae in QTimer::timerEvent (this=0x984b240, e=0xbfeb09fc) at kernel/qtimer.cpp:261
#18 0xb6fa816f in QObject::event (this=0x984b240, e=0xbfeb09fc) at kernel/qobject.cpp:1066
#19 0xb73a50cc in QApplicationPrivate::notify_helper (this=0x957c4e8, receiver=0x984b240, e=0xbfeb09fc) at kernel/qapplication.cpp:4056
#20 0xb73adbb3 in QApplication::notify (this=0xbfeb0d9c, receiver=0x984b240, e=0xbfeb09fc) at kernel/qapplication.cpp:3603
#21 0xb7c3d59e in KApplication::notify (this=0xbfeb0d9c, receiver=0x984b240, event=0xbfeb09fc) at /var/tmp/portage/kde-base/kdelibs-4.2.96/work/kdelibs-4.2.96/kdeui/kernel/kapplication.cpp:302
#22 0xb6f98c52 in QCoreApplication::notifyInternal (this=0xbfeb0d9c, receiver=0x984b240, event=0xbfeb09fc) at kernel/qcoreapplication.cpp:606
#23 0xb6fc3bf1 in QTimerInfoList::activateTimers (this=0x957bf24) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#24 0xb6fc0831 in timerSourceDispatch (source=0x957bef0) at kernel/qeventdispatcher_glib.cpp:165
#25 0xb596e43f in IA__g_main_context_dispatch (context=0x957bd90) at gmain.c:1824
#26 0xb5971b8b in g_main_context_iterate (context=0x957bd90, block=1, dispatch=1, self=0x957bb80) at gmain.c:2455
#27 0xb5971d19 in IA__g_main_context_iteration (context=0x957bd90, may_block=1) at gmain.c:2518
#28 0xb6fc0789 in QEventDispatcherGlib::processEvents (this=0x957c260, flags={i = -1075115144}) at kernel/qeventdispatcher_glib.cpp:327
#29 0xb74354d6 in QGuiEventDispatcherGlib::processEvents (this=0x957c260, flags={i = -1075115096}) at kernel/qguieventdispatcher_glib.cpp:202
#30 0xb6f9739b in QEventLoop::processEvents (this=0xbfeb0c10, flags={i = -1075115032}) at kernel/qeventloop.cpp:149
#31 0xb6f9757a in QEventLoop::exec (this=0xbfeb0c10, flags={i = -1075114984}) at kernel/qeventloop.cpp:197
#32 0xb6f997f1 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#33 0xb73a4f38 in QApplication::exec () at kernel/qapplication.cpp:3525
#34 0x0804bfd7 in main (argc=3, argv=0xbfeb0f94) at /var/tmp/portage/kde-base/kontact-4.2.96/work/kontact-4.2.96/kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 Dario Andres 2009-07-21 02:39:32 UTC
The backtrace looks related to bug 196053. Thanks
Comment 2 Dario Andres 2009-07-25 21:48:42 UTC
*** Bug 201466 has been marked as a duplicate of this bug. ***
Comment 3 Dario Andres 2009-07-25 21:49:15 UTC
Bug 201466 has an updated backtrace and another description. Thanks
Comment 4 Dario Andres 2009-09-05 20:57:32 UTC
*** Bug 206406 has been marked as a duplicate of this bug. ***
Comment 5 Christophe Marin 2009-09-28 18:19:45 UTC
*** Bug 208796 has been marked as a duplicate of this bug. ***
Comment 6 Myriam Schweingruber 2012-08-19 11:04:04 UTC
Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding