Re: [Evolution] BUG: frozen while looking up new mail

[Jeffrey Stedfast <fejj ximian com>]

On Tue, 2004-03-02 at 17:30, D. D. Brierton wrote:
> On Tue, 2004-03-02 at 18:53, Florin Andrei wrote:
>
> > Everything's mostly fine, with one exception: Evo gets locked up hard
> > every time it checks the Inbox. It's only for a few seconds, and after
> > that it resumes normal functioning, but during those moments nothing
> > works, i cannot even type into the Composer, or if i copy/paste text
> > outside Evo and i hit CTRL-V exactly when it's frozen, it will wait
> > until the lookup is over.
> > This is not a regular "the system is too loaded to serve new requests"
> > type of thing. It is a hard lock, the CPU is mostly idle, the SCSI is
> > mostly idle, but Evo is 100% unresponsive for like 5 seconds or so.
>
> Isn't this the known issue of either no entry for localhost or gaps
> and/or comments in /etc/hosts? If it is, then it isn't a bug in
> evolution but a known bug in something else (either glib or glibc if I
> remember correctly). Remove any comments or blank lines in /etc/hosts
> and see if the problem goes away.

the hang you are thinking of is the one in the composer due to the
autosave code which does a hostname lookup on for the local machine to
generate a valid Message-Id. The hang there is due to the user not
having "127.0.0.1  localhost" in his /etc/hosts file.

The glibc bug you are thinking about related to hostname lookups only
affects SMTP as far as we know (since it is the only code that uses
gethostbyaddr_r).

While this problem *could* be related to the first issue, he hasn't
stated that he had the composer open, but maybe he just forgot to
mention it?

Florin: do you have a composer window open?

Jeff

> Best, Darren