Date: Fri, 19 Aug 2011 17:59:53 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Alex Dupre <ale@FreeBSD.org> Cc: gecko@FreeBSD.org, Doug Barton <dougb@FreeBSD.org> Subject: Re: cvs commit: ports UPDATING ports/mail/enigmail Makefile distinfo pkg-message ports/mail/enigmail-thunderbird Makefile Message-ID: <4E4E7A69.8050406@FreeBSD.org> In-Reply-To: <4E4E05BA.9070707@FreeBSD.org> References: <201108181007.p7IA7PgK032094@repoman.freebsd.org> <4E4D6AD3.2050708@FreeBSD.org> <4E4D70FF.2060206@FreeBSD.org> <4E4DCFED.4070601@FreeBSD.org> <4E4E05BA.9070707@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[restoring cc to the list, I hope that you don't object] on 19/08/2011 09:42 Alex Dupre said the following: > Doug Barton ha scritto: >>> Tomorrow I'll try also with thunderbird and let you know. >> >> Thanks. > > I've just tried. I confirm your behavior only the first time I launch > thunderbird. It is sufficient to close and reopen thunderbird and then > enigmail works like a charm. This is with a clean installation (rm -rf > ~/.thunderbird), so it seems the issue is present only when the profile > is created the first time. I imagine you have tried multiple times > before writing me, so I think the issue is to be searched in your profile. I don't think that the situation is that simple in my case. Having enabled debug messages in enigmail I see that it gets stuck after the following message: 2011-08-19 12:35:24.717 [CONSOLE] EnigmailAgentPath=/usr/local/bin/gpg It is actually stuck in ipcService.runPipe() call after that message. Having looked further it seems that the call is actually stuck in the following sequence: nsIPCService::RunPipe -> nsPipeTransport::Terminate -> nsPipeTransport::Kill -> IPC_WaitProcess == _MD_WaitUnixProcess In the _MD_WaitUnixProcess the following path is taken: FindPidTable returns NULL and the thread gets stuck forever on PR_WaitCondVar(pRec->reapedCV, ...) With ktrace I see that /usr/local/bin/gpg (which is actually a symlink to /usr/local/bin/gpg2) gets executed, gpg2 prints some information and exits with a status of 0. I am not sure if this behavior can be explained by anything in the profile. It rather looks like some possibly timing-triggered bug. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E4E7A69.8050406>