From owner-freebsd-gnome@FreeBSD.ORG Tue Nov 9 00:20:12 2010 Return-Path: Delivered-To: gnome@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85D131065670 for ; Tue, 9 Nov 2010 00:20:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5A7458FC18 for ; Tue, 9 Nov 2010 00:20:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oA90KCiS011162 for ; Tue, 9 Nov 2010 00:20:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oA90KCPP011161; Tue, 9 Nov 2010 00:20:12 GMT (envelope-from gnats) Date: Tue, 9 Nov 2010 00:20:12 GMT Message-Id: <201011090020.oA90KCPP011161@freefall.freebsd.org> To: gnome@FreeBSD.org From: "Kevin Oberman" Cc: Subject: Re: ports/151725: sysutils/hal: hald fails to start with dbus-1.4 X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kevin Oberman List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Nov 2010 00:20:12 -0000 The following reply was made to PR ports/151725; it has been noted by GNATS. From: "Kevin Oberman" To: Joe Marcus Clarke Cc: Andriy Gapon , gnome@freebsd.org, bug-followup@freebsd.org Subject: Re: ports/151725: sysutils/hal: hald fails to start with dbus-1.4 Date: Mon, 08 Nov 2010 16:14:42 -0800 > Date: Mon, 08 Nov 2010 19:02:13 -0500 > From: Joe Marcus Clarke > > On 11/5/10 1:33 PM, Andriy Gapon wrote: > > on 05/11/2010 19:24 Andriy Gapon said the following: > >> It looked like the issue was caused by the above write() call after a sufficiently > >> quick child process had already exited. > > > > The proper patch. > > While I don't really have a problem with this patch, I'm am a bit > curious as to why it's now needed. Could either of you downgrade to > dbus-1.2, then add something like: > > g_warning ("XXX: Trying to write '%s' to stdin", r->input); > > At line 285 (right below the "if"). I'd love to know what is being > written there normally to try and see if there is a hidden problem with > the dbus upgrade. Thanks. I'll try this as soon as I can. I'm not too sure that it will happen as I think that this is somehow timing related. I suspect that the entry is disappearing too quickly with 1.4 in some cases but is not a problem with 1.2. Perhaps some optimization? I suggest this because on at least rare occasion, 1.4 did run successfully, not because I have any clue what was happening under the covers. The systems involved are VERY different as his is a fast 64-bit SMP while mine is a slow (2 GHz) 32-bit uniprocessor. At least in my case I typically have only the two internal USB connected devices, neither of which have drivers. Not sure what USB devices Andriy might have. I'll let you know the results ASAP, but I in the middle of brining up DNS anycast for my employer and it is eating all of my free cycles until it is on-line tomorrow. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751