soffice.bin crashed with SIGSEGV

Bug #950695 reported by Blümchen Blau
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libreoffice (Ubuntu)
New
Undecided
Unassigned

Bug Description

While trying to reformat a .xls and delete some Makros (which were deactivated at start) LOffice crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libreoffice-core 1:3.5.0-2ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
ApportVersion: 1.94.1-0ubuntu1
Architecture: i386
Date: Fri Mar 9 11:05:00 2012
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120201.2)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc /home/username/Arbeitsfläche/AFBOE\ Besetzungsliste\ Stand\ 2012-03-08\ 17.45\ Uhr.xls --splash-pipe=6
SegvAnalysis:
 Segfault happened at: 0xb061b077: mov (%eax),%edx
 PC (0xb061b077) ok
 source "(%eax)" (0x00380030) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 ?? () from /usr/lib/libreoffice/program/../share/extensions/menubar/Linux_x86/menubar.uno.so
 ?? () from /usr/lib/libreoffice/program/../share/extensions/menubar/Linux_x86/menubar.uno.so
 ?? () from /usr/lib/libreoffice/program/libsfxlo.so
 ?? () from /usr/lib/libreoffice/program/libsfxlo.so
 ?? () from /usr/lib/libreoffice/program/libsfxlo.so
Title: soffice.bin crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin nvram plugdev sambashare sudo vboxusers

Revision history for this message
Blümchen Blau (bluemchen-blau) 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 #950387, 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-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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