Posted: Wed Jun 02, 2004 10:10 pm Post subject: Help, OOo suddenly stopped working
I managed to get OOo to function after some work a couple-few days ago, but now it's stopped working. I haven't changed anything on the system since it last functioned that should have affected anything*. StartOOo just gives a "Couldn't start OOo" error with no details, /tmp/Start* doesn't have anything stored in it, and I don't know how to interperate the Console logs.
* I've messed around with Apache (though it's not running when I tried starting OOo) and changed the password on a different account than the one I installed OOo under and am trying to run OOo under. I believe those are the only changes I've made to the system at all since it worked.
Posted: Thu Jun 03, 2004 12:37 am Post subject: Re: Help, OOo suddenly stopped working
phreelance wrote:
I managed to get OOo to function after some work a couple-few days ago, but now it's stopped working. I haven't changed anything on the system since it last functioned that should have affected anything*. StartOOo just gives a "Couldn't start OOo" error with no details, /tmp/Start* doesn't have anything stored in it, and I don't know how to interperate the Console logs.
1) Can you successfully launch XDarwin or OroborOSX manually?
2) Use the Console application - check the Preferences menu item and click on the Crashes tab - if the options are not enabled, enable them. Look at the console.log - see if any entries refer to CrashReporter logs being written when you have the problem with OOo - if so, open up the CrashReporter log for probably "soffice.bin", scroll to the bottom of the log, and if the last crash report is not too long, paste the details here.
I have seen problems like you describe when XDarwin starts to launch but then crashes (because of something changed in the system). We need to find (by process of elimination) if the problem is with the X11 Window system, OOo itself, or "Start OpenOffice.org".
Posted: Thu Jun 03, 2004 9:34 pm Post subject: Re: Help, OOo suddenly stopped working
I can launch both XDarwin and OroborOSX independently. (OroborOSX does come up when launched from StartOOo.) The console has creashes being logged, I just turned on the automatically opening crash logs.
Posted: Fri Jun 04, 2004 12:43 am Post subject: Re: Help, OOo suddenly stopped working
phreelance wrote:
I can launch both XDarwin and OroborOSX independently. (OroborOSX does come up when launched from StartOOo.) The console has creashes being logged, I just turned on the automatically opening crash logs.
Joined: May 25, 2003 Posts: 4752 Location: Santa Barbara, CA
Posted: Sat Jun 05, 2004 9:01 am Post subject:
Underneath that portion of soffice.bin will probably be a whole sequence of thred stack traces. They have lines like "Thread 0 Crashed" and then a bunch of lines.
If the one that says "Crashed" contains an FT entry, you'll need to get rid of your fonts. There are some older threads here that should explain how to do this.
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x01907520
Thread 0 Crashed:
#0 0x011f2f7c in OpenTTFont
#1 0x0118b830 in psp::PrintFontManager::_analyzeTrueTypeFile(psp::PrintFontManager::PrintFont *) const
#2 0x01189440 in psp::PrintFontManager::_analyzeFontFile(int, rtl::OString const &, bool, _STL::list<psp, _STL::allocator<psp> > const &, _STL::list<psp::PrintFontManager::PrintFont *, _STL::allocator<OString *> > &) const
#3 0x0118ceec in psp::PrintFontManager::_initialize(void *)
#4 0x01187d60 in psp::PrintFontManager::_get(void)
#5 0x00eaa364 in FontLookup::_BuildSet(_STL::hash_set<FontLookup, FontLookup::hash, FontLookup::equal, _STL::allocator<FontLookup> > &)
#6 0x00eaabb4 in SalDisplay::_GetXlfdList(void)
#7 0x00eaddb0 in SalGraphics::_GetDevFontList(ImplDevFontList *)
#8 0x00e0d910 in Window::_ImplInit(Window *, unsigned long, SystemParentData *)
#9 0x00ddda88 in ImplBorderWindow::_ImplInit(Window *, unsigned long, unsigned short, SystemParentData *)
#10 0x00dddb64 in ImplBorderWindow::_(Window *, SystemParentData *, unsigned long, unsigned short)
#11 0x00e2ef4c in WorkWindow::_ImplInit(Window *, unsigned long, SystemParentData *)
#12 0x00e2f210 in WorkWindow::_(Window *, unsigned long)
#13 0x000154b8 in IntroWindow_Impl::_(Bitmap const &)
#14 0x0000d034 in Desktop::_OpenStartupScreen(void)
#15 0x00007998 in Desktop::_Main(void)
#16 0x00d36f78 in SVMain(void)
#17 0x00eb8960 in main
#18 0x000026b0 in _start
#19 0x000024e0 in start
Thread 1:
#0 0x90042588 in semaphore_timedwait_signal_trap
#1 0x9003e7b4 in _pthread_cond_wait
#2 0x0029ae0c in osl_waitCondition
#3 0x00cb1e6c in store::OStorePageDaemon_Impl::_run(void)
#4 0x00cb29b8 in threadFunc
#5 0x0029f524 in osl_thread_start_Impl
#6 0x90020c28 in _pthread_body
Thread 2:
#0 0x9003130c in accept
#1 0x002aa474 in osl_acceptPipe
#2 0x001008a4 in vos::OPipe::_accept(vos::OStreamPipe &)
#3 0x00017258 in desktop::OfficeIPCThread::_run(void)
#4 0x000fb550 in vos::__cpp_OThread_WorkerFunction(void *)
#5 0x0029f524 in osl_thread_start_Impl
#6 0x90020c28 in _pthread_body
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x01907520
Thread 0 Crashed:
#0 0x011f2f7c in OpenTTFont
#1 0x0118b830 in psp::PrintFontManager::_analyzeTrueTypeFile(psp::PrintFontManager::PrintFont *) const
#2 0x01189440 in psp::PrintFontManager::_analyzeFontFile(int, rtl::OString const &, bool, _STL::list<psp, _STL::allocator<psp> > const &, _STL::list<psp::PrintFontManager::PrintFont *, _STL::allocator<OString *> > &) const
#3 0x0118ceec in psp::PrintFontManager::_initialize(void *)
#4 0x01187d60 in psp::PrintFontManager::_get(void)
#5 0x00eaa364 in FontLookup::_BuildSet(_STL::hash_set<FontLookup, FontLookup::hash, FontLookup::equal, _STL::allocator<FontLookup> > &)
#6 0x00eaabb4 in SalDisplay::_GetXlfdList(void)
#7 0x00eaddb0 in SalGraphics::_GetDevFontList(ImplDevFontList *)
#8 0x00e0d910 in Window::_ImplInit(Window *, unsigned long, SystemParentData *)
#9 0x00ddda88 in ImplBorderWindow::_ImplInit(Window *, unsigned long, unsigned short, SystemParentData *)
#10 0x00dddb64 in ImplBorderWindow::_(Window *, SystemParentData *, unsigned long, unsigned short)
#11 0x00e2ef4c in WorkWindow::_ImplInit(Window *, unsigned long, SystemParentData *)
#12 0x00e2f210 in WorkWindow::_(Window *, unsigned long)
#13 0x000154b8 in IntroWindow_Impl::_(Bitmap const &)
#14 0x0000d034 in Desktop::_OpenStartupScreen(void)
#15 0x00007998 in Desktop::_Main(void)
#16 0x00d36f78 in SVMain(void)
#17 0x00eb8960 in main
#18 0x000026b0 in _start
#19 0x000024e0 in start
Thread 1:
#0 0x90042588 in semaphore_timedwait_signal_trap
#1 0x9003e7b4 in _pthread_cond_wait
#2 0x0029ae0c in osl_waitCondition
#3 0x00cb1e6c in store::OStorePageDaemon_Impl::_run(void)
#4 0x00cb29b8 in threadFunc
#5 0x0029f524 in osl_thread_start_Impl
#6 0x90020c28 in _pthread_body
Thread 2:
#0 0x9003130c in accept
#1 0x002aa474 in osl_acceptPipe
#2 0x001008a4 in vos::OPipe::_accept(vos::OStreamPipe &)
#3 0x00017258 in desktop::OfficeIPCThread::_run(void)
#4 0x000fb550 in vos::__cpp_OThread_WorkerFunction(void *)
#5 0x0029f524 in osl_thread_start_Impl
#6 0x90020c28 in _pthread_body
Joined: May 25, 2003 Posts: 4752 Location: Santa Barbara, CA
Posted: Tue Jun 08, 2004 9:36 pm Post subject:
Yup, you are experiencing the freetype error. This happened with libfreetypes that were included with early versions of XFree86 and with Apple X11. Dan fixed them, but the patches weren't incorporated into all of the projects that had thier own copies of libfreetype that were independent of the main distribution (just like OOo).
Check out this FAQ entry for more references on how to workaround the problem:
Posted: Fri Jun 11, 2004 9:58 pm Post subject: TTFont errors (was Re: Help, OOo suddenly stopped working)
Okay so I downloaded the dylib and used it to replace my old one. This fixed it so I can run OOo with XDarwin. I still get the TTFont crash when I try to open OOo with OroborOSX though; do you know what would cause that? Just curious since I prefer Oroborosx a bit (faster load-up time primarily, though it is prettier too)
Once again, thanks a bundle for helping this newbie walk through things.
Joined: May 25, 2003 Posts: 4752 Location: Santa Barbara, CA
Posted: Fri Jun 11, 2004 11:20 pm Post subject:
If it's still crashing with the new dylib, then it may be some form of a corrupted font file. The only thing I can think of next would be to search for any files in /applications/openoffice.org1.0.3/share/fonts/truetype that are 0K in length or are not "english" fonts.
It's always struck me odd since I never have had font problems myself. then again, I don't have anything except default os x fonts :/
Posted: Sun Jun 13, 2004 3:20 pm Post subject: OroborOSX font problems
I didn't find any in there with a 0k size. There are a few that aren't "English", but I use those fonts I have a bunch of old OS9 fonts which fondu didn't seem to look at, but all my OSX fonts are standard ones. Guess I'll just have to use XDarwin instead of OroborOSX for the time being.
Joined: May 25, 2003 Posts: 4752 Location: Santa Barbara, CA
Posted: Sun Jun 13, 2004 11:44 pm Post subject:
One problem may be that OroborOSX contains its own internal version of XDarwin. Are you running the latest version of OroborOSX? The latest version I know of is 0.9, the version required for Panther compatibility.
If you are running the latest version, please let me know so I can forward along the issue for Adrian
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You cannot download files in this forum
I have a bunch of old OS9 fonts which fondu didn't seem to look at, but all my OSX fonts are standard ones. Guess I'll just have to use XDarwin instead of OroborOSX for the time being.