From owner-freebsd-stable@FreeBSD.ORG Tue Jan 12 13:09:49 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 924381065672; Tue, 12 Jan 2010 13:09:49 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 668318FC08; Tue, 12 Jan 2010 13:09:48 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA28759; Tue, 12 Jan 2010 15:09:46 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <4B4C7499.3080003@icyb.net.ua> Date: Tue, 12 Jan 2010 15:09:45 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20091206) MIME-Version: 1.0 To: Hajimu UMEMOTO References: <25538.130.133.86.198.1263210888.webmail@portal.zedat.fu-berlin.de> In-Reply-To: X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, ohartman@zedat.fu-berlin.de, freebsd-ports@freebsd.org Subject: Re: thunderbird3: dies with socket(): Protocol not supported Illegal instruction (core dumped) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jan 2010 13:09:49 -0000 on 12/01/2010 08:53 Hajimu UMEMOTO said the following: > Hi, > >>>>>> On Mon, 11 Jan 2010 12:54:48 +0100 >>>>>> ohartman@zedat.fu-berlin.de said: > > ohartman> Since friday after the last FreeBSD 8.0-STABLE/amd64 update, thunderbird3 > ohartman> crashes immmediately or after a view seconds with > > ohartman> socket(): Protocol not supported > ohartman> Illegal instruction (core dumped) > > I'm not sure but I suspect you are using custom kernel built without > INET6 option. If so, thunderbird3 is depending upon IPv6. Can it be made to not require IPv6? (especially when there is no actual IPv6 connectivity). -- Andriy Gapon