Bug 180255 - After searching in an imap folder kmail crashs and all mails are lost
Summary: After searching in an imap folder kmail crashs and all mails are lost
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Unspecified
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-10 15:15 UTC by Wolfgang Mader
Modified: 2009-03-19 00:38 UTC (History)
3 users (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 Wolfgang Mader 2009-01-10 15:15:04 UTC
Version:            (using Devel)
Installed from:    Compiled sources

Hello,

Kmail is pointed to the lmap server of my university. I do not know what server is running there, but if this information becomes interesting I sure can get it. There have been 1750 Mails is this folder.  This Imap account has a few folders:
account
|- INBOX
|- INBOX.Drafts
|- INBOX.Sent
|- INBOX.Trash
|- fdm
|- privat
|- temp

I do not remember in full detail what i did, but the main actions were:
- I performed a search in the folder fdm (search in the whole message).
- Right after this first search I searched in the same folder for another keyword without closing the the search dialog in between. Kmail responded by crashing.
- I restarted Kmail and tried to open the folder fdm, but every time I click on the icon of this folder Kmail crashe (see backtrace below).

Then I checked this folder with an webclient and, tada, it turns out that all messages stored in this folder are now gone. I have found a copy of all messages under
~/.kde4/share/apps/kmail/imap/,
but I do not know if attachments as well are backed up.

Additional info:
All other folders do work as normal. I also can send and receive messages.
I also can crash Kmail by right clicking on the folder. Since diff finds differences in the two backtraces I also appended the one for the right-click-crash.


Backtrace start (left click on the icon -> open the folder):
_____________________________________________________
Application: KMail (kmail), signal SIGSEGV
[Current thread is 0 (LWP 4314)]

Thread 2 (Thread 0xb0e4fb90 (LWP 4316)):
#0  0xb7f30424 in __kernel_vsyscall ()
#1  0xb55d2352 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb63dd854 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6
#3  0xb6e9c51c in QWaitCondition::wait (this=0x9f46548, mutex=0x9f46544, time=30000) at thread/qwaitcondition_unix.cpp:80
#4  0xb6e917c6 in QThreadPoolThread::run (this=0x9f845c0) at concurrent/qthreadpool.cpp:135
#5  0xb6e9b52e in QThreadPrivate::start (arg=0x9f845c0) at thread/qthread_unix.cpp:185
#6  0xb55ce4c0 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb63cf6de in clone () from /lib/i686/cmov/libc.so.6

Thread 1 (Thread 0xb3fbe6c0 (LWP 4314)):
[KCrash Handler]
#6  0xb7418cfe in KMFolderImap::slotListFolderResult (this=0x9c02428, job=0x9fc8648) at ../../kmail/kmfolderimap.cpp:1355
#7  0xb741b38c in KMFolderImap::qt_metacall (this=0x9c02428, _c=QMetaObject::InvokeMetaMethod, _id=27, _a=0xbfb48eac) at ./kmfolderimap.moc:181
#8  0xb6f9fbe0 in QMetaObject::activate (sender=0x9fc8648, from_signal_index=7, to_signal_index=7, argv=0xbfb48eac) at kernel/qobject.cpp:3031
#9  0xb6fa0962 in QMetaObject::activate (sender=0x9fc8648, m=0xb7b854a8, local_signal_index=3, argv=0xbfb48eac) at kernel/qobject.cpp:3101
#10 0xb7a2a973 in KJob::result (this=0x9fc8648, _t1=0x9fc8648) at ./kjob.moc:186
#11 0xb7a2ae89 in KJob::emitResult (this=0x9fc8648) at ../../kdecore/jobs/kjob.cpp:294
#12 0xb5078dd5 in KIO::SimpleJob::slotFinished (this=0x9fc8648) at ../../kio/kio/job.cpp:489
#13 0xb5078f1e in KIO::ListJob::slotFinished (this=0x9fc8648) at ../../kio/kio/job.cpp:2416
#14 0xb507ad03 in KIO::ListJob::qt_metacall (this=0x9fc8648, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbfb49098) at ./jobclasses.moc:747
#15 0xb6f9fbe0 in QMetaObject::activate (sender=0x9f38fa0, from_signal_index=8, to_signal_index=8, argv=0x0) at kernel/qobject.cpp:3031
#16 0xb6fa0962 in QMetaObject::activate (sender=0x9f38fa0, m=0xb5235a64, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3101
#17 0xb5144e77 in KIO::SlaveInterface::finished (this=0x9f38fa0) at ./slaveinterface.moc:163
#18 0xb5148c47 in KIO::SlaveInterface::dispatch (this=0x9f38fa0, _cmd=104, rawdata=@0xbfb49264) at ../../kio/kio/slaveinterface.cpp:175
#19 0xb5145357 in KIO::SlaveInterface::dispatch (this=0x9f38fa0) at ../../kio/kio/slaveinterface.cpp:91
#20 0xb513675d in KIO::Slave::gotInput (this=0x9f38fa0) at ../../kio/kio/slave.cpp:322
#21 0xb51378d3 in KIO::Slave::qt_metacall (this=0x9f38fa0, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfb49378) at ./slave.moc:75
#22 0xb6f9fbe0 in QMetaObject::activate (sender=0x9f46f28, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3031
#23 0xb6fa0962 in QMetaObject::activate (sender=0x9f46f28, m=0xb5232540, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3101
#24 0xb503f757 in KIO::Connection::readyRead (this=0x9f46f28) at ./connection.moc:84
#25 0xb5041819 in KIO::ConnectionPrivate::dequeue (this=0x9f46c68) at ../../kio/kio/connection.cpp:82
#26 0xb50419a6 in KIO::Connection::qt_metacall (this=0x9f46f28, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x9ffbc80) at ./connection.moc:72
#27 0xb6f98d7b in QMetaCallEvent::placeMetaCall (this=0xa1917e0, object=0x9f46f28) at kernel/qobject.cpp:529
#28 0xb6f9a8f1 in QObject::event (this=0x9f46f28, e=0xa1917e0) at kernel/qobject.cpp:1155
#29 0xb668079c in QApplicationPrivate::notify_helper (this=0x9a810f0, receiver=0x9f46f28, e=0xa1917e0) at kernel/qapplication.cpp:3803
#30 0xb668861e in QApplication::notify (this=0xbfb49bc8, receiver=0x9f46f28, e=0xa1917e0) at kernel/qapplication.cpp:3393
#31 0xb7d607fd in KApplication::notify (this=0xbfb49bc8, receiver=0x9f46f28, event=0xa1917e0) at ../../kdeui/kernel/kapplication.cpp:307
#32 0xb6f8b0e1 in QCoreApplication::notifyInternal (this=0xbfb49bc8, receiver=0x9f46f28, event=0xa1917e0) at kernel/qcoreapplication.cpp:587
#33 0xb6f8bd65 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9a5e670) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:209
#34 0xb6f8bf5d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1091
#35 0xb6fb599f in postEventSourceDispatch (s=0x9a83520) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:214
#36 0xb488e1b8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#37 0xb4891853 in ?? () from /usr/lib/libglib-2.0.so.0
#38 0x09a83498 in ?? ()
#39 0x00000000 in ?? ()
_____________________________________________________
Backtrace end.

Backtrace start (right click on the icon):
_____________________________________________________
Application: KMail (kmail), signal SIGSEGV

Thread 1 (Thread 0xb40026c0 (LWP 4422)):
[KCrash Handler]
#6  0xb745ccfe in KMFolderImap::slotListFolderResult (this=0x845e948, job=0x895efa8) at ../../kmail/kmfolderimap.cpp:1355
#7  0xb745f38c in KMFolderImap::qt_metacall (this=0x845e948, _c=QMetaObject::InvokeMetaMethod, _id=27, _a=0xbf88dafc) at ./kmfolderimap.moc:181
#8  0xb6fe3be0 in QMetaObject::activate (sender=0x895efa8, from_signal_index=7, to_signal_index=7, argv=0xbf88dafc) at kernel/qobject.cpp:3031
#9  0xb6fe4962 in QMetaObject::activate (sender=0x895efa8, m=0xb7bc94a8, local_signal_index=3, argv=0xbf88dafc) at kernel/qobject.cpp:3101
#10 0xb7a6e973 in KJob::result (this=0x895efa8, _t1=0x895efa8) at ./kjob.moc:186
#11 0xb7a6ee89 in KJob::emitResult (this=0x895efa8) at ../../kdecore/jobs/kjob.cpp:294
#12 0xb50bcdd5 in KIO::SimpleJob::slotFinished (this=0x895efa8) at ../../kio/kio/job.cpp:489
#13 0xb50bcf1e in KIO::ListJob::slotFinished (this=0x895efa8) at ../../kio/kio/job.cpp:2416
#14 0xb50bed03 in KIO::ListJob::qt_metacall (this=0x895efa8, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbf88dce8) at ./jobclasses.moc:747
#15 0xb6fe3be0 in QMetaObject::activate (sender=0x8790678, from_signal_index=8, to_signal_index=8, argv=0x0) at kernel/qobject.cpp:3031
#16 0xb6fe4962 in QMetaObject::activate (sender=0x8790678, m=0xb5279a64, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3101
#17 0xb5188e77 in KIO::SlaveInterface::finished (this=0x8790678) at ./slaveinterface.moc:163
#18 0xb518cc47 in KIO::SlaveInterface::dispatch (this=0x8790678, _cmd=104, rawdata=@0xbf88deb4) at ../../kio/kio/slaveinterface.cpp:175
#19 0xb5189357 in KIO::SlaveInterface::dispatch (this=0x8790678) at ../../kio/kio/slaveinterface.cpp:91
#20 0xb517a75d in KIO::Slave::gotInput (this=0x8790678) at ../../kio/kio/slave.cpp:322
#21 0xb517b8d3 in KIO::Slave::qt_metacall (this=0x8790678, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbf88dfc8) at ./slave.moc:75
#22 0xb6fe3be0 in QMetaObject::activate (sender=0x879e590, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3031
#23 0xb6fe4962 in QMetaObject::activate (sender=0x879e590, m=0xb5276540, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3101
#24 0xb5083757 in KIO::Connection::readyRead (this=0x879e590) at ./connection.moc:84
#25 0xb5085819 in KIO::ConnectionPrivate::dequeue (this=0x879e3a8) at ../../kio/kio/connection.cpp:82
#26 0xb50859a6 in KIO::Connection::qt_metacall (this=0x879e590, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x89ab938) at ./connection.moc:72
#27 0xb6fdcd7b in QMetaCallEvent::placeMetaCall (this=0x896f8e0, object=0x879e590) at kernel/qobject.cpp:529
#28 0xb6fde8f1 in QObject::event (this=0x879e590, e=0x896f8e0) at kernel/qobject.cpp:1155
#29 0xb66c479c in QApplicationPrivate::notify_helper (this=0x8312148, receiver=0x879e590, e=0x896f8e0) at kernel/qapplication.cpp:3803
#30 0xb66cc61e in QApplication::notify (this=0xbf88f908, receiver=0x879e590, e=0x896f8e0) at kernel/qapplication.cpp:3393
#31 0xb7da47fd in KApplication::notify (this=0xbf88f908, receiver=0x879e590, event=0x896f8e0) at ../../kdeui/kernel/kapplication.cpp:307
#32 0xb6fcf0e1 in QCoreApplication::notifyInternal (this=0xbf88f908, receiver=0x879e590, event=0x896f8e0) at kernel/qcoreapplication.cpp:587
#33 0xb6fcfd65 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x82ef670) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:209
#34 0xb6fcff5d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1091
#35 0xb6ff999f in postEventSourceDispatch (s=0x8314520) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:214
#36 0xb48d21b8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#37 0xb48d5853 in ?? () from /usr/lib/libglib-2.0.so.0
#38 0x08314498 in ?? ()
#39 0x00000000 in ?? ()
_____________________________________________________
Backtrace end.
Comment 1 Jaime Torres 2009-01-10 23:42:26 UTC
This could be a duplicate of bug 179765, that is probably a kde 4 version of bug 146156.

Do you still see it with a more recent version of kmail?
Comment 2 Wolfgang Mader 2009-01-11 00:10:46 UTC
The Kmail version is:
Qt: 4.4.3
KDE: 4.1.96 (KDE 4.1.96 (KDE 4.2 RC1))
KMail: 1.11.0

But I found out a bit more. The file on the server representing the imap folder (fdm) still exists, but Kmail, as well as the webmailer, is not able to show its content.
Then I have removed the imap account in Kmail and configured if anew. Now, after the old folder settings are gone Kmail no longer crashs, and the content is shown correctly. Curiously, the webmailer still shows no content.

I do not know how imap is organized, but now I think Kmail has destroit some sort of imap-index.

Hope this helps.
Cheers, Wolfgang
Comment 3 Dario Andres 2009-01-13 15:51:31 UTC
Bug 180554 have the same backtrace. It should be related to thi
Comment 4 George Kiagiadakis 2009-01-13 16:12:36 UTC
@Wolfgang: does it still happen with kdepim >= svn revision 908525 ? This
revision is supposed to fix this issue...
Comment 5 Wolfgang Mader 2009-01-13 16:45:06 UTC
@George
I do rely on the kde4.2 packages from the debian kde team. The version of kdepim in this repo is svn907519. So, at the moment, I can not answer your question.
On the other side, since I managed to get back my mail, everything works, and I am not sure to be able to reproduce the problem. But, of course, I will try once the next version of kdepim pops up on my computer.
Comment 6 Christophe Marin 2009-02-14 19:39:52 UTC
Wolfgang: Did you experience this crash again during the past month ?
Comment 7 Wolfgang Mader 2009-02-16 13:24:45 UTC
Christophe Giboudeaux:
No, the report marks the only occurrence of this event on my machine. I tried to reproduce the problem at the moment, but the problem seems to be solved. This is with kmail 1.11.0.
Comment 8 Jaime Torres 2009-02-21 10:54:25 UTC
If this bug appens again, please reopen the bug report.