soffice.bin crashed with SIGSEGV

Bug #941788 reported by Britt Yazel
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libreoffice (Ubuntu)
New
Undecided
Unassigned

Bug Description

After attempting click the "bibliography database" under the "tools" menu in LibreOffice Writer this error comes up. It is repeatable and happens every single time.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libreoffice-core 1:3.5.0-1ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Sun Feb 26 22:57:15 2012
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --splash-pipe=6
SegvAnalysis:
 Segfault happened at: 0x7f74d35e4909: mov (%rbx),%rax
 PC (0x7f74d35e4909) ok
 source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 ?? () from /usr/lib/libreoffice/program/../program/libbiblo.so
 ?? () from /usr/lib/libreoffice/program/../program/libbiblo.so
 ?? () from /usr/lib/libreoffice/program/../program/libbiblo.so
 ?? () from /usr/lib/libreoffice/program/../program/libbiblo.so
 ?? () from /usr/lib/libreoffice/program/../program/libbiblo.so
Title: soffice.bin crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2012-02-19 (8 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Britt Yazel (bwyazel) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #927189, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.