Posted: Thu Jul 10, 2003 1:11 pm Post subject: crashlog from running Start OpenOffice.org
I'm trying to get up and running in OO 1.0.3. I previously had 1.0.1 running OK. Now when I run the new Start OpenOffice.org, I get a "Could not start OpenOffice.org" alert with no "Details…" button. The following is the beginning of the crashlog. Thanks for any help!
Posted: Fri Jul 11, 2003 1:31 am Post subject: Re: crashlog from running Start OpenOffice.org
LonWright wrote:
I'm trying to get up and running in OO 1.0.3. I previously had 1.0.1 running OK. Now when I run the new Start OpenOffice.org, I get a "Could not start OpenOffice.org" alert with no "Details…" button. The following is the beginning of the crashlog. Thanks for any help!
Unfortunately we need more details of your hardware and software configuration/setup, and most importantly, the rest of that particular crash log (if there are multiple entries at different times, if the crashes look the same, we just need one particular entry), before we can help further.
Sorry about that! I've included the rest of the crash log. It looks like something went awry with fonts. I'll look here for any font-related problems. In case this isn't enough, I've installed OO.org 1.0.3 in the Applications folder of a drive different from the startup one. 1.0.1 ran OK from there. It's still there--could that cause a problem? I've also installed XFree86 4.2.0 and run the Jaguar XTerm Update. My OroborOSX is v0.8b2. Do I need a newer version of this?
Thanks,
Loren Wright
<lorenw@conversent.net>
Code:
Thread 0 Crashed:
#0 0x011f29d0 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::ImplBorderWindow(Window *, SystemParentData *, unsigned long, unsigned short)
#11 0x00e2ef4c in WorkWindow::ImplInit(Window *, unsigned long, SystemParentData *)
#12 0x00e2f210 in WorkWindow::WorkWindow(Window *, unsigned long)
#13 0x000154b8 in IntroWindow_Impl::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 0x90042688 in semaphore_timedwait_signal_trap
#1 0x9003e8b4 in _pthread_cond_wait
#2 0x0029ae0c in osl_waitCondition
#3 0x0131ae6c in store::OStorePageDaemon_Impl::run(void)
#4 0x0131b9b8 in threadFunc
#5 0x0029f524 in osl_thread_start_Impl
#6 0x90020d48 in _pthread_body
Thread 2:
#0 0x9003142c 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 0x90020d48 in _pthread_body
Joined: May 25, 2003 Posts: 4752 Location: Santa Barbara, CA
Posted: Fri Jul 11, 2003 10:41 am Post subject:
OK, what you'res seeing is actually a crash in freetype. Dan fixed freetype's font support for Mac fonts which, in some cases, would cause a double-free and crash. This freetype fix didn't make it into XFree86 4.3.0 or Apple X11 betas...I have yet to check Panther.
You probably wouldn't have seen this in version 1.0.1 unless you did a full "fondu" conversion of all of your fonts.
There are two possible solutions:
1) Remove all of the ".ttf" files in your share/fonts/truetype directory and re-add them in one by one to find which one is crashing freetype.
2) Replace freetype with a more recent version containing Dan's bug fixes. There's no grpahical installer at this time, so you'll either need to get the freetype sources and build them yourself, or try to patch in a library manually.
Note that we didn't link 1.0.3 GM against this one, so it may not work. The general idea is to copy that file over whatever "libfreetype.6.3.dylib" file is living on your system (or 6.2 etc.) and see if that fixes the crash (it should...Dan's freetype fix was precisely in OpenTTFont).
We ran out of time and punted on including this fixed Freetype in our GM installer since the defaults seemed to not crash on most system configurations.
It took me a while to get back to this. When I click on the link in Terry's last message, I get "permission denied." I even registered an account with trinity, but that doesn't make a difference. I also tried the link with Fugu. Do I need a password, or is there a different way to access the ftp site? Meanwhile, I'll look for the file elsewhere.
Joined: May 25, 2003 Posts: 4752 Location: Santa Barbara, CA
Posted: Thu Jul 24, 2003 9:59 am Post subject:
There's a limit of two anonymous users on the server and no permission to go outside the anonymous file location, and I think Safari may just exclaim "broken link" if it can't get a connection. You may want to try using comand line FTP or Transfer. It definitely doesn't support SFTP however See the "NeoOffice FTP FAQ" (click on FAQ to the left) for more info.
The user accounts here are separate from FTP server accounts. I doubt I can link them without actually having to pay money for a better FTP server program (or just suck it up and move it to a better server).
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