soffice.bin crashed with SIGSEGV

Bug #654382 reported by Ian! D. Allen on 2010-10-04
This bug affects 1 person
Affects Status Importance Assigned to Milestone (Ubuntu)

Bug Description

Binary package hint: (Ubuntu) bug reporting guidelines:
If possible please report the bug about from inside the
application: Help -> Report a Bug

That menu item does not exist in OpenOffice 3.2 Calc

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: 1:3.2.0-7ubuntu4.1
ProcVersionSignature: Ubuntu 2.6.32-25.44-generic
Uname: Linux 2.6.32-25-generic x86_64
Architecture: amd64
Date: Mon Oct 4 00:57:02 2010
Disassembly: => 0x7feb2b5c4ed9: Cannot access memory at address 0x7feb2b5c4ed9
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/openoffice/program/soffice.bin
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: /usr/lib/openoffice/program/soffice.bin i.csv -splash-pipe=5
 PATH=(custom, user)
 Segfault happened at: 0x7feb2b5c4ed9: Cannot access memory at address 0x7feb2b5c4ed9
 PC (0x7feb2b5c4ed9) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: soffice.bin crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Ian! D. Allen (idallen) wrote :
visibility: private → public

 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace

Ian! D. Allen thank you for reporting this problem and helping make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
* Could you please attach the Calc file opened when this crash occurred?

This will help us to find and resolve the problem.

Changed in (Ubuntu):
status: New → Incomplete
Ian! D. Allen (idallen) wrote :

That bug was four months ago. I don't run that software or that operating system any more. No further information.

P.S. There is still no "Report a Bug" entry under "Help" in 3.2.1
OOO320m19 (Build:9505) ooo-build, Ubuntu package 1:3.2.1-7ubuntu1.1

Ian! D. Allen , we are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers