Hi Stuart, I've come across a similar "bug". Keep in mind that I'm not entirely sure if this is what is going on with your machine, but I found the solution to be quite simple (ie. there is no need to even think about delving in to debugging).
What happens is that OpenOffice has detected that you did not cleanly shut down last time you used it. Perhaps you may have killed the process or whatnot. OpenOffice, in an attempt to be useful, has mamaged to recover some part of this file which you were working on before it was abruptly killed-off. The first thing OpenOffice does is to ask you if you wish to recover your last session. Unfortunately, the OpenOffice splash obscures this dialog box, and so it seems to have hung, whereas it is actually trying to ask you a question. I've forgotten how I got around this annoying "obscuration" by the splash (it was some months ago), but it probably involved holding the ALT key to try and drag the splash away, or the dialog elsewhere. You may even have to delve into your /tmp directory and personal OpenOffice directory to try to hunt out this "saved" file and remove it (so OpenOffice no longer finds the file, and will no longer ask if you wish to recover it). I hope this helps, but like I said, it does seem to be way too simple a fix when you are talking of debugging the code. David H. On Mon, 24 Feb 2003 11:08, Stuart Guthrie wrote: > Just got a nasty with Open office and am wondering the best way to > debug. > > The only change to my laptop setup is to alter the network from > 192.168.2.201 to 192.168.1.201. > > Now oocalc hangs after inital CPU flurry for 2 secs. The processes are > there in background but the splash screen seems to be waiting for > something. > > There doesn't seem to be any debug mode as an option or at least I can't > find it ooffice --help starts the app as does -help. > > Any ideas OO users? > > > Stu -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
