linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Eric Blade <eblade@m-net.arbornet.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Evolution and 2.5.x
Date: 13 Oct 2002 15:03:23 -0400	[thread overview]
Message-ID: <1034535804.6032.4501.camel@phantasy> (raw)
In-Reply-To: <200210131854.g9DIs1I0062874@m-net.arbornet.org>

On Sun, 2002-10-13 at 14:54, Eric Blade wrote:

>   I'm guessing that not too many of the kernel developers use Evolution as
> their email program :)   Since I started picking up the 2.5.x series, at around
> 2.5.34, Evolution does not run anywhere near properly.  I'm not sure if that
> is a kernel issue, or a problem with Evolution's code..  But it did improve
> quite a bit with all the low-level process management that was in the 2.5.3x 
> series.  It still doesn't work right though.  (in 2.5.34, evolution would
> just plain halt the system ... in 2.5.42, it mostly works right, as long
> as you don't try to compose a message.. composing a message will leave you
> with a whole buch of zombie processes). 

Hey, I use Evolution ;-)

See this thread:
http://lists.ximian.com/archives/public/evolution-hackers/2002-June/004841.html

It is indeed broken in 2.5 and it is not, for once, our fault.  This
thread and other discussion seem to point out it is a bug in ORBit.

	Robert Love


  reply	other threads:[~2002-10-13 18:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-13 18:54 Evolution and 2.5.x Eric Blade
2002-10-13 19:03 ` Robert Love [this message]
2002-10-13 19:24   ` Eric Blade
2002-10-14 18:07   ` Andy Pfiffer
2002-10-14 19:41     ` Thomas Molina
2002-10-14 19:48       ` Robert Love
2002-10-14 20:39       ` Andy Pfiffer
2002-10-15  4:48       ` Eric Blade

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1034535804.6032.4501.camel@phantasy \
    --to=rml@tech9.net \
    --cc=eblade@m-net.arbornet.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).