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

[Maarten Kossen]

Crashed as soon as I started LibreOffice Calc.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libreoffice-core 1:3.5.0~beta2-2ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Wed Feb 15 11:45:30 2012
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc /home/username/Documents/Quateria/Finances/2012\ -\ Finances.ods --splash-pipe=6
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f028e1fadca <_ZN14X11SalGraphics13GetResolutionERiS0_+10>: mov 0x238(%rax),%rdx
 PC (0x7f028e1fadca) ok
 source "0x238(%rax)" (0x00000238) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 X11SalGraphics::GetResolution(int&, int&) () 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-14 (1 days ago)
UserGroups: adm admin cdrom dialout libvirtd 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 #916357, 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.