soffice.bin crashed with SIGSEGV in basegfx::B2DPolygon::getB2DPoint()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
LibreOffice |
Incomplete
|
Undecided
|
Unassigned | ||
libreoffice (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
1) lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04
2) apt-cache policy libreoffice-impress
libreoffice-
Installed: 1:3.5.0-1ubuntu4
Candidate: 1:3.5.0-1ubuntu4
Version table:
*** 1:3.5.0-1ubuntu4 0
500 http://
100 /var/lib/
3) What is expected to happen in Impress via the Terminal:
cd ~/Desktop && wget -c https:/
Save as .odp and it does not crash.
4) What happens instead is it crashes.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libreoffice-core 1:3.5.0-1ubuntu4
ProcVersionSign
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
Date: Mon Feb 27 10:37:14 2012
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
ProcCmdline: /usr/lib/
ProcEnviron:
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f33ad18487f <_ZNK7basegfx10
PC (0x7f33ad18487f) ok
source "(%rdx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
basegfx:
basegfx:
XLineStartItem
?? () from /usr/lib/
?? () from /usr/lib/
Title: soffice.bin crashed with SIGSEGV in basegfx:
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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 #936130, 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.