Bug 208314 - Kontact crashed while selecting an eMail in my inbox
Summary: Kontact crashed while selecting an eMail in my inbox
Status: RESOLVED DUPLICATE of bug 180741
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: 2009-09-23 18:07 UTC by Lukas
Modified: 2009-09-25 02:21 UTC (History)
1 user (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 Lukas 2009-09-23 18:07:00 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.2
Operating System: Linux 2.6.30-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (squeeze)

What I was doing when the application crashed:
While selecting an eMail which was beeing moved from the trash as it was not a spam to my local inbox, kontact crashed instantly.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  0x0000000003d79ec8 in ?? ()
#6  0x00007f6fc8434ac1 in KMReaderWin::parseMsg (this=0x20ff890, aMsg=0xc07a070) at ../../kmail/kmreaderwin.cpp:1681
#7  0x00007f6fc84229ba in KMReaderWin::displayMessage (this=0x20ff890) at ../../kmail/kmreaderwin.cpp:1605
#8  0x00007f6fc8422ba5 in KMReaderWin::updateReaderWin (this=0x20ff890) at ../../kmail/kmreaderwin.cpp:1545
#9  0x00007f6fc842e9bd in KMReaderWin::qt_metacall (this=0x20ff890, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff6daf6070) at ./kmreaderwin.moc:168
#10 0x00007f6fdf077682 in QMetaObject::activate (sender=0x20ff938, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x1) at kernel/qobject.cpp:3112
#11 0x00007f6fdf071bf3 in QObject::event (this=0x20ff938, e=0x18f8434) at kernel/qobject.cpp:1074
#12 0x00007f6fde4da80d in QApplicationPrivate::notify_helper (this=0x1928bd0, receiver=0x20ff938, e=0x7fff6daf6720) at kernel/qapplication.cpp:4056
#13 0x00007f6fde4e286a in QApplication::notify (this=0x7fff6daf6b70, receiver=0x20ff938, e=0x7fff6daf6720) at kernel/qapplication.cpp:4021
#14 0x00007f6fdf9ff43b in KApplication::notify (this=0x7fff6daf6b70, receiver=0x20ff938, event=0x7fff6daf6720) at ../../kdeui/kernel/kapplication.cpp:302
#15 0x00007f6fdf06251c in QCoreApplication::notifyInternal (this=0x7fff6daf6b70, receiver=0x20ff938, event=0x7fff6daf6720) at kernel/qcoreapplication.cpp:610
#16 0x00007f6fdf08e826 in QCoreApplication::sendEvent (this=0x19223c0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#17 QTimerInfoList::activateTimers (this=0x19223c0) at kernel/qeventdispatcher_unix.cpp:572
#18 0x00007f6fdf08ac9d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#19 0x00007f6fd819386a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#20 0x00007f6fd8196eb8 in ?? () from /usr/lib/libglib-2.0.so.0
#21 0x00007f6fd819706c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#22 0x00007f6fdf08abff in QEventDispatcherGlib::processEvents (this=0x18f7f70, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#23 0x00007f6fde57164f in QGuiEventDispatcherGlib::processEvents (this=0xc07a070, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#24 0x00007f6fdf060de2 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#25 0x00007f6fdf0611b4 in QEventLoop::exec (this=0x7fff6daf69d0, flags=...) at kernel/qeventloop.cpp:201
#26 0x00007f6fdf063424 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#27 0x0000000000404751 in main (argc=1, argv=0x7fff6daf7148) at ../../../kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 Dario Andres 2009-09-25 02:21:15 UTC
Thanks

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