From owner-freebsd-openoffice@FreeBSD.ORG Fri Apr 4 07:06:48 2003 Return-Path: Delivered-To: freebsd-openoffice@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CE8937B401 for ; Fri, 4 Apr 2003 07:06:48 -0800 (PST) Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1454A43FB1 for ; Fri, 4 Apr 2003 07:06:47 -0800 (PST) (envelope-from mb@imp.ch) Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9]) by mail.imp.ch (8.12.6p2/8.12.3) with ESMTP id h34F6jNT040812; Fri, 4 Apr 2003 17:06:45 +0200 (CEST) (envelope-from Martin.Blapp@imp.ch) Date: Fri, 4 Apr 2003 17:06:45 +0200 (CEST) From: Martin Blapp To: Bartosz Fabianowski In-Reply-To: <3E8A8F58.1080702@chillt.de> Message-ID: <20030404170601.V37965@cvs.imp.ch> References: <20030329191134.R99771@cvs.imp.ch> <200303312101.47840.avleeuwen@piwebs.com> <3E8A8F58.1080702@chillt.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: openoffice@freebsd.org Subject: Re: FreeBSD: OO.org 1.1Beta packages available. X-BeenThere: freebsd-openoffice@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting OpenOffice to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 15:06:48 -0000 Hi, > It seems that the setup program does not correctly set the "Temporary > files" path and OpenOffice.org is unable to create any temporary files, > which are necessary for correct operation. Go to the "Tools->Options..." > menu in OpenOffice.org, in the "Options" dialog choose > "OpenOffice.org->Paths" and change the path labelled as "Temporary > files" to "/var/tmp". You then then need to restart OpenOffice.org and > it should be able to load and save files just fine. You will have to > repeat this for all user that want to use OpenOffice.org, except for root. > > By the way, this also seems to fix the "AutoPilot" bug reported earlier. I think I've found the bug in the OOO source causing this. In the next beta package (next week) this will be fixed. Martin