Bug 224934 - Kmail crashed while reading mail
Summary: Kmail crashed while reading mail
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:
Depends on:
Blocks:
 
Reported: 2010-01-30 23:40 UTC by lacrosse.dante
Modified: 2018-09-04 18: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 lacrosse.dante 2010-01-30 23:40:45 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.2
Operating System: Linux 2.6.31-17-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
Kmail just crashed while reading a message

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6  0x00e90f3a in ?? () from /usr/lib/libkmailprivate.so.4
#7  0x011cd8f0 in ?? () from /usr/lib/libkmailprivate.so.4
#8  0x011d260f in ?? () from /usr/lib/libkmailprivate.so.4
#9  0x006d6263 in QMetaObject::activate (sender=0x8e0f888, from_signal_index=7, to_signal_index=7, argv=0xbff6b958) at kernel/qobject.cpp:3113
#10 0x006d6ec2 in QMetaObject::activate (sender=0x8e0f888, m=0x34fd68, local_signal_index=3, argv=0xbff6b958) at kernel/qobject.cpp:3187
#11 0x001e9fe3 in KJob::result (this=0x8e0f888, _t1=0x8e0f888) at ./kjob.moc:188
#12 0x001ea469 in KJob::emitResult (this=0x8e0f888) at ../../kdecore/jobs/kjob.cpp:304
#13 0x01a71660 in KIO::SimpleJob::slotFinished (this=0x8e0f888) at ../../kio/kio/job.cpp:477
#14 0x01a71b7a in KIO::TransferJob::slotFinished (this=0x8e0f888) at ../../kio/kio/job.cpp:948
#15 0x01a6f8a3 in KIO::TransferJob::qt_metacall (this=0x8e0f888, _c=QMetaObject::InvokeMetaMethod, _id=47, _a=0xbff6bbbc) at ./jobclasses.moc:343
#16 0x006d6263 in QMetaObject::activate (sender=0x8e41288, from_signal_index=8, to_signal_index=8, argv=0x0) at kernel/qobject.cpp:3113
#17 0x006d6ec2 in QMetaObject::activate (sender=0x8e41288, m=0x1c23f64, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3187
#18 0x01b3b557 in KIO::SlaveInterface::finished (this=0x8e41288) at ./slaveinterface.moc:165
#19 0x01b3f44d in KIO::SlaveInterface::dispatch (this=0x8e41288, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175
#20 0x01b3ba13 in KIO::SlaveInterface::dispatch (this=0x8e41288) at ../../kio/kio/slaveinterface.cpp:91
#21 0x01b2daea in KIO::Slave::gotInput (this=0x8e41288) at ../../kio/kio/slave.cpp:322
#22 0x01b2fee3 in KIO::Slave::qt_metacall (this=0x8e41288, _c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbff6be9c) at ./slave.moc:76
#23 0x006d6263 in QMetaObject::activate (sender=0x9261cf0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#24 0x006d6ec2 in QMetaObject::activate (sender=0x9261cf0, m=0x1c208a0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#25 0x01a37f97 in KIO::Connection::readyRead (this=0x9261cf0) at ./connection.moc:86
#26 0x01a39d5e in KIO::ConnectionPrivate::dequeue (this=0x9261d00) at ../../kio/kio/connection.cpp:82
#27 0x01a39e8e in KIO::Connection::qt_metacall (this=0x9261cf0, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0x921bc10) at ./connection.moc:73
#28 0x006cef0b in QMetaCallEvent::placeMetaCall (this=0x90bd4d0, object=0x9261cf0) at kernel/qobject.cpp:477
#29 0x006d05fe in QObject::event (this=0x9261cf0, e=0x90bd4d0) at kernel/qobject.cpp:1111
#30 0x06299f54 in QApplicationPrivate::notify_helper (this=0x86c8150, receiver=0x9261cf0, e=0x90bd4d0) at kernel/qapplication.cpp:4056
#31 0x062a167c in QApplication::notify (this=0xbff6c7d0, receiver=0x9261cf0, e=0x90bd4d0) at kernel/qapplication.cpp:3603
#32 0x00c3fbfa in KApplication::notify (this=0xbff6c7d0, receiver=0x9261cf0, event=0x90bd4d0) at ../../kdeui/kernel/kapplication.cpp:302
#33 0x006c06cb in QCoreApplication::notifyInternal (this=0xbff6c7d0, receiver=0x9261cf0, event=0x90bd4d0) at kernel/qcoreapplication.cpp:610
#34 0x006c12b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x8694fa8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#35 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8694fa8) at kernel/qcoreapplication.cpp:1247
#36 0x006c147d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#37 0x006eb3ff in QCoreApplication::sendPostedEvents (s=0x86c54b0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#38 postEventSourceDispatch (s=0x86c54b0) at kernel/qeventdispatcher_glib.cpp:210
#39 0x018b8e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#40 0x018bc730 in ?? () from /lib/libglib-2.0.so.0
#41 0x018bc863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#42 0x006eb02c in QEventDispatcherGlib::processEvents (this=0x8695180, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#43 0x0633abe5 in QGuiEventDispatcherGlib::processEvents (this=0x8695180, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#44 0x006bec79 in QEventLoop::processEvents (this=0xbff6c694, flags=) at kernel/qeventloop.cpp:149
#45 0x006bf0ca in QEventLoop::exec (this=0xbff6c694, flags=...) at kernel/qeventloop.cpp:201
#46 0x006c153f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#47 0x06299dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#48 0x0804a702 in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2010-01-31 01:19:56 UTC
- If you can reproduce the crash at will (or you experience this regularly), can you install the "kdepim-dbg" package and post a complete backtrace here? (you can get more information at http://techbase.kde.org/User:DarioAndres/Basic_Guide_about_Crash_Reporting ) Thanks
Comment 2 Andrew Crouthamel 2018-09-04 18:21:09 UTC
Hello! Sorry to be the bearer of bad news, but this version of Kmail has been unmaintained for many years so I am closing this bug. Please try using the latest version of Kmail to see if your issue persists. If it does, please submit a new bug in "kmail2". Thank you!