Date: Tue, 3 Jul 2007 15:24:56 -0700 From: Gary Kline <kline@tao.thought.org> To: "[LoN]Kamikaze" <LoN_Kamikaze@gmx.de> Cc: freebsd-questions@freebsd.org Subject: Re: OpenOffice.org 2.2.1 quits on launch Message-ID: <20070703222456.GA83628@thought.org> In-Reply-To: <468A4F4A.1060500@gmx.de> References: <20070703121408.GA357@it.ca> <468A4F4A.1060500@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 03, 2007 at 03:29:46PM +0200, [LoN]Kamikaze wrote: > Paul Chvostek wrote: > > Hiya. > > > > I just did my Xorg upgrade, which included an upgrade of OpenOffice.org > > to version 2.2.1. > > > > Now, when I launch OO, it complains not at all, but opens no windows. > > It doesn't take much time: > > > > > time openoffice.org-2.2.1 > > 0.727u 0.267s 0:02.06 47.5% 301+915k 1+0io 0pf+0w > > > > > > > The shell wrapper (/usr/local/openoffice.org-2.2.1/program/soffice) is > > definitely running soffice.bin. But the binary does nothing except > > return an exit value of 78, which is *not* trapped by the shell wrapper. > > And I don't know what 78 means. > > > > I've seen some hints in other operating systems' forums that OO does > > strange things when fonts with questionable metrics are installed, so > > I've uninstalled a bunch of things that I can probably do without, and > > replaced the rest with `portupgrade -fR xorg-fonts-7.2`, to no avail. > > > > Running soffice.bin in an strace produces gobs of output that I don't > > know how to interpret. The last few "useful" lines from strace refer to > > libraries like libglib, libiconv, etc, so I've reinstalled glib2 and > > libiconv and some others, also to no avail. > > > > I'm in 6.1-RELEASE-p17. Java (diablo-jdk1.5.0) works standalone, TTF > > fonts work in other apps, and OO was built with these in /etc/make.conf: > > WITH_EVOLUTION2=yes > > WITH_TTF_BYTECODE_ENABLED=yes > > WITH_SYSTEM_FREETYPE=yes > > > > Any suggestions? Has anyone else seen and solved this? > > > > Thanks. > > > > Try env OO_FORCE_DESKTOP=none Setting this does almost nothing, running even as root. When a file finally does open, setecting All -- or any other command -- causes an immediate crash. Not even a core file to look at. ... . -- Gary Kline kline@thought.org www.thought.org Public Service Unix
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070703222456.GA83628>