Re: [Evolution] Mail Delivery (failure evolution ximian com)
- From: Not Zed <notzed ximian com>
- To: James Ascroft-Leigh <jwal declarative co uk>
- Cc: evolution lists ximian com
- Subject: Re: [Evolution] Mail Delivery (failure evolution ximian com)
- Date: Mon, 17 May 2004 09:38:41 +0800
On Sun, 2004-05-16 at 00:25 +0100, James Ascroft-Leigh wrote:
All,
On Fri, 2004-05-14 at 09:57 +0900, fejj ximian com wrote:
> If the message will not displayed automatically,
> follow the link to read the delivered message.
>
> Received message is available at:
> www.ximian.com/inbox/evolution/read.php?sessionid-8463
>
I am using the 1.5.7 build from Debian unstable + experimental. The
message I am replying to causes Evolution to die on display (in my case
in the preview pane). Displaying as email source does not cause the
crash. I have observed two different crash modes, I think:
1. Die saying something like "The application has crashed...
[restart] [crash] [report]"
2. Just die
This is a known bug. I get about 5-6 of these every day. It is a crash in Pango.
I normally view the message from a vFolder, the crash does not seem to
happen when I look at the message directly from my IMAP inbox. I should
also mention that I am replying in plain text but there is some artifact
being rendered to from the original HTML message. Strangely now that I
have viewed the message properly from my real inbox it displays without
crashing from the vFolder now.
Its probably just luck. It doesn't always crash for me, but it stomps all over memory, hence the following effects.
Okay, this is getting really strange now - as I compose this message I
find all kinds of crazy effects. Placing the cursor at the top of the
message and using the down arrow to move firstly makes it jump from the
artifact back to the beginning. Then, as I continue pressing down, it
continues beyond the artifact and even beyond the end of the message.
The page down key has similarly unexpected consequences.
I would like to attach some debugging information but am now unable to
recreate because it has stopped crashing.
Well 'known', but no known fix yet. Its getting to the serious end of the devel cycle, so should be addressed I guess.
Thanks for a great MUA,
James Ascroft-Leigh
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]