| Summary: | Kmail crashes after getting stuck loading an imap account / on start / when performing a search [null KIO::Slave::slaveProtocol, KIO::Scheduler::*, KMail::SearchJob::searchCompleteFolder] | ||
|---|---|---|---|
| Product: | [Applications] kmail2 | Reporter: | Ralph Janke <txwikinger> |
| Component: | search | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | andreas.petzold+kdebugs, andresbajotierra, anssi.hannula, arthur, bernddude, bjoern, david.heremans, davidak, diseberg, Dr.Allcome, eljefedelito, emmanuel_legrand, his.arnaud1, kdenis, m.uebelacker, mario.koehn, montel, pachkov, petrustris, reeves.87, tbe, tcaswell, toralf.foerster, tpenya, urodelomutante |
| Priority: | NOR | Keywords: | triaged |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi Crash information |
||
(In reply to comment #1) > Could be related to bug 91617 Looks like mAccount->slave() is returning a NULL pointer. excerpt from SearchJob::searchCompleteFolder where problem originates. KIO::SimpleJob *job = KIO::special( url, packedArgs, KIO::HideProgressInfo ); if ( mFolder->imapPath() != QString("/") ) { // the "/ folder" of an imap account makes the kioslave stall KIO::Scheduler::assignJobToSlave(mAccount->slave(), job); connect( job, SIGNAL(infoMessage(KJob*,const QString&,const QString&)), SLOT(slotSearchData(KJob*,const QString&,const QString&)) ); connect( job, SIGNAL(result(KJob *)), SLOT(slotSearchResult(KJob *)) ); } In my case I got a connection error immediately before the crash. The crash I got was on KDE 4.3.2 after searching for message with a particular subject. The search returned over 400 messages. Which tried to move to the IMAP trash it got most the way finished reported the connection error then crashed shortly after that. *** Bug 224820 has been marked as a duplicate of this bug. *** *** Bug 231240 has been marked as a duplicate of this bug. *** - Could you update to KDE SC 4.3.5 or 4.4.1 and check if this still happens ? Regards *** Bug 233936 has been marked as a duplicate of this bug. *** *** Bug 233715 has been marked as a duplicate of this bug. *** Judging from the new duplicates it still happens in KDE 4.4.2 *** Bug 233579 has been marked as a duplicate of this bug. *** *** Bug 234540 has been marked as a duplicate of this bug. *** Hello everybody Updating to Version KDE 4.4.3 did not fix the issue for me. If you need more data on this please let me know. At the moment this is for me a show stopper. I cannot use email on this client. Does have anybody some directions for me on howto resolve this or any help on howto get my client up an running again without loosing my local stored mails and data, please. Thank you in advanced. Kind regards, Dr.Allcome *** Bug 234366 has been marked as a duplicate of this bug. *** *** Bug 236520 has been marked as a duplicate of this bug. *** *** Bug 234367 has been marked as a duplicate of this bug. *** I'm getting this exact problem. Must I remove the settings folder and re-add all my accounts, etc.? (In reply to comment #16) > I'm getting this exact problem. Must I remove the settings folder and re-add > all my accounts, etc.? Removing my ~/.kde/share/apps/kmail folder worked and all my account settings remained intact, so I wonder where those are stored. *** Bug 242570 has been marked as a duplicate of this bug. *** *** Bug 246617 has been marked as a duplicate of this bug. *** *** Bug 245452 has been marked as a duplicate of this bug. *** *** Bug 248011 has been marked as a duplicate of this bug. *** *** Bug 252023 has been marked as a duplicate of this bug. *** Created attachment 52380 [details]
New crash information added by DrKonqi
kontact (4.4.6) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0
- What I was doing when the application crashed:
Searching by subject in my inbox folder (IMAP account)
-- Backtrace (Reduced):
#6 QString (this=0x0) at /usr/include/qt4/QtCore/qstring.h:727
#7 KIO::Slave::protocol (this=0x0) at ../../kio/kio/slave.cpp:181
#8 0x00007fb4b6dad8a9 in KIO::SchedulerPrivate::assignJobToSlave (this=0x1797fa0, slave=0x0, job=0x6ba74b0) at ../../kio/kio/scheduler.cpp:1205
#9 0x00007fb49c82dc0a in KMail::SearchJob::searchCompleteFolder (this=0x6b60ad0) at ../../kmail/searchjob.cpp:95
#10 0x00007fb49c650168 in KMFolderImap::search (this=0x1b86bf0, pattern=0x34d91c0) at ../../kmail/kmfolderimap.cpp:2408
Created attachment 52649 [details]
New crash information added by DrKonqi
kmail (1.13.5) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0
- What I was doing when the application crashed:
Searching imap (free.fr) mail ; there was first a « wrong caracter search message » as i enter the word « coopérative » (maybe the « é »), then i tried « cooperative » and then Kmail crashes.
-- Backtrace (Reduced):
#7 QString (this=0x0) at /usr/include/qt4/QtCore/qstring.h:727
#8 KIO::Slave::protocol (this=0x0) at ../../kio/kio/slave.cpp:181
#9 0xb52e85f1 in KIO::SchedulerPrivate::assignJobToSlave (this=0x8b694d0, slave=0x0, job=0x903e498) at ../../kio/kio/scheduler.cpp:1205
#10 0xb52e8721 in KIO::Scheduler::assignJobToSlave (slave=0x0, job=0x903e498) at ../../kio/kio/scheduler.cpp:816
#11 0xb6ec91e3 in KMail::SearchJob::searchCompleteFolder (this=0x9391518) at ../../kmail/searchjob.cpp:95
[Comment from a bug triager] I wonder if this bug could have been solved with the commit from bug 255969 comment 1: http://websvn.kde.org/?view=rev&revision=1192678 [Comment from a bug triager] From bug 255400: - What I was doing when the application crashed: After a fulltext search in a IMAP Folder (Exchange 2007) the same error message every minute: Search failed "Command Error. 11". After that errormessage, kmail dies randomly with the attached backtrace From bug 257022: - What I was doing when the application crashed: I was searching for 'prudential' and got no results; changed the search term and KMail crashed. [Comment from a bug triager] From bug 255400: Delete the file "~/.kde4/share/apps/kmail/search/Last Search" stopped the error popping up, a new search leads to the same error as before, until the file is deleted again. *** Bug 255400 has been marked as a duplicate of this bug. *** *** Bug 257022 has been marked as a duplicate of this bug. *** *** Bug 261744 has been marked as a duplicate of this bug. *** [Comment from a bug triager] We could assume this is fixed by http://websvn.kde.org/?revision=1192678&view=revision as the latest duplicates are from KDE SC 4.5.2 time (not really using the latest kdepim where the bug was fixed). @All: Please try to reproduce with KMail 1.13.6 (from kdepim 4.4.10) and reopen this report if you get the same backtrace. Created attachment 58617 [details]
New crash information added by DrKonqi
kmail (1.13.5) on KDE Platform 4.6.1 (4.6.1) using Qt 4.7.0
kMAIL crashes on startup every time. I have one account, it uses IMAP.
-- Backtrace (Reduced):
#6 0x00007f7c4ebcd5dc in KMail::SearchJob::searchCompleteFolder (this=0x2208ec0) at ../../kmail/searchjob.cpp:87
#7 0x00007f7c4e9f0e58 in KMFolderImap::search (this=0x221ef90, pattern=0x20887e0) at ../../kmail/kmfolderimap.cpp:2408
#8 0x00007f7c4eb34c6d in KMSearch::slotProcessNextBatch (this=0x22d4820) at ../../kmail/kmfoldersearch.cpp:272
#9 0x00007f7c4eb34dc0 in KMSearch::qt_metacall (this=0x22d4820, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff396a9ad0) at ./kmfoldersearch.moc:85
[...]
#11 0x00007f7c4d32a8f9 in QObject::event (this=0x214d9a0, e=0x0) at kernel/qobject.cpp:1183
Created attachment 61523 [details]
New crash information added by DrKonqi
kontact (4.4.11) on KDE Platform 4.6.4 (4.6.4) using Qt 4.7.3
- What I was doing when the application crashed:
An IMAP search went wrong and now kmail is crashing again and again.
-- Backtrace (Reduced):
#7 QString (this=0x0) at /usr/include/QtCore/qstring.h:728
#8 KIO::Slave::protocol (this=0x0) at /usr/src/debug/kdelibs-4.6.4/kio/kio/slave.cpp:182
#9 0x069f3392 in KIO::SchedulerPrivate::assignJobToSlave (this=0x9398498, slave=0x0, job=0x9fb9a20) at /usr/src/debug/kdelibs-4.6.4/kio/kio/scheduler.cpp:1236
#10 0x069f34eb in KIO::Scheduler::assignJobToSlave (slave=0x0, job=0x9fb9a20) at /usr/src/debug/kdelibs-4.6.4/kio/kio/scheduler.cpp:822
#11 0x0591b116 in KMail::SearchJob::searchSingleMessage (this=0x97593f0) at /usr/src/debug/kdepim-4.4.11.1/kmail/searchjob.cpp:395
I'm on holiday, you're mail will be read when I'm back 25th of July. Reassigning to kmail2 as it was reproduce with Kontact 4.4.x, see comment #34. Is this still valid with Kmail 4.8.5 or later? Created attachment 91261 [details]
Crash information
It has only happened two times, when kmail starts. It spends much time searching for new mail, some minutes, and then crash.
It also happened taking too much time searching but with no crash. Then it takes several seconds changing from folder to folder.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |
Application that crashed: kmail Version of the application: 1.11.90 KDE Version: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2)) Qt Version: 4.5.0 Operating System: Linux 2.6.28-13-generic i686 Distribution: Ubuntu 9.04 What I was doing when the application crashed: Kmail got stuck on 79% loading an imap account. After clicking abort, it got stuck there too. Eventually it crashed with segmentation fault. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #6 KIO::Slave::slaveProtocol (this=0x0) at /usr/include/qt4/QtCore/qstring.h:711 #7 0xb6e5b039 in KIO::SchedulerPrivate::assignJobToSlave (this=0xa584130, slave=0x0, job=0xcb61658) at /build/buildd/kde4libs-4.2.90/kio/kio/scheduler.cpp:958 #8 0xb6e5b3f6 in KIO::Scheduler::assignJobToSlave (slave=0x0, job=0xcb61658) at /build/buildd/kde4libs-4.2.90/kio/kio/scheduler.cpp:304 #9 0xb773c20d in KMail::SearchJob::searchCompleteFolder (this=0xc85e098) at /build/buildd/kdepim-4.2.90/kmail/searchjob.cpp:95 #10 0xb769c734 in KMail::FolderJob::start (this=0x0) at /build/buildd/kdepim-4.2.90/kmail/folderjob.cpp:106 #11 0xb753e769 in KMFolderImap::search (this=0xa0d91f0, pattern=0xd0b5478) at /build/buildd/kdepim-4.2.90/kmail/kmfolderimap.cpp:2412 #12 0xb7697ff4 in KMSearch::slotProcessNextBatch (this=0xb1072c0) at /build/buildd/kdepim-4.2.90/kmail/kmfoldersearch.cpp:272 #13 0xb769816b in KMSearch::qt_metacall (this=0xb1072c0, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbf877928) at /build/buildd/kdepim-4.2.90/obj-i486-linux-gnu/kmail/kmfoldersearch.moc:79 #14 0xb5febca8 in QMetaObject::activate (sender=0xb68b638, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3069 #15 0xb5fec932 in QMetaObject::activate (sender=0xb68b638, m=0xb60c8904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3143 #16 0xb6027717 in QTimer::timeout (this=0xb68b638) at .moc/release-shared/moc_qtimer.cpp:128 #17 0xb5ff16fe in QTimer::timerEvent (this=0xb68b638, e=0xbf877dac) at kernel/qtimer.cpp:261 #18 0xb5fe615f in QObject::event (this=0xb68b638, e=0xbf877dac) at kernel/qobject.cpp:1082 #19 0xb6283e9c in QApplicationPrivate::notify_helper (this=0x9e48bb0, receiver=0xb68b638, e=0xbf877dac) at kernel/qapplication.cpp:4084 #20 0xb628c19e in QApplication::notify (this=0xbf8780c8, receiver=0xb68b638, e=0xbf877dac) at kernel/qapplication.cpp:3631 #21 0xb7e78e8d in KApplication::notify (this=0xbf8780c8, receiver=0xb68b638, event=0xbf877dac) at /build/buildd/kde4libs-4.2.90/kdeui/kernel/kapplication.cpp:302 #22 0xb5fd5a3b in QCoreApplication::notifyInternal (this=0xbf8780c8, receiver=0xb68b638, event=0xbf877dac) at kernel/qcoreapplication.cpp:602 #23 0xb6004d71 in QTimerInfoList::activateTimers (this=0x9e48ca4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #24 0xb60014e0 in timerSourceDispatch (source=0x9e48c70) at kernel/qeventdispatcher_glib.cpp:164 #25 0xb43a9b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #26 0xb43ad0eb in ?? () from /usr/lib/libglib-2.0.so.0 #27 0xb43ad268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #28 0xb6001438 in QEventDispatcherGlib::processEvents (this=0x9e46368, flags={i = -1081639128}) at kernel/qeventdispatcher_glib.cpp:323 #29 0xb6325365 in QGuiEventDispatcherGlib::processEvents (this=0x9e46368, flags={i = -1081639080}) at kernel/qguieventdispatcher_glib.cpp:202 #30 0xb5fd406a in QEventLoop::processEvents (this=0xbf877fd0, flags={i = -1081639016}) at kernel/qeventloop.cpp:149 #31 0xb5fd44aa in QEventLoop::exec (this=0xbf877fd0, flags={i = -1081638952}) at kernel/qeventloop.cpp:200 #32 0xb5fd6959 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880 #33 0xb6283d17 in QApplication::exec () at kernel/qapplication.cpp:3553 #34 0x0804a7b0 in main (argc=) at /build/buildd/kdepim-4.2.90/kmail/main.cpp:146 Reported using DrKonqi