Bug 237422 - Kmail crash on startup
Summary: Kmail crash on startup
Status: RESOLVED DUPLICATE of bug 153411
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.13.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-12 21:36 UTC by David Masover
Modified: 2010-05-27 16:18 UTC (History)
1 user (show)

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 David Masover 2010-05-12 21:36:51 UTC
Application: kmail (1.13.2)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-22-generic x86_64
Distribution: Ubuntu 10.04 LTS

-- Information about the crash:
I did look, but can't find a duplicate. Crashed within a few seconds of startup. I haven't tried starting again.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[Current thread is 1 (Thread 0x7ffd88958820 (LWP 9457))]

Thread 2 (Thread 0x7ffd68d1a710 (LWP 9467)):
#0  0xffffffffff60017b in ?? ()
#1  0x00007ffd68d199e0 in ?? ()
#2  0x00007fff7b1ff852 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0x7ffd88958820 (LWP 9457)):
[KCrash Handler]
#5  0x00007ffd8751fa6e in KMail::ISubject::notify (this=0x1b6eac0) at ../../kmail/isubject.cpp:33
#6  0x00007ffd8721db1c in KMMessage::updateBodyPart (this=0x1b6e9f0, partSpecifier=) at ../../kmail/kmmessage.cpp:3185
#7  0x00007ffd874f73e9 in KMail::ImapJob::slotGetMessageResult (this=0x16ba730, job=<value optimized out>) at ../../kmail/imapjob.cpp:435
#8  0x00007ffd874f8f8b in KMail::ImapJob::qt_metacall (this=0x16ba730, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff7b0f3fe0) at ./imapjob.moc:88
#9  0x00007ffd85dc0e3f in QMetaObject::activate (sender=0x5610c00, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x5) at kernel/qobject.cpp:3293
#10 0x00007ffd87db2b82 in KJob::result (this=0x92a678, _t1=0x5610c00) at ./kjob.moc:194
#11 0x00007ffd87db2e20 in KJob::emitResult (this=0x5610c00) at ../../kdecore/jobs/kjob.cpp:312
#12 0x00007ffd826a4503 in KIO::SimpleJob::slotFinished (this=0x5610c00) at ../../kio/kio/job.cpp:486
#13 0x00007ffd826a4ec7 in KIO::TransferJob::slotFinished (this=0x5610c00) at ../../kio/kio/job.cpp:1058
#14 0x00007ffd826a2af1 in KIO::TransferJob::qt_metacall (this=0x5610c00, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff7b0f43e0) at ./jobclasses.moc:367
#15 0x00007ffd85dc0e3f in QMetaObject::activate (sender=0x1280ab0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x5) at kernel/qobject.cpp:3293
#16 0x00007ffd82764271 in KIO::SlaveInterface::dispatch (this=0x1280ab0, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175
#17 0x00007ffd827615e3 in KIO::SlaveInterface::dispatch (this=0x1280ab0) at ../../kio/kio/slaveinterface.cpp:91
#18 0x00007ffd82755a46 in KIO::Slave::gotInput (this=0x1280ab0) at ../../kio/kio/slave.cpp:324
#19 0x00007ffd82755c2c in KIO::Slave::qt_metacall (this=0x1280ab0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff7b0f4800) at ./slave.moc:82
#20 0x00007ffd85dc0e3f in QMetaObject::activate (sender=0x16bfce0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x5) at kernel/qobject.cpp:3293
#21 0x00007ffd826739d7 in KIO::ConnectionPrivate::dequeue (this=0x16c0400) at ../../kio/kio/connection.cpp:82
#22 0x00007ffd82673afd in KIO::Connection::qt_metacall (this=0x16bfce0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x155d3f0) at ./connection.moc:79
#23 0x00007ffd85dbdd49 in QObject::event (this=0x16bfce0, e=0x12e6ad0) at kernel/qobject.cpp:1248
#24 0x00007ffd8628122c in QApplicationPrivate::notify_helper (this=0x74d3d0, receiver=0x16bfce0, e=0x12e6ad0) at kernel/qapplication.cpp:4300
#25 0x00007ffd862876fb in QApplication::notify (this=0x7fff7b0f5420, receiver=0x16bfce0, e=0x12e6ad0) at kernel/qapplication.cpp:4183
#26 0x00007ffd88383526 in KApplication::notify (this=0x7fff7b0f5420, receiver=0x16bfce0, event=0x12e6ad0) at ../../kdeui/kernel/kapplication.cpp:302
#27 0x00007ffd85dae06c in QCoreApplication::notifyInternal (this=0x7fff7b0f5420, receiver=0x16bfce0, event=0x12e6ad0) at kernel/qcoreapplication.cpp:704
#28 0x00007ffd85db07e7 in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x6b08b0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#29 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x6b08b0) at kernel/qcoreapplication.cpp:1345
#30 0x00007ffd85dd79d3 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#31 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:276
#32 0x00007ffd7ce178c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#33 0x00007ffd7ce1b748 in ?? () from /lib/libglib-2.0.so.0
#34 0x00007ffd7ce1b8fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#35 0x00007ffd85dd7513 in QEventDispatcherGlib::processEvents (this=0x6b0000, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#36 0x00007ffd8633146e in QGuiEventDispatcherGlib::processEvents (this=0x92a678, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#37 0x00007ffd85dac992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#38 0x00007ffd85dacd6c in QEventLoop::exec (this=0x7fff7b0f5250, flags=) at kernel/qeventloop.cpp:201
#39 0x00007ffd85db0aab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#40 0x0000000000403482 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kmail/main.cpp:156

Possible duplicates by query: bug 235176, bug 233482, bug 233123, bug 232331, bug 232191.

Reported using DrKonqi
Comment 1 Jonathan Thomas 2010-05-27 16:18:31 UTC

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