On Sun, 21 May 2006 17:55:12 -0700, Steve wrote in message <[EMAIL PROTECTED]>:
> On Fri, May 19, 2006 at 08:40:09PM +0200, Arnt Karlsen wrote: > > On Thu, 18 May 2006 17:48:04 -0700, Debian wrote in message > > <[EMAIL PROTECTED]>: > > > ..if there has been _any_ activity on this bug at all, I _am_ losing > > mail data, I see precisely _nothing_ other than the initial > > acknowledgement on bug#367986. > > Please explain what data it is that's being lost. If you are losing > the mails that you're trying to move between folders, that's cause for > a release-critical bug. ..that would be the case. If you can verify this is the first response to my bug report, I have gotten it all, if not, I'm losing mail. > If you're losing data because you had mails open for *composing* at > the time of the crash, that's not a release-critical bug in > sylpheed-gtk1. ..no problem there. ;o) > Any crash in X is not itself a bug in sylpheed-gtk1 either, *unless* > sylpheed-gtk1 is allocating an excess of server-side memory and > triggering the kernel's OOM killer, which doesn't seem likely. ..ok, how do I help you find out? Running it locally, has it crash X a lot, and get X get sluggish and I see loads around 2 to 6. Running it over ssh, I see nice low loads, around 0.05-0.15. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
