From owner-freebsd-openoffice@FreeBSD.ORG Mon Apr 21 22:19:58 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 8517B37B401 for ; Mon, 21 Apr 2003 22:19:58 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id E744F43FCB for ; Mon, 21 Apr 2003 22:19:55 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (scratch.catspoiler.org [192.168.101.3]) by gw.catspoiler.org (8.12.6/8.12.6) with ESMTP id h3M5JnXB025837 for ; Mon, 21 Apr 2003 22:19:53 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200304220519.h3M5JnXB025837@gw.catspoiler.org> Date: Mon, 21 Apr 2003 22:19:49 -0700 (PDT) From: Don Lewis To: freebsd-openoffice@FreeBSD.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Subject: openoffice-devel problems on recent -current 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: Tue, 22 Apr 2003 05:19:58 -0000 I just installed openoffice-devel on a recent -current box. 5.0-CURRENT FreeBSD 5.0-CURRENT #61: Sat Apr 19 00:36:17 PDT 2003 I'm having trouble getting it to run though. The first problem is that setup bombs out near, after populating most of ~/OpenOffice.org644/ and ~/.kde/, but before the "registering components" stage. % setup crash_report: not found Abort (core dumped) If I try to run scalc, I get an alert window that says: The application cannot be started. Unable to create instance of com.sun.star.office.SplashScreen and it exits when I hit the "Ok" button. Another problem I ran across is that if I blow away ~/OpenOffice.org644 without removing the entry from ~/.sversionrc, that when I attempt to start the software it attempts to "repair" the missing directory by doing the much larger "Local Installation" instead of the smaller "Workstation Installation". It doesn't ask which I'd prefer, but just starts writing. Unfortunately my home directory is NFS mounted and this triggered a bug in the NFS client code, which require a reboot. 1.0.3 works fine on this machine.