From owner-freebsd-gnome@FreeBSD.ORG Thu Jun 28 21:20:08 2007 Return-Path: X-Original-To: gnome@hub.freebsd.org Delivered-To: freebsd-gnome@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E3E1D16A400 for ; Thu, 28 Jun 2007 21:20:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 900B313C483 for ; Thu, 28 Jun 2007 21:20:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l5SLK8PX024677 for ; Thu, 28 Jun 2007 21:20:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l5SLK8s0024676; Thu, 28 Jun 2007 21:20:08 GMT (envelope-from gnats) Date: Thu, 28 Jun 2007 21:20:08 GMT Message-Id: <200706282120.l5SLK8s0024676@freefall.freebsd.org> To: gnome@FreeBSD.org From: Volker Cc: Subject: Re: ports/113720: editors/openoffice.org-2.2.0 and 2.2.1 fail afterupgrade of xorg 7.2 X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Volker List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2007 21:20:09 -0000 The following reply was made to PR ports/113720; it has been noted by GNATS. From: Volker To: Kevin Oberman Cc: Jung-uk Kim , freebsd-openoffice@FreeBSD.org, Janos Mohacsi , bug-followup@FreeBSD.org Subject: Re: ports/113720: editors/openoffice.org-2.2.0 and 2.2.1 fail afterupgrade of xorg 7.2 Date: Thu, 28 Jun 2007 22:48:43 +0200 On 06/28/07 22:04, Kevin Oberman wrote: >> From: Jung-uk Kim >> Date: Thu, 28 Jun 2007 15:05:40 -0400 >> >> I tracked it down and confirmed it is not OpenOffice.org's bug. >> Basically you it goes like this: OOo -> GTK+ -> Cairo -> >> libX11. :-( Luckily these issues are fixed in the latest ports. So, >> update your x11/libX11 and graphics/cairo and try again. It should >> fix the issue. > > Wow! That must have been quite a job to track down. Thanks! > > I can confirm that OOo is operating correctly again on 2 of my > systems. I won't be able to check the third until next week, but I feel > pretty sure that it will be OK, too. Updating cairo to at least version 1.4.8_1 fixes this issue. But I still wonder why OOo aborted silently w/o core dumping or making some noise on stderr. Also gdb hasn't been very helpful for this issue.