Bug 210289 - Run kmail, login to account and double click on mail to open it. CRASH!
Summary: Run kmail, login to account and double click on mail to open it. CRASH!
Status: RESOLVED DUPLICATE of bug 193891
Alias: None
Product: kmail
Classification: Unmaintained
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-10-12 10:20 UTC by paul s. romanchenko
Modified: 2009-10-12 10:28 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description paul s. romanchenko 2009-10-12 10:20:20 UTC
Application that crashed: kmail
Version of the application: 1.12.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.31-trunk-amd64 x86_64
Distribution: Debian GNU/Linux 5.0 (lenny)

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#5  DwEntity::Headers (this=0x1187) at ../../mimelib/entity.cpp:241
#6  0x00007fd5ebc30341 in KMMessage::rawHeaderField (this=0x37477c0, name=...) at ../../kmail/kmmessage.cpp:1958
#7  0x00007fd5ebc32595 in KMMessage::from (this=0x37477c0) at ../../kmail/kmmessage.cpp:1710
#8  0x00007fd5ebe88450 in KMail::FancyHeaderStyle::format (this=<value optimized out>, message=0x37477c0, strategy=0x16a34b0, vCardName=..., printing=24, topLevel=true)
    at ../../kmail/headerstyle.cpp:457
#9  0x00007fd5ebd23b55 in KMReaderWin::writeMsgHeader (this=0x1a50850, aMsg=0x37477c0, hasVCard=false, topLevel=4) at ../../kmail/kmreaderwin.cpp:1783
#10 0x00007fd5ebd2a6f0 in KMReaderWin::parseMsg (this=0x1a50850, aMsg=0x37477c0) at ../../kmail/kmreaderwin.cpp:1668
#11 0x00007fd5ebd199fa in KMReaderWin::displayMessage (this=0x1a50850) at ../../kmail/kmreaderwin.cpp:1605
#12 0x00007fd5ebd19be5 in KMReaderWin::updateReaderWin (this=0x1a50850) at ../../kmail/kmreaderwin.cpp:1545
#13 0x00007fd5ebd259fd in KMReaderWin::qt_metacall (this=0x1a50850, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff5e7cfa20) at ./kmreaderwin.moc:168
#14 0x00007fd5eb513df2 in QMetaObject::activate (sender=0x1a508f8, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x6d6f72) at kernel/qobject.cpp:3112
#15 0x00007fd5eb50e353 in QObject::event (this=0x1a508f8, e=0x37477c0) at kernel/qobject.cpp:1074
#16 0x00007fd5ea97701d in QApplicationPrivate::notify_helper (this=0x1438f10, receiver=0x1a508f8, e=0x7fff5e7d00d0) at kernel/qapplication.cpp:4065
#17 0x00007fd5ea97f07a in QApplication::notify (this=0x7fff5e7d0790, receiver=0x1a508f8, e=0x7fff5e7d00d0) at kernel/qapplication.cpp:4030
#18 0x00007fd5ecbb60db in KApplication::notify (this=0x7fff5e7d0790, receiver=0x1a508f8, event=0x7fff5e7d00d0) at ../../kdeui/kernel/kapplication.cpp:302
#19 0x00007fd5eb4fec9c in QCoreApplication::notifyInternal (this=0x7fff5e7d0790, receiver=0x1a508f8, event=0x7fff5e7d00d0) at kernel/qcoreapplication.cpp:610
#20 0x00007fd5eb52b2c6 in QCoreApplication::sendEvent (this=0x1439930) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#21 QTimerInfoList::activateTimers (this=0x1439930) at kernel/qeventdispatcher_unix.cpp:580
#22 0x00007fd5eb52b468 in QEventDispatcherUNIX::processEvents (this=0x1405170, flags=...) at kernel/qeventdispatcher_unix.cpp:916
#23 0x00007fd5eaa0eee2 in QEventDispatcherX11::processEvents (this=0x1405170, flags=...) at kernel/qeventdispatcher_x11.cpp:152
#24 0x00007fd5eb4fd562 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#25 0x00007fd5eb4fd934 in QEventLoop::exec (this=0x7fff5e7d05e0, flags=...) at kernel/qeventloop.cpp:201
#26 0x00007fd5eb4ffba4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#27 0x0000000000402fab in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kmail/main.cpp:146

Reported using DrKonqi
Comment 1 Christophe Marin 2009-10-12 10:28:28 UTC

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