soffice.bin crashed with SIGSEGV in GetVisibleArea_Impl()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libreoffice (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
1) lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04
2) apt-cache policy unoconv
unoconv:
Installed: 0.3-6
Candidate: 0.3-6
Version table:
*** 0.3-6 0
500 http://
100 /var/lib/
apt-cache policy libreoffice-calc
libreoffice-calc:
Installed: 1:3.3.3-1ubuntu1
Candidate: 1:3.3.3-1ubuntu1
Version table:
*** 1:3.3.3-1ubuntu1 0
500 http://
100 /var/lib/
1:
500 http://
1:
500 http://
3) What is expected to happen via the Terminal:
cd ~/Desktop && wget https:/
is the file is converted quickly and successfully.
4) What happens instead is it hung without creating the new document. I clicked Applications -> Office -> LibreOffice Calc and then it crash.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libreoffice-core 1:3.3.3-1ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-10-generic i686
NonfreeKernelMo
Architecture: i386
Date: Fri Jul 15 09:47:38 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: /usr/lib/
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xb21eb795 <GetVisibleArea
PC (0xb21eb795) ok
source "0x454(%edi)" (0x00000455) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
GetVisibleArea
ScAccessibleDo
CreateAccessible () from /usr/lib/
GetAccessible () from /usr/lib/
WindowEventHandler () from /usr/lib/
Title: soffice.bin crashed with SIGSEGV in GetVisibleArea_
UpgradeStatus: Upgraded to natty on 2011-05-14 (62 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #760665, 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.