Date: Tue, 22 Apr 2003 08:38:35 +0200 (CEST) From: Martin Blapp <mb@imp.ch> To: Don Lewis <truckman@freebsd.org> Cc: freebsd-openoffice@freebsd.org Subject: Re: openoffice-devel problems on recent -current Message-ID: <20030422083532.M95995@cvs.imp.ch> In-Reply-To: <200304220519.h3M5JnXB025837@gw.catspoiler.org> References: <200304220519.h3M5JnXB025837@gw.catspoiler.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > 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) Hmm. The crash_report: not found is normal, but it should not core after that. > 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. That happens if you don't start it from the wrappers. Either you use a wrapper or you cd into the program dir. > 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. That's really bad. Can you get repeat the panic and get a backtrace ? I'll try to fix the behaviour in openoffice. Martin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030422083532.M95995>