Public bug reported:
Binary package hint: openoffice.org
This is a repeat of an earlier notification which was thought to have been
fixed.
When closing OpenOffice it causes a crash.
On the original notification last week,and subsequent emails, the system
didn't produce a backtrace.
After upgrading yesterday (Sat 7th June) it is still crashing but now at
least produces somethign which may assist in the diagnostics.
This is what my machine produced when closing the App. (Note it's on
closing the actual App itself not any individual docs etc., .... that
seems to work OK. It doesn't seem to kill the App cleanly.
Here's the copy of the backtrace that was produced.
SORRY... no..... this might be a clue in itself .
When I tried the App earlier this morning it created a backtrace on 3
successive occasions; ... I have just open and closed the App and the
KDE Crash Handler is telling me ....
.................................................................
This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents
creation of proper backtraces, or the stack frame was seriously corrupted in
the crash.
................................................................
Which is what it was doing last week, ..... Quite why it should produce
backtraces sometimes and not others may be symptomatic.
Ian
AMD64 - Ubuntu 8.04 (Kernel xxxxx.19)
ProblemType: Bug
Architecture: amd64
Date: Sun Jun 8 09:05:08 2008
DistroRelease: Ubuntu 8.04
NonfreeKernelModules: nvidia
Package: openoffice.org-core 1:2.4.1~rc2-1ubuntu1
PackageArchitecture: amd64
ProcEnviron:
PATH=/usr/lib/openoffice/program:/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: openoffice.org
Uname: Linux 2.6.24-19-rt x86_64
** Affects: openoffice.org (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug
--
crashes out on closure rather than closing cleanly
https://bugs.launchpad.net/bugs/238287
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
