@JedMeister: To find out, whether you're problem is the same as the one 
reported here, you should 1) install the -dbgsym packages for openoffice (see 
here: https://wiki.ubuntu.com/DebuggingProgramCrash) and 2) start openoffice 
under the gdb debugger like this:
  gdb /usr/lib/openoffice/program/soffice.bin
Then, in the gdb console enter
  run -writer
and reproduce the crash. If in gdb you get an output like:
  Program received signal SIGSEGV, Segmentation fault.
  0x03de0747 in WW8_SdrAttrIter::OutParaAttr () from 
/usr/lib/openoffice/basis3.1/program/libmswordli.so
then it is very likely the same problem. If you get the error in a different 
function, consider filing a new bug (ideally with a sample document triggering 
the bug) and possibly include a full backtrace (instructions here: 
https://wiki.ubuntu.com/Backtrace )

Bug #454545 is a different bug and not (at least not directly) related.

Note: The bug filed here is one that does not seem to be present when
using the original openoffice.org package (from
http://download.openoffice.org/index.html but be aware that these
packages have other issues :-/ ), but only with the ooo-build version
that is used by many linux distributions (see comment #59). The "novell-
bugs #559714 " is about ooo-build. To test their newest version (like I
did, see that bug) you would have to build it from sources, which takes
*very* long, uses ~10GB of disk space and is not really recommendable if
you're not experienced building from source.

The good news is that apparently, the crash reported here will be gone
with v3.2 as well. The code that seems to trigger the crash is no longer
present, because the word export filter has been reworked.

-- 
[ooo-build] [i386] OpenOffice crashes when saving .doc file with "notes" in it, 
Karmic.
https://bugs.launchpad.net/bugs/457220
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to