[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Re: IMAP crash ate inbox (was: Re: [Kde-cafe] Sometimes I hate KDE...)
From:       Eva Brucherseifer <eva () kde ! org>
Date:       2002-03-31 20:48:52
[Download RAW message or body]

> I wonder why people discuss this in the cafe.

Well, you asked...  I wanted to check first, if others experience the same 
problem and also if we can find some similarities, before writing a bug 
report about a vague thing. I already expirienced quite harsh answers to 
kmail bug reports at other occasions...

>
> Please cc Martijn and Eva (?) if you reply to this message.
>
> ----------  Forwarded Message  ----------
>
> Subject: Re: [Kde-cafe] Sometimes I hate KDE...
> Date: Sun, 31 Mar 2002 16:46:23 +0200
> From: Martijn Klingens <mklingens@yahoo.com>
> To: kde-cafe@kde.org
>
> On Sunday 31 March 2002 12:35, Eva Brucherseifer wrote:
> > it happened again... kmail managed to kill my inbox. This time even
> > on the server (via imap) - pretty intelligent this tool. The bad
> > thing is, I have a crash (with backtrace), I have several strange
> > events, but I don't know at all when and how this happend. Not real
> > good conditions to write a bug report...
> >
> > So I thought, I take comfort in meeting my friends in the cafe and
> > telling my story here. I guess I don't have to ask, if you have
> > similar experiences...
>
> I have. In my case KMail didn't crash, but apart from that I have seen
>  it eating my inbox as well. However, I can also confirm regular
>  crashes with KMail and imap.
>
> As for the crashes, in my case they happen as soon as I am selecting
> _multiple_ messages by either keyboard or mouse and at the same time
>  the check for new messages tries to add a new message to the listview.

That could be the reason for my experiences too. What I basically did is the 
following: I have a pop3s account which I use for reading mails, since all 
filters work locally and since I have the mails still on the server to 
download them to my machine at work (at work KDE2.2.2 is running with rather 
bad imap support). Because I cannot delete single messages from the server 
using pop3 in kmail, I use the imaps. And yes - I select multiple messages 
for that. The deletion in the inbox copies the mails to Trash on the server. 
From Trash I can delete them for good.

>  This is a very nasty race condition that Michael Haeckel couldn't
>  reproduce, so I have my doubts whether this one will be fixed soon.
>  The crash does not happen if there's no new mail. Also, if you have
>  some mails selected but don't select more mails while new mail arrives
>  the crash doesn't happen. Since adding the raw item to the list view
>  can be considered atomic (the event loop is not active during that
>  operation) it must be either an obscure bug in QListView with trees or
>  KMail updates some internal variables that are not in the list view
>  and modified by both the selection and the mail fetching.

Since the transaction was quite slow for a reason I don't know, so I started 
switching between the imap inbox and the imap Trash folder - so it could be, 
that a message arrived during this time.

The day I also tried to get rid of old messages, but the result was different: 
When I wanted to download messages via pop3 afterwards, it started to 
download _all_ mails, also old ones.

The messages in the log file on the imap server look like this:

Mar 31 11:02:28 glia imapd[16870]: [ID 576018 mail.debug] port 57363 service 
ini
t from 127.0.0.1
Mar 31 11:02:28 glia imapd[16870]: [ID 666661 mail.info] Authenticated 
user=eva
host=localhost [127.0.0.1]
Mar 31 11:02:59 glia imapd[16870]: [ID 949407 mail.info] Broken pipe, while 
writ
ing text user=eva host=localhost [127.0.0.1]
Mar 31 11:03:01 glia imapd[16871]: [ID 576018 mail.debug] port 57369 service 
ini
t from 127.0.0.1
Mar 31 11:03:05 glia imapd[16871]: [ID 666661 mail.info] Authenticated 
user=eva
host=localhost [127.0.0.1]
Mar 31 11:03:35 glia imapd[16871]: [ID 985434 mail.info] Connection reset by 
pee
r, while reading line user=eva host=localhost [127.0.0.1]


The last mail I got was 9:28, so I am not sure that it was received during the 
delete. But the deletion from the imap inbox (which is equal to moving the 
mail to the imap Trash) and the deletion in the imap Trash folder can have 
accured at the same time due to my impatience.

>
> As for the eating my inbox, I haven't seen that in some 2-3 months
>  anymore, though I saw at least one report on kde-cvs indicating that
>  this is not solved yet.

My sources are from March 24. Matze also killed his inbox which happend 2 or 3 
months ago. He also remembers, that he had selected several messages for 
deletion.

>
> As for you experiencing both: could it be that both bugs are related
>  and/or that you triggered both at the same time?

Puh, maybe... I'll attach the backtrace.

Hope this helps,
eva




>
> > Do you see any chances for still setting up a reasonable bug report?
>
> Hopefully the above is of any use. Since it is still _very_ vague I
>  didn't bother about cc-ing the kmail developers, although Ingo might
>  want to do so himself if he considers this mail valuable. I'm not
>  subscribed there, so CC me if you want me to comment on the issues.
>
> > The bad thing with kmail and imap is, is that it allows several
> > actions in parallel, but there is only one status line. So you never
> > know which action the progress bar is for and if actions you did
> > before are really finished. An impatient user as I am one never waits
> > until actions are finished.
>
> Me too.
>
> > I also use the stop button quite a lot, if I have to wait too long.
> > Maybe I should request the "feature" to block parallel actions for
> > imap?
>
> heh... maybe :-)
>
> Martijn

