Bug 234367 - repeat of kMail segmentation fault bug
Summary: repeat of kMail segmentation fault bug
Status: RESOLVED DUPLICATE of bug 198561
Alias: None
Product: kmail
Classification: Applications
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-04-14 18:20 UTC by bernd
Modified: 2010-05-27 15:04 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 bernd 2010-04-14 18:20:15 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:
its a 100% repeat of my earlier bug report, happen now each time i try to open kMail 

 -- 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  0x00007f7b4c76ed3f in KIO::SchedulerPrivate::assignJobToSlave (this=0xfe2960, slave=0x0, job=0xed1560) at ../../kio/kio/scheduler.cpp:1073
#8  0x00007f7b515a2d6a in KMail::SearchJob::searchCompleteFolder (this=0x1035850) at ../../kmail/searchjob.cpp:95
#9  0x00007f7b513cdf38 in KMFolderImap::search (this=0xf7fba0, pattern=0xe1fa90) at ../../kmail/kmfolderimap.cpp:2403
#10 0x00007f7b5150b6d7 in KMSearch::slotProcessNextBatch (this=0x1014a40) at ../../kmail/kmfoldersearch.cpp:272
#11 0x00007f7b5150c840 in KMSearch::qt_metacall (this=0x1014a40, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff2ccd8c20) at ./kmfoldersearch.moc:85
#12 0x00007f7b4fde3e3f in QMetaObject::activate (sender=0xfe62c0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x1011330) at kernel/qobject.cpp:3293
#13 0x00007f7b4fde0a63 in QObject::event (this=0xfe62c0, e=0x7fff2ccd9370) at kernel/qobject.cpp:1212
#14 0x00007f7b502a422c in QApplicationPrivate::notify_helper (this=0xbf9d60, receiver=0xfe62c0, e=0x7fff2ccd9370) at kernel/qapplication.cpp:4300
#15 0x00007f7b502aa6fb in QApplication::notify (this=0x7fff2ccd97e0, receiver=0xfe62c0, e=0x7fff2ccd9370) at kernel/qapplication.cpp:4183
#16 0x00007f7b523a6526 in KApplication::notify (this=0x7fff2ccd97e0, receiver=0xfe62c0, event=0x7fff2ccd9370) at ../../kdeui/kernel/kapplication.cpp:302
#17 0x00007f7b4fdd106c in QCoreApplication::notifyInternal (this=0x7fff2ccd97e0, receiver=0xfe62c0, event=0x7fff2ccd9370) at kernel/qcoreapplication.cpp:704
#18 0x00007f7b4fdfdd42 in QCoreApplication::sendEvent (this=0xb54d80) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 QTimerInfoList::activateTimers (this=0xb54d80) at kernel/qeventdispatcher_unix.cpp:603
#20 0x00007f7b4fdfa824 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#21 0x00007f7b46e3a8c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#22 0x00007f7b46e3e748 in ?? () from /lib/libglib-2.0.so.0
#23 0x00007f7b46e3e8fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#24 0x00007f7b4fdfa513 in QEventDispatcherGlib::processEvents (this=0xb0c000, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#25 0x00007f7b5035446e in QGuiEventDispatcherGlib::processEvents (this=0x7fff2ccd88e0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#26 0x00007f7b4fdcf992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#27 0x00007f7b4fdcfd6c in QEventLoop::exec (this=0x7fff2ccd9610, flags=) at kernel/qeventloop.cpp:201
#28 0x00007f7b4fdd3aab 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

This bug may be a duplicate of or related to bug 234366.

Possible duplicates by query: bug 234366, bug 233715.

Reported using DrKonqi
Comment 1 bernd 2010-04-23 20:41:26 UTC
One additional information which i hope might be helpful, is that a repeatable and reliable way to make kMail failing is simply to disconnect the internet connection. after re-establishing the connection kMail won't be able to update any IMAP mail accounts and sometimes corrupts the mail folder by repeating the same email over and over again
Comment 2 Jonathan Thomas 2010-05-27 15:04:24 UTC

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