soffice.bin crashed with SIGSEGV in X11SalGraphics::GetResolution()

[Mike Michalik]

Was just starting up LibreOffice to edit a document

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libreoffice-core 1:3.5.0~beta2-2ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
ApportVersion: 1.92-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Mon Feb 20 15:31:52 2012
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --writer /home/username/NFS_Storage/Clients/CA/Jobs/Services/ExpressPack/AppGridExpressPack_spd.doc --splash-pipe=6
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb1e58b6b <_ZN14X11SalGraphics13GetResolutionERlS0_+27>: mov 0x144(%eax),%edx
 PC (0xb1e58b6b) ok
 source "0x144(%eax)" (0x00000144) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 X11SalGraphics::GetResolution(long&, long&) () from /usr/lib/libreoffice/program/libvclplug_genlo.so
 ?? () from /usr/lib/libreoffice/program/libvcllo.so
 ?? () from /usr/lib/libreoffice/program/libvcllo.so
 ?? () from /usr/lib/libreoffice/program/libvcllo.so
 ?? () from /usr/lib/libreoffice/program/libvcllo.so
Title: soffice.bin crashed with SIGSEGV in X11SalGraphics::GetResolution()
UpgradeStatus: Upgraded to precise on 2012-02-20 (0 days ago)
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare

[Apport retracing service (apport)]

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 #930293, 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.