Posted: Thu Aug 07, 2003 4:35 pm Post subject: Yet another "Can't Start OpenOffice"
I am running a G4 dual 500 MHz with X11. The install seemed to go just fine. I have looked through all the faq's and searched topics in this forum and did as much as I can to get this running but still no luck. I am trying to run it from OpenOffice and from the terminal. when I try from OpenOffice I get "Could not launch OpenOffice". When I try from the terminal it seems like something might be going to happen and then I get the message, "aborted".
I have checked the location of both libdl.dylib and libdl.0.dylib. libdl.dylb was in it's /usr/lib but libdl.0.dylib was not. I created a symlink to it (at least I think I did), but that did not help. I also took out the X11R6 portion of the setenv statement.
I am not much of a UNIX person yet, but I'm learning, so I pretty much need a lot of hand holding in the process of installing some programs, and this one looks like it's going to be one of those.
Posted: Thu Aug 07, 2003 4:41 pm Post subject: Forgot to add...
I forgot to add that I installed OpenOffice on a different drive than the Mac OS so OpenOffice is not in the default Applications folder. I am setting the setenv to the true location of OpenOffice as the instructions showed after installation.
Joined: May 25, 2003 Posts: 4752 Location: Santa Barbara, CA
Posted: Thu Aug 07, 2003 8:44 pm Post subject:
Can you post the full output you see in the terminal? Unfortunately, simply the fact that it can't start doesn't really give enough information to troubleshoot the problem.
Joined: May 25, 2003 Posts: 4752 Location: Santa Barbara, CA
Posted: Fri Aug 08, 2003 9:43 pm Post subject:
Aargh Not your fault, more openoffice's. Something's going drastically wrong here if you're just seeing "Abort" at the terminal. I haven't seen things like this since the early days when we were having problems with X servers. Unfortunately it means we've not no more clue about why it's failing, except that it's serious.
One thing, though...can you try using:
setenv DISPLAY :0.0
instead of
setenv DIPSLAY localhost:0
I know if there's problems resolving the IP address for "localhost" X11 apps with the above DISPLAY will hork. Another thing to try...are you using Apple X11? If so, launch X11.app and go to Applications > xterm. Try launching from the xterm, but without the "setenv DISPLAY" command.
If the display isn't the problem (it's just a shot in the dark based on problems I've had in the past), then we'll have to do some differnet things to extract enough information to track down what the problem is.
Posted: Sat Aug 09, 2003 7:44 am Post subject: Still no luck
Yes, I am using Apple's X11. In defaults to Xterm when I launch it. I have now tried launching it with and with out "setenv" as well as setenv:0 and setenv:0.0 Still the same thing.
I also tried unistalling and reinstalling. As part of uninstalling, I removed ~/.sversionrc and xinitrc. Before I uninstalled, I copied their contents. After reinstalling, I checked these files and they were the same. Here is the copy.
This is the only version of xinitrc I found on my system.
I removed both /Users/kimmacke/Library/Preferences/OpenOffice.Start.plist and
~/sversionrc before I reinstalled. I tried running StartOpenOffice again. Still get a dialog box that simply says "Can't Launch OpenOffice". Also, I don't seem to have openoffce.start.plist anymore.
Some additional info:
1. I don't think I have XDarwin - but I don't need it, do I?
2. I installed OpenOffice on a different partition from my system
Hope some of this may give you a clue about what's going on.
Posted: Sun Aug 10, 2003 1:36 am Post subject: Re: Still no luck
mackeyka wrote:
I removed both /Users/kimmacke/Library/Preferences/OpenOffice.Start.plist and
~/sversionrc before I reinstalled. I tried running StartOpenOffice again. Still get a dialog box that simply says "Can't Launch OpenOffice". Also, I don't seem to have openoffce.start.plist anymore.
Some additional info:
1. I don't think I have XDarwin - but I don't need it, do I?
2. I installed OpenOffice on a different partition from my system
Hope some of this may give you a clue about what's going on.
You don't need XDarwin, but if you have installed it previously, please tell us.
Installing OOo on a different partiition is no problem 99% of the time, except you should tell us the exact volume name of this partition. I also assume all your partitions are HFS+.
You won't see a ~/Library/Preferences/org.OpenOffice.Start.plist (note the correct name) file, until after you quit "Start OpenOffice.org" the first time.
When "Start OpenOffice.org" displays that error, is there a "Details…" button in the Alert - if so, please click the "Details…" button and give us the details (if any). Otherwise, while the Alert is displayed, open a Terminal session, type the following, and give us the details (if any) :
cat /tmp/StartOO*
As was said previously we have seen the "Abort" problem during early development versions of OOo, and I can't remember the cause. I would suggest configuring your machine to use only 1 CPU. For info on how to do that, visit :
Joined: May 25, 2003 Posts: 4752 Location: Santa Barbara, CA
Posted: Thu Aug 14, 2003 9:46 am Post subject:
Unfortunately, this is just incredibly difficult to track down. The mode of failure gives us no information about what could be causing it In addition to Terry's dual-CPU abort failure I've seen this Abort issue with old versions of Orobor (pre 0.8b2...was a window manager hints issue, IIRC) and on initial 638C builds where it was a compiler casting bug with non-typesafe upcasting. I'm hoping the latter isn't an issue any more...but Apple X11b3 has been having issues with window manager hints in 1.1...
If anyone who's experiencing this Abort error has gdb on their system, I'd like to try to debug this and put a breakpoint on XError (I belive the symbol may be named "_XError" without quotes). If not hit, I believe that we could rule out any X server or window manager issues.
Posted: Sun Aug 17, 2003 6:45 pm Post subject: short break from installing
Well, other life matters interrupted, so I had to take a little break. Thinking I may just wait until I upgrade to OS 10.3 and try installing again at that time.
I did capture the crash log "soffice.bin.crash.log and will include that here to see if that helps anyone figure out what's happining.
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
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 0x90042668 in semaphore_timedwait_signal_trap
#1 0x9003e894 in _pthread_cond_wait
#2 0x0029ae0c in osl_waitCondition
#3 0x00c75e6c in store::OStorePageDaemon_Impl::run(void)
#4 0x00c769b8 in threadFunc
#5 0x0029f524 in osl_thread_start_Impl
#6 0x90020d28 in _pthread_body
Thread 2:
#0 0x9003140c 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 0x90020d28 in _pthread_body
Posted: Sun Aug 17, 2003 7:24 pm Post subject: Found my problem
This forum is a great place.
I was about to give up for a while but then I read "plc's" post with a problem that sounded a lot like mine. As it turns out his solution was just what I needed. There were a number of truetypefonts in my OpenOffice fonts folder which were 0 bytes. I moved them to a temporary folder and was then able to start my installation of OpenOffice.
Thanks to OPENSTEP and other for their patient assistance.
Joined: May 25, 2003 Posts: 4752 Location: Santa Barbara, CA
Posted: Mon Aug 18, 2003 9:06 pm Post subject:
Yup, OpenTTFont is a dead giveaway that you're having issues with Asian, Hebrew, or other fonts. I'm glad that you found it. If I can find a way to remove the SQL injection security hole, I guess I should enable the search feature here. There's beginning to be enough content that it's a useful tool...
I should have mentioned the OpenTTFont crash in the launching FAQ, but it is quite disturbing that OOo was crashing on you there and not leaving around crashdumps. I've actually had it happen a couple of times on me as well, and not just with OOo. The crashdump gets left behind, but with a bogus process name.
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
Not your fault, more openoffice's. Something's going drastically wrong here if you're just seeing "Abort" at the terminal. I haven't seen things like this since the early days when we were having problems with X servers. Unfortunately it means we've not no more clue about why it's failing, except that it's serious.
