Bug 181267 - KMail crashed at startup
Summary: KMail crashed at startup
Status: RESOLVED DUPLICATE of bug 153411
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.10.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-19 08:55 UTC by jde3
Modified: 2009-03-19 01:11 UTC (History)
0 users

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 jde3 2009-01-19 08:55:04 UTC
Version:           1.10.3 (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

Here is the report I got :

Application : KMail (kmail), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb41b06c0 (LWP 1349)]
[New Thread 0xaf80cb90 (LWP 25985)]
[KCrash handler]
#6  0xb7834ea1 in KMail::ISubject::notify (this=0xa50cba4)
    at /build/buildd/kdepim-4.1.3/kmail/isubject.cpp:30
#7  0xb74a1646 in KMMessage::updateBodyPart (this=0xa50cb88, partSpecifier=
      {static null = {<No data fields>}, static shared_null = {ref = {_q_value = 23563}, alloc = 0, size = 0, data = 0xb7fa29ba, clean = 0, simpletext = 0, righttoleft = 0, asciiCache = 0, capacity = 0, reserved = 0, array = {0}}, static shared_empty = {ref = {_q_value = 857}, alloc = 0, size = 0, data = 0xb7fa29ce, clean = 0, simpletext = 0, righttoleft = 0, asciiCache = 0, capacity = 0, reserved = 0, array = {0}}, d = 0xbfcd56bc, static codecForCStrings = 0x0}, 
    data=@0xa91a140) at /build/buildd/kdepim-4.1.3/kmail/kmmessage.cpp:4178
#8  0xb780895d in KMail::ImapJob::slotGetMessageResult (this=0xa72be48, 
    job=0x9f24140) at /build/buildd/kdepim-4.1.3/kmail/imapjob.cpp:435
#9  0xb780cee4 in KMail::ImapJob::qt_metacall (this=0xa72be48, 
    _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfcd57cc)
    at /build/buildd/kdepim-4.1.3/obj-i486-linux-gnu/kmail/imapjob.moc:81
#10 0xb7ed1a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb7ed27e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb7c36283 in KJob::result (this=0x9f24140, _t1=0x9f24140)
    at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/kdecore/kjob.moc:186
#13 0xb7c36792 in KJob::emitResult (this=0x9f24140)
    at /build/buildd/kde4libs-4.1.3/kdecore/jobs/kjob.cpp:290
#14 0xb53d08c5 in KIO::SimpleJob::slotFinished (this=0x9f24140)
    at /build/buildd/kde4libs-4.1.3/kio/kio/job.cpp:498
#15 0xb53d7353 in KIO::TransferJob::slotFinished (this=0x9f24140)
    at /build/buildd/kde4libs-4.1.3/kio/kio/job.cpp:967
#16 0xb53d812b in KIO::TransferJob::qt_metacall (this=0x9f24140, 
    _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbfcd5a08)
    at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/kio/jobclasses.moc:336
#17 0xb7ed1a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#18 0xb7ed27e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#19 0xb5496f27 in KIO::SlaveInterface::finished (this=0x9c139c0)
    at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/kio/slaveinterface.moc:161
#20 0xb549ab97 in KIO::SlaveInterface::dispatch (this=0x9c139c0, _cmd=104, 
    rawdata=@0xbfcd5bd4)
    at /build/buildd/kde4libs-4.1.3/kio/kio/slaveinterface.cpp:175
#21 0xb54976a7 in KIO::SlaveInterface::dispatch (this=0x9c139c0)
    at /build/buildd/kde4libs-4.1.3/kio/kio/slaveinterface.cpp:90
#22 0xb54876cd in KIO::Slave::gotInput (this=0x9c139c0)
    at /build/buildd/kde4libs-4.1.3/kio/kio/slave.cpp:322
#23 0xb548a113 in KIO::Slave::qt_metacall (this=0x9c139c0, 
    _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfcd5ce8)
    at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/kio/slave.moc:75
#24 0xb7ed1a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#25 0xb7ed27e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#26 0xb53978f7 in KIO::Connection::readyRead (this=0xa954d00)
    at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/kio/connection.moc:84
#27 0xb53999c9 in KIO::ConnectionPrivate::dequeue (this=0xa47ab88)
    at /build/buildd/kde4libs-4.1.3/kio/kio/connection.cpp:82
#28 0xb5399b56 in KIO::Connection::qt_metacall (this=0xa954d00, 
    _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x9dd8ae8)
    at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/kio/connection.moc:72
#29 0xb7ecabfb in QMetaCallEvent::placeMetaCall ()
   from /usr/lib/libQtCore.so.4
#30 0xb7ecc771 in QObject::event () from /usr/lib/libQtCore.so.4
#31 0xb67ab8ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#32 0xb67b372e in QApplication::notify () from /usr/lib/libQtGui.so.4
#33 0xb7142b2d in KApplication::notify (this=0xbfcd6538, receiver=0xa954d00, 
    event=0xa57a768)
    at /build/buildd/kde4libs-4.1.3/kdeui/kernel/kapplication.cpp:311
#34 0xb7ebce61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#35 0xb7ebdae5 in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#36 0xb7ebdcdd in QCoreApplication::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#37 0xb7ee782f in ?? () from /usr/lib/libQtCore.so.4
#38 0xb63716f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#39 0xb6374da3 in ?? () from /usr/lib/libglib-2.0.so.0
#40 0xb6374f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#41 0xb7ee7478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#42 0xb6845ea5 in ?? () from /usr/lib/libQtGui.so.4
#43 0xb7ebb52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#44 0xb7ebb6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#45 0xb7ebdda5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#46 0xb67ab767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#47 0x0804a6c0 in main (argc=-1212928472, argv=0xa750760)
    at /build/buildd/kdepim-4.1.3/kmail/main.cpp:146
#0  0xb7fd4430 in __kernel_vsyscall ()
Comment 1 Jaime Torres 2009-01-19 09:37:57 UTC
Thank you for taking the time to report this bug and helping to make KDE better. This particular bug has already been reported and is a duplicate of bug 153411, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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