Bug 234366

Summary: kMail crashes with segmentation fault error
Product: [Unmaintained] kmail Reporter: bernd <bernddude>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: bernddude, kde, MurzNN
Priority: NOR    
Version: 1.13.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description bernd 2010-04-14 18:11:17 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-20-generic x86_64
Distribution: Ubuntu lucid (development branch)

-- Information about the crash:
This erorr does occure quite frequently on my system, it does seem to be not just a kMail issue but also does seem to happen with other KDE applications for example rkward (and R GUI)
my system is lucid lynx beta II (but the problem occured befoore under Karmic Koala as well)

The crash can be reproduced some of the time.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#5  QString (this=0x0) at /usr/include/qt4/QtCore/qstring.h:714
#6  KIO::Slave::protocol (this=0x0) at ../../kio/kio/slave.cpp:176
#7  0x00007f3921e8cd3f in KIO::SchedulerPrivate::assignJobToSlave (this=0x25d82c0, slave=0x0, job=0x25dc940) at ../../kio/kio/scheduler.cpp:1073
#8  0x00007f3926cc0d6a in KMail::SearchJob::searchCompleteFolder (this=0x25b67d0) at ../../kmail/searchjob.cpp:95
#9  0x00007f3926aebf38 in KMFolderImap::search (this=0x250fac0, pattern=0x2506040) at ../../kmail/kmfolderimap.cpp:2403
#10 0x00007f3926c296d7 in KMSearch::slotProcessNextBatch (this=0x258c3d0) at ../../kmail/kmfoldersearch.cpp:272
#11 0x00007f3926c2a840 in KMSearch::qt_metacall (this=0x258c3d0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff7e265ac0) at ./kmfoldersearch.moc:85
#12 0x00007f3925501e3f in QMetaObject::activate (sender=0x259acc0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x24fa670) at kernel/qobject.cpp:3293
#13 0x00007f39254fea63 in QObject::event (this=0x259acc0, e=0x7fff7e266210) at kernel/qobject.cpp:1212
#14 0x00007f39259c222c in QApplicationPrivate::notify_helper (this=0x2195cf0, receiver=0x259acc0, e=0x7fff7e266210) at kernel/qapplication.cpp:4300
#15 0x00007f39259c86fb in QApplication::notify (this=0x7fff7e266680, receiver=0x259acc0, e=0x7fff7e266210) at kernel/qapplication.cpp:4183
#16 0x00007f3927ac4526 in KApplication::notify (this=0x7fff7e266680, receiver=0x259acc0, event=0x7fff7e266210) at ../../kdeui/kernel/kapplication.cpp:302
#17 0x00007f39254ef06c in QCoreApplication::notifyInternal (this=0x7fff7e266680, receiver=0x259acc0, event=0x7fff7e266210) at kernel/qcoreapplication.cpp:704
#18 0x00007f392551bd42 in QCoreApplication::sendEvent (this=0x20f0f40) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 QTimerInfoList::activateTimers (this=0x20f0f40) at kernel/qeventdispatcher_unix.cpp:603
#20 0x00007f3925518824 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#21 0x00007f391c5588c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#22 0x00007f391c55c748 in ?? () from /lib/libglib-2.0.so.0
#23 0x00007f391c55c8fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#24 0x00007f3925518513 in QEventDispatcherGlib::processEvents (this=0x20a8000, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#25 0x00007f3925a7246e in QGuiEventDispatcherGlib::processEvents (this=0x7fff7e265780, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#26 0x00007f39254ed992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#27 0x00007f39254edd6c in QEventLoop::exec (this=0x7fff7e2664b0, flags=) at kernel/qeventloop.cpp:201
#28 0x00007f39254f1aab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#29 0x0000000000403482 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kmail/main.cpp:156

Possible duplicates by query: bug 233715.

Reported using DrKonqi
Comment 1 bernd 2010-04-14 19:01:54 UTC
repeat via command line kMail start :
here is what i get (in 10 out of 10 cases) when i repeat a kMail start from the command line 

bernd@ubuntu:~$ kmail
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kmail(1714) KMFolderMgr::removeFolderAux: Can not find parent folder for  Last Search 
*** KMail got signal 11 (Crashing)
<unknown program name>(1713)/: Communication problem with  "kmail" , it probably crashed. 
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " 

bernd@ubuntu:~$ KCrash: Application 'kmail' crashing...
sock_file=/home/bernd/.kde/socket-ubuntu/kdeinit4__0
Comment 2 Nicolas L. 2010-04-28 11:33:54 UTC
*** Bug 234779 has been marked as a duplicate of this bug. ***
Comment 3 Nicolas L. 2010-04-28 14:27:08 UTC

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