Bug 224820 - kmail crashes on start
Summary: kmail crashes on start
Status: RESOLVED DUPLICATE of bug 198561
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-29 21:43 UTC by mario.koehn
Modified: 2010-01-30 22:56 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 mario.koehn 2010-01-29 21:43:10 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 x86_64
Distribution: Ubuntu 9.10

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5  QString (this=0x0) at /usr/include/qt4/QtCore/qstring.h:711
#6  KIO::Slave::slaveProtocol (this=0x0) at ../../kio/kio/slave.cpp:188
#7  0x00007f23ec24baef in KIO::SchedulerPrivate::assignJobToSlave (this=0x243caf0, slave=0x0, job=0x24d6260) at ../../kio/kio/scheduler.cpp:958
#8  0x00007f23f3a4167a in KMail::SearchJob::searchCompleteFolder (this=0x24e3ed0) at ../../kmail/searchjob.cpp:95
#9  0x00007f23f3869a1f in KMFolderImap::search (this=0x249fb20, pattern=0x243a270) at ../../kmail/kmfolderimap.cpp:2412
#10 0x00007f23f39a6097 in KMSearch::slotProcessNextBatch (this=0x2446ed0) at ../../kmail/kmfoldersearch.cpp:272
#11 0x00007f23f39aa4f0 in KMSearch::qt_metacall (this=0x2446ed0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff226bce00) at ./kmfoldersearch.moc:79
#12 0x00007f23f23f7ddc in QMetaObject::activate (sender=0x2445320, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3113
#13 0x00007f23f23f1d83 in QObject::event (this=0x2445320, e=0x0) at kernel/qobject.cpp:1075
#14 0x00007f23f2875efc in QApplicationPrivate::notify_helper (this=0x22308a0, receiver=0x2445320, e=0x7fff226bd400) at kernel/qapplication.cpp:4056
#15 0x00007f23f287d1ce in QApplication::notify (this=0x7fff226bd870, receiver=0x2445320, e=0x7fff226bd400) at kernel/qapplication.cpp:4021
#16 0x00007f23f4638ab6 in KApplication::notify (this=0x7fff226bd870, receiver=0x2445320, event=0x7fff226bd400) at ../../kdeui/kernel/kapplication.cpp:302
#17 0x00007f23f23e2c2c in QCoreApplication::notifyInternal (this=0x7fff226bd870, receiver=0x2445320, event=0x7fff226bd400) at kernel/qcoreapplication.cpp:610
#18 0x00007f23f240d862 in QCoreApplication::sendEvent (this=0x21be5a0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#19 QTimerInfoList::activateTimers (this=0x21be5a0) at kernel/qeventdispatcher_unix.cpp:572
#20 0x00007f23f240b25d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#21 0x00007f23e967bbce in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#22 0x00007f23e967f598 in ?? () from /lib/libglib-2.0.so.0
#23 0x00007f23e967f6c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#24 0x00007f23f240b1a6 in QEventDispatcherGlib::processEvents (this=0x2187930, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#25 0x00007f23f290a4be in QGuiEventDispatcherGlib::processEvents (this=0x7fff226bcac0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#26 0x00007f23f23e1532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#27 0x00007f23f23e1904 in QEventLoop::exec (this=0x7fff226bd6a0, flags=) at kernel/qeventloop.cpp:201
#28 0x00007f23f23e3ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#29 0x0000000000402fe9 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kmail/main.cpp:146

This bug may be a duplicate of or related to bug 222179

Reported using DrKonqi
Comment 1 Dario Andres 2010-01-30 22:56:24 UTC
Merging with bug 198561 which has a similar backtrace (seems to be the same root issue)
Regards

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