Re: [Evolution] Should I file these problems as bugs?



On Mon, 2004-11-22 at 09:25 +0800, Not Zed wrote:
You mean you're running 2.0.2, there is no such version as 2.02, and
if there is, then it must be something we can't support. 

Oops, fatfingers... 2.0.2 is indeed the version.

If I would want to investigate further, where would I start?
ethereal? diffing snapshots of ~/.evolution/mail/pop/$account/uid-cache?

Probably camel logs.

Below is a piece of my camel log.
I only see "Checking expire cycle time on dir" when evolution
redownloads all the messages. (I have replaced my details with
account server)

Checking expire cycle time on dir
'/home/bas/.evolution/mail/pop/account server/cache/00'^M
Checking '/home/bas/.evolution/mail/pop/account server/cache/00/.' for
expiry^M
Checking '/home/bas/.evolution/mail/pop/account server/cache/00/..' for
expiry^M
Checking
'/home/bas/.evolution/mail/pop/account server/cache/00/1100260842.33268'
for expiry^M
Checking
'/home/bas/.evolution/mail/pop/account server/cache/00/1100710364.19988'
for expiry^M
Checking
'/home/bas/.evolution/mail/pop/account server/cache/00/1100710364.19989'
for expiry^M
Checking
'/home/bas/.evolution/mail/pop/account server/cache/00/1100731496.21556'
for expiry^M
Checking
'/home/bas/.evolution/mail/pop/account server/cache/00/1100731496.21557'
for expiry^M
Thread ad7bfbb0 >^M
CamelFolder:get_message('inbox', '1100260842.33267') =^M
class: CamelMimeMessage^M
mime-type: text/plain^M
content class: CamelDataWrapper^M
content mime-type: text/plain^M
< ad7bfbb0 >^M


With evolution 2.0.1 I do not have any redownloading problems.
After searching the bug DB a bit I came along
http://bugs.ximian.com/show_bug.cgi?id=63521
The fix for this bug was applied in 2.0.2
Could that fix have introduced the problems I am having?

Thanks in advance,

Bastiaan Spandaw





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]