Version: 1.10.0 (using 4.1.1 (KDE 4.1.0 (4.1 >= 20080722)) "release 26.8", KDE:KDE4:Factory:Desktop / openSUSE_Factory) Compiler: gcc OS: Linux (i686) release 2.6.25.11-0.1-pae When I use Kmail I receive mails only in my "Inbox" folder, nowhere else. After reading I move them to different folders. But Kmail freezes a lot of times, and here's what happens: - Kmail deletes the message from Inbox folder immediately after I had made a move - Kmail crashes (probably under synch.) - After the restart the messages ARE NOT in the appropriate folder (because Kmail crashed) but they aren't in the inbox folder either - Plus: after this the program uploads the whole affected folder to the mail server (which means in some times 50-60MB upload!), sometimes duplicating the existing mails on the server (and only there, in the program I don't see the duplicates). The folder counter is decreasing meanwhile but after finished, it downloads only a fragment of the all letters (eg. from 400 only 20). This is a very annoying and _dangerous data loss_ which happens to me every 5-6th day, so very-very often.
As you say that this crash happens regularly, could you have a look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and install the debug packages for your distribution so that? This way you can paste a good backtrace the next time it crashes for you.
Thank you for your advice, I installed the debug libraries (after the 3rd crash) and reported the first one: #169172 :)
so can we close this one as you'll file the crashes as individual bugreports?
My main problem is described in the upper 4 points: when Kmail crashes and I moved my letters to an other folder, it loses them at next restart (and sometimes it uploads the whole folder to the server). I file crash reports individually from this ticket, becaue the "how-the-crash-occured" is not related to this bug. (Btw. the new Bugzilla theme is modern but very hard to read because it has no room for the report itself.)
I had 27 important letters in my inbox folder with which I should have had to do something. But after a crash only 4 mails left in the folder. I don't know why exactly 4. The other 23 disappeared. Fortunately, Gmail stores them in "All mail" folder (and I disabled this folder in KMail), so I must find 23 letters within 5200. But a lot of people do not have Gmail which can save their important mails. Please, fix this bug.
Today crashed again, but this time without a KCrash window. From 45 letters I have 0 in my inbox after restarting Kmail... It WIPED OUT ALL my mails! When do you want to fix this?
Seems like Bug 63353, a five-and-half-year-old bug.
I can reproduce this on 1.11.2. Steps: 1. Move mail to some folder using right click option. 2. Try step 1 again. 3. Drag mail from inbox to some folder. 4. Boom! (In case it doesn't crash, repeat step 3 several times.) Fortunately mails are not lost in my case. Backtrace: Application: KMail (kmail), signal SIGSEGV [?1034h[Thread debugging using libthread_db enabled] [Current thread is 1 (Thread 0xb3bff700 (LWP 9292))] Thread 2 (Thread 0xb0895b90 (LWP 9840)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb5cf9411 in select () from /lib/libc.so.6 #2 0xb6b05477 in QProcessManager::run (this=0x8078ae8) at io/qprocess_unix.cpp:305 #3 0xb6a3374e in QThreadPrivate::start (arg=0x8078ae8) at thread/qthread_unix.cpp:189 #4 0xb69d11b5 in start_thread () from /lib/libpthread.so.0 #5 0xb5d003be in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb3bff700 (LWP 9292)): [KCrash Handler] #6 KMail::FolderJob::msgList (this=0x81ee508) at /usr/include/QtCore/qatomic_i386.h:116 #7 0xb751873b in KMAcctImap::ignoreJobsForMessage (this=0x85bbd98, msg=0x843f9c8) at /usr/src/debug/kdepim-4.2.2/kmail/kmacctimap.cpp:215 #8 0xb752cee5 in KMFolderImap::ignoreJobsForMessage (this=0x84a1f80, msg=0x843f9c8) at /usr/src/debug/kdepim-4.2.2/kmail/kmfolderimap.cpp:1562 #9 0xb7626814 in KMMoveCommand::execute (this=0x8b06cb8) at /usr/src/debug/kdepim-4.2.2/kmail/kmcommands.cpp:2086 #10 0xb7614c12 in KMCommand::slotPostTransfer (this=0x8b06cb8, result=KMCommand::OK) at /usr/src/debug/kdepim-4.2.2/kmail/kmcommands.cpp:276 #11 0xb761ed94 in KMCommand::qt_metacall (this=0x8b06cb8, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbff415ac) at /usr/src/debug/kdepim-4.2.2/build/kmail/kmcommands.moc:86 #12 0xb761f28a in KMMoveCommand::qt_metacall (this=0x8b06cb8, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbff415ac) at /usr/src/debug/kdepim-4.2.2/build/kmail/kmcommands.moc:1662 #13 0xb6b3dc88 in QMetaObject::activate (sender=0x8b06cb8, from_signal_index=4, to_signal_index=4, argv=0xbff415ac) at kernel/qobject.cpp:3069 #14 0xb6b3f412 in QMetaObject::activate (sender=0x8b06cb8, m=0xb7a059d4, local_signal_index=0, argv=0xbff415ac) at kernel/qobject.cpp:3143 #15 0xb7610773 in KMCommand::messagesTransfered (this=0x8b06cb8, _t1=KMCommand::OK) at /usr/src/debug/kdepim-4.2.2/build/kmail/kmcommands.moc:100 #16 0xb7628b94 in KMCommand::transferSelectedMsgs (this=0x8b06cb8) at /usr/src/debug/kdepim-4.2.2/kmail/kmcommands.cpp:370 #17 0xb7628d83 in KMCommand::slotStart (this=0x8b06cb8) at /usr/src/debug/kdepim-4.2.2/kmail/kmcommands.cpp:268 #18 0xb761eda3 in KMCommand::qt_metacall (this=0x8b06cb8, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbff41788) at /usr/src/debug/kdepim-4.2.2/build/kmail/kmcommands.moc:85 #19 0xb761f28a in KMMoveCommand::qt_metacall (this=0x8b06cb8, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbff41788) at /usr/src/debug/kdepim-4.2.2/build/kmail/kmcommands.moc:1662 #20 0xb6b3dc88 in QMetaObject::activate (sender=0x8c97778, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3069 #21 0xb6b3f412 in QMetaObject::activate (sender=0x8c97778, m=0xb6c1d908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3143 #22 0xb6b430f7 in QSingleShotTimer::timeout (this=0x8c97778) at .moc/release-shared/qtimer.moc:76 #23 0xb6b4321c in QSingleShotTimer::timerEvent (this=0x8c97778) at kernel/qtimer.cpp:298 #24 0xb6b3812f in QObject::event (this=0x8c97778, e=0xbff41c30) at kernel/qobject.cpp:1082 #25 0xb5fd7eec in QApplicationPrivate::notify_helper (this=0x80761c8, receiver=0x8c97778, e=0xbff41c30) at kernel/qapplication.cpp:4084 #26 0xb5fe01ae in QApplication::notify (this=0xbff41f78, receiver=0x8c97778, e=0xbff41c30) at kernel/qapplication.cpp:3631 #27 0xb7e11bcd in KApplication::notify (this=0xbff41f78, receiver=0x8c97778, event=0xbff41c30) at /usr/src/debug/kdelibs-4.2.2/kdeui/kernel/kapplication.cpp:307 #28 0xb6b279db in QCoreApplication::notifyInternal (this=0xbff41f78, receiver=0x8c97778, event=0xbff41c30) at kernel/qcoreapplication.cpp:602 #29 0xb6b57026 in QTimerInfoList::activateTimers (this=0x8078a64) at kernel/qcoreapplication.h:213 #30 0xb6b534d0 in timerSourceDispatch (source=0x8078a30) at kernel/qeventdispatcher_glib.cpp:164 #31 0xb43a8d88 in IA__g_main_context_dispatch (context=0x8078220) at gmain.c:1814 #32 0xb43ac2fb in g_main_context_iterate (context=0x8078220, block=1, dispatch=1, self=0x8076130) at gmain.c:2448 #33 0xb43ac478 in IA__g_main_context_iteration (context=0x8078220, may_block=1) at gmain.c:2511 #34 0xb6b53428 in QEventDispatcherGlib::processEvents (this=0x8073828, flags={i = -1074520616}) at kernel/qeventdispatcher_glib.cpp:323 #35 0xb6077ac5 in QGuiEventDispatcherGlib::processEvents (this=0x8073828, flags={i = -1074520568}) at kernel/qguieventdispatcher_glib.cpp:202 #36 0xb6b25ffa in QEventLoop::processEvents (this=0xbff41e80, flags={i = -1074520504}) at kernel/qeventloop.cpp:149 #37 0xb6b2643a in QEventLoop::exec (this=0xbff41e80, flags={i = -1074520440}) at kernel/qeventloop.cpp:200 #38 0xb6b288e9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880 #39 0xb5fd7d67 in QApplication::exec () at kernel/qapplication.cpp:3553 #40 0x0804a5e0 in main (argc=) at /usr/src/debug/kdepim-4.2.2/kmail/main.cpp:146
Backtrace in comment #8 is a duplicate of 163071, and seems unrelated to this bug report.
No backtrace from the original reporter. It's time to close this report.