["kmail_imap_delete_crash.txt" (text/plain)]

[New Thread 1024 (LWP 5693)]
0x414f4079 in wait4 () from /lib/libc.so.6
#0  0x414f4079 in wait4 () from /lib/libc.so.6
#1  0x4156c8c4 in __DTOR_END__ () from /lib/libc.so.6
#2  0x413cd177 in waitpid () from /lib/libpthread.so.0
#3  0x40b39a0c in KCrash::defaultCrashHandler ()
   from /opt/kde3cvs_2/lib/libkdecore.so.4
#4  0x413cabc4 in pthread_sighandler () from /lib/libpthread.so.0
#5  <signal handler called>
#6  0x0819705a in KMImapJob::slotGetMessageResult ()
#7  0x081a2ef5 in KMImapJob::qt_invoke ()
#8  0x40e5deb4 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#9  0x404bcc25 in KIO::Job::result () from /opt/kde3cvs_2/lib/libkio.so.4
#10 0x4049d562 in KIO::Job::emitResult () from /opt/kde3cvs_2/lib/libkio.so.4
#11 0x404a01f9 in KIO::SimpleJob::slotFinished ()
   from /opt/kde3cvs_2/lib/libkio.so.4
#12 0x404a4981 in KIO::TransferJob::slotFinished ()
   from /opt/kde3cvs_2/lib/libkio.so.4
#13 0x404be02c in KIO::TransferJob::qt_invoke ()
   from /opt/kde3cvs_2/lib/libkio.so.4
#14 0x40e5deb4 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0x40e5ddfe in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0x4048c46c in KIO::SlaveInterface::finished ()
   from /opt/kde3cvs_2/lib/libkio.so.4
#17 0x404886b4 in KIO::SlaveInterface::dispatch ()
   from /opt/kde3cvs_2/lib/libkio.so.4
#18 0x40488202 in KIO::SlaveInterface::dispatch ()
   from /opt/kde3cvs_2/lib/libkio.so.4
#19 0x4048534c in KIO::Slave::gotInput () from /opt/kde3cvs_2/lib/libkio.so.4
#20 0x40487819 in KIO::Slave::qt_invoke () from /opt/kde3cvs_2/lib/libkio.so.4
#21 0x40e5deb4 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0x40e5dfcb in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0x4110f1bd in QSocketNotifier::activated ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0x40e7437f in QSocketNotifier::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0x40e05533 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0x40e053d4 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0x40a9fde5 in KApplication::notify ()
   from /opt/kde3cvs_2/lib/libkdecore.so.4
#28 0x40db30ed in sn_activate () from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0x40db38b7 in QApplication::processNextEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0x40e069d1 in QApplication::enter_loop ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#31 0x40db316b in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0x081c1218 in main ()
#33 0x414697ee in __libc_start_main () from /lib/libc.so.6

_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic