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

List:       kmail-devel
Subject:    IMAP crash ate inbox (was: Re: [Kde-cafe] Sometimes I hate KDE...)
From:       Ingo =?iso-8859-1?q?Kl=F6cker?= <ingo.kloecker () epost ! de>
Date:       2002-03-31 17:45:31
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I wonder why people discuss this in the cafe.

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.
 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.

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.

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

> 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
- --
Kde-cafe mailing list
Kde-cafe@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-cafe

- -------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8p0s7GnR+RTDgudgRAul8AJ47aSHHFl80tHDLpLFfSof/JAweUQCbB8Q5
eLOyBKF3A6thQRP9kdSTCEg=
=FaTw
-----END PGP SIGNATURE-----
_______________________________________________
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]