Date: Tue, 30 Jul 2002 21:33:39 -0700 From: walt <wa1ter@hotmail.com> To: freebsd-openoffice@freebsd.org Subject: Crashing 'setup' solved--halleluja!!! Message-ID: <3D4768A3.10809@hotmail.com>
next in thread | raw e-mail | index | archive | help
I got openoffice working on -current at last, and it finally turned out to be not really a -current problem. The clue was ultimately from Sobomax, who told me that my gnome- session segfaulting problem was probably due to missing Type1 fonts, or maybe a mis-configured font directory. I upgraded libgnomeprintui today and the installation program segfaulted when it got to my ttf font directory which contained some fonts from Windows I had stuck in there myself a long time ago and forgot about. I deleted those fonts and found that the libgnomeprintui install no longer segfaulted. So...I went back and tried running 'setup' from openoffice and after printing "font directory error (recovered)" it went on to actually, truly run! I'm so happy I could happily strangle Bill for including those Microsoft TrueType fonts in his crappy OS in the first place. How many wasted hours that man has cost me! Well he just wasted many more. Maybe some of you have the same problem I did. I wonder if there may be some way of asking openoffice to test for font integrity before installing. Or maybe just a general-purpose FreeBSD utility that would run through the fonts directory and check for such errors. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-openoffice" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D4768A3.10809>