Bug 208296

Summary: Kmail part crashed a while after making a new dimap folder and moving some messages there
Product: [Applications] kontact Reporter: Andreas K. Huettel <dilfridge>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Andreas K. Huettel 2009-09-23 15:03:23 UTC
Application that crashed: kontact
Version of the application: 4.3.1
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.1
Operating System: Linux 2.6.30-gentoo-r5 x86_64

What I was doing when the application crashed:
* made a new dimap folder
* moved some messages there from inbox
* dimap was synchronized
* click on message -> crash!

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f97726f99b0 in vtable for DwString () from /usr/lib64/libmimelib.so.4
#6  0x00007f9774532b21 in KMReaderWin::parseMsg (this=0x22b3f30, aMsg=0x2d60fa0) at /var/tmp/portage/kde-base/kmail-4.3.1/work/kmail-4.3.1/kmail/kmreaderwin.cpp:1681
#7  0x00007f977452069a in KMReaderWin::displayMessage (this=0x22b3f30) at /var/tmp/portage/kde-base/kmail-4.3.1/work/kmail-4.3.1/kmail/kmreaderwin.cpp:1605
#8  0x00007f9774520885 in KMReaderWin::updateReaderWin (this=0x22b3f30) at /var/tmp/portage/kde-base/kmail-4.3.1/work/kmail-4.3.1/kmail/kmreaderwin.cpp:1545
#9  0x00007f977452c955 in KMReaderWin::qt_metacall (this=0x22b3f30, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffd5fac060)
    at /var/tmp/portage/kde-base/kmail-4.3.1/work/kmail-4.3.1_build/kmail/kmreaderwin.moc:168
#10 0x00007f9785987e4d in QMetaObject::activate (sender=0x22b3fd8, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x1) at kernel/qobject.cpp:3108
#11 0x00007f97859844e3 in QObject::event (this=0x22b3fd8, e=0x1cfb324) at kernel/qobject.cpp:1073
#12 0x00007f978673565d in QApplicationPrivate::notify_helper (this=0x1d2b4b0, receiver=0x22b3fd8, e=0x7fffd5fac700) at kernel/qapplication.cpp:4057
#13 0x00007f978673e04a in QApplication::notify (this=0x7fffd5facb50, receiver=0x22b3fd8, e=0x7fffd5fac700) at kernel/qapplication.cpp:4022
#14 0x00007f97875008ab in KApplication::notify (this=0x7fffd5facb50, receiver=0x22b3fd8, event=0x7fffd5fac700)
    at /var/tmp/portage/kde-base/kdelibs-4.3.1-r1/work/kdelibs-4.3.1/kdeui/kernel/kapplication.cpp:302
#15 0x00007f9785975a1b in QCoreApplication::notifyInternal (this=0x7fffd5facb50, receiver=0x22b3fd8, event=0x7fffd5fac700) at kernel/qcoreapplication.cpp:606
#16 0x00007f978599e12e in QTimerInfoList::activateTimers (this=0x1d24500) at kernel/qcoreapplication.h:213
#17 0x00007f978599af2d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:164
#18 0x00007f9780d91ce0 in IA__g_main_context_dispatch (context=0x1d2d920) at gmain.c:1824
#19 0x00007f9780d95408 in g_main_context_iterate (context=0x1d2d920, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2455
#20 0x00007f9780d955cc in IA__g_main_context_iteration (context=0x1d2d920, may_block=1) at gmain.c:2518
#21 0x00007f978599ae8f in QEventDispatcherGlib::processEvents (this=0x1d22950, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:324
#22 0x00007f97867bb81f in QGuiEventDispatcherGlib::processEvents (this=0x2d60fa0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#23 0x00007f97859743d2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -704984720}) at kernel/qeventloop.cpp:149
#24 0x00007f9785974565 in QEventLoop::exec (this=0x7fffd5fac9b0, flags={i = -704984640}) at kernel/qeventloop.cpp:196
#25 0x00007f97859765fc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#26 0x0000000000404b59 in main (argc=1, argv=0x7fffd5fad128) at /var/tmp/portage/kde-base/kontact-4.3.1/work/kontact-4.3.1/kontact/src/main.cpp:218

This bug may be a duplicate of or related to bug 205809

Reported using DrKonqi
Comment 1 Dario Andres 2009-09-23 15:38:24 UTC
Thanks

*** This bug has been marked as a duplicate of bug 180741 ***