From owner-freebsd-gnome@FreeBSD.ORG Sun Apr 5 14:00:03 2009 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 48473106566C for ; Sun, 5 Apr 2009 14:00:03 +0000 (UTC) (envelope-from kwm@rainbow-runner.nl) Received: from smtp-vbr19.xs4all.nl (smtp-vbr19.xs4all.nl [194.109.24.39]) by mx1.freebsd.org (Postfix) with ESMTP id BB0EF8FC08 for ; Sun, 5 Apr 2009 14:00:02 +0000 (UTC) (envelope-from kwm@rainbow-runner.nl) Received: from [192.168.1.67] (kazerne.demon.nl [212.238.222.22]) by smtp-vbr19.xs4all.nl (8.13.8/8.13.8) with ESMTP id n35DmBYs080619; Sun, 5 Apr 2009 15:48:11 +0200 (CEST) (envelope-from kwm@rainbow-runner.nl) From: Koop Mast To: Nicolas In-Reply-To: <49D7C65D.2060307@wanadoo.fr> References: <49D4D56A.2030104@wanadoo.fr> <49D645FF.8050008@embarqmail.com> <1238795396.73986.5.camel@headache.rainbow-runner.nl> <49D68CB5.8020805@embarqmail.com> <49D7C5B4.1000207@embarqmail.com> <49D7C65D.2060307@wanadoo.fr> Content-Type: text/plain Date: Sun, 05 Apr 2009 15:48:30 +0200 Message-Id: <1238939310.21232.133.camel@headache.rainbow-runner.nl> Mime-Version: 1.0 X-Mailer: Evolution 2.24.5 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-gnome@freebsd.org Subject: Re: Can't write in abiword 2.6.8 X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Apr 2009 14:00:03 -0000 On Sat, 2009-04-04 at 22:43 +0200, Nicolas wrote: > I'm under i386 too ! > > Nicolas. > > > > Joseph S. Atkinson wrote: > >> I am currently updating my i386 machine that runs 7.1 and will see if > >> the problem duplicates here. > >> > > > > My i386 is fine. > > > > Maybe it's tied to amd64? > > > > Nicolas, your seeing this on a i386 machine? Can't reproduce it on i386/7-stable with gnome 2.24. I see the bug appear on amd64/8.0-current with gnome 2.26. Basically the same result Joseph had if you only look at machine architectures. -Koop