On Monday 23 March 2009 16:57:52 Eli Wapniarski wrote: > On Monday 23 March 2009 16:44:57 Anne Wilson wrote: > > On Monday 23 March 2009 12:38:59 Claude Jones wrote: > > > I've had this happen with individual messages. One message would be > > > problematic, and it was a real pain to get around (I'd have to find a > > > way to mark it read without entering the folder or some such...) I > > > can't say what fixed the issue, but, I would guess it may have been an > > > update. > > > > FWIW, I had this problem with a particular message. The big problem was > > that every time I tried to start it the cursor was on the bad message. > > The way I got around the problem was to edit ~/.kde/share/config/kmailrc, > > [Behaviour] section, setting ActionEnterFolder=SelectFirstNew - which > > puts me onto a different message. Then I read all messages in the folder > > apart from the bad one, and used the Folder context menu to mark all > > messages read. > > > > Anne > > There should be no such thing as a "bad message which causes kmail to > crash. Which means that this is a bug. Which means it should be reported. > If you haven't removed the "bad message" don't. Please report this > upstream. > IIRC I discovered later that the problem was not in the message itself, but a problem with the GPG signature of the message. I don't recall the details, but GPG was choking on it. It has only happened once and that was a long, long time ago. Anne -- New to KDE4? - get help from http://userbase.kde.org Just found a cool new feature? Add it to UserBase -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. Url : http://lists.fedoraproject.org/pipermail/kde/attachments/20090323/797af956/attachment.bin
