soffice.bin crashed with SIGSEGV in cppu::throwException()

Bug #657555 reported by Ian! D. Allen on 2010-10-10
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
openoffice.org (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: openoffice.org

I was away from the computer overnight, and when I clicked on the document to resume editing, it died.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: openoffice.org-core 1:3.2.0-7ubuntu4.1
ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sat Oct 9 20:53:56 2010
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 Program_Self_Audit_Ian.docx -splash-pipe=5
ProcEnviron:
 LC_CTYPE=en_CA.utf8
 LC_COLLATE=C
 PATH=(custom, user)
 LANG=C
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f87931555b7: jmpq *%rax
 PC (0x7f87931555b7) ok
 source "*%rax" ok
 SP (0x7fff017a7b38) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: openoffice.org
StacktraceTop:
 cppu::throwException(com::sun::star::uno::Any const&) ()
 ucbhelper::cancelCommandExecution(com::sun::star::ucb::IOErrorCode, com::sun::star::uno::Sequence<com::sun::star::uno::Any> const&, com::sun::star::uno::Reference<com::sun::star::ucb::XCommandEnvironment> const&, rtl::OUString const&, com::sun::star::uno::Reference<com::sun::star::ucb::XCommandProcessor> const&) ()
 ?? ()
 ?? ()
 ?? ()
Title: soffice.bin crashed with SIGSEGV in cppu::throwException()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

StacktraceTop:
 cppu::throwException ()
 ucbhelper::cancelCommandExecution ()
 ?? ()
 ?? ()
 ?? ()

Changed in openoffice.org (Ubuntu):
status: New → Invalid

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

tzdata: installed version 2010l-0ubuntu0.10.04, latest version: 2010m-0ubuntu0.10.04

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
Ian! D. Allen (idallen) wrote :

Isn't is a bit silly to say that outdated time zone data invalidate this
bug report and prevent you from getting a symbolic stack trace? I'll let you
know if it happens again.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers