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

[Sami Haahtinen]

After the latest upgrades in 12.04, Libreoffice stopped working
properly. After a brief investigation it appears that soffice.bin is
exiting with SIGSEGV.

I've tried erasing the user configuration (~/.config/libreoffice)
without any effect on the situation.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libreoffice-core 1:3.5.0~beta2-2ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1
Uname: Linux 3.2.0-9-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.90-0ubuntu2
Architecture: amd64
Date: Tue Jan 17 23:11:43 2012
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --splash-pipe=6
SegvAnalysis:
 Segfault happened at: 0x7f4d2bc66dca <_ZN14X11SalGraphics13GetResolutionERiS0_+10>: mov 0x238(%rax),%rdx
 PC (0x7f4d2bc66dca) 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 2011-12-27 (21 days ago)
UserGroups: adm admin audio bacula cdrom dialout dip disk floppy fuse libvirtd lpadmin mythtv netdev plugdev vboxusers video wireshark

[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.