soffice.bin crashed with SIGSEGV in Application::GetSolarMutex()

[Artur Frysiak]

soffice.bin crashed with SIGSEGV in Application::GetSolarMutex()

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: libreoffice-core 1:4.4.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
Uname: Linux 3.19.0-13-generic x86_64
ApportVersion: 2.17-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Apr 12 22:16:28 2015
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2014-01-05 (462 days ago)
InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc file:///home/username/Dokumenty/pko-kredyt-2014.xls --splash-pipe=5
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pl_PL.UTF-8
 SHELL=/bin/zsh
 LD_LIBRARY_PATH=<set>
SegvAnalysis:
 Segfault happened at: 0x7f008d50e44a <_ZN11Application13GetSolarMutexEv+10>: mov 0x8(%rax),%rdi
 PC (0x7f008d50e44a) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 Application::GetSolarMutex() () from /usr/lib/libreoffice/program/libmergedlo.so
 ?? () from /usr/lib/libreoffice/program/libmergedlo.so
 ?? () from /usr/lib/libreoffice/program/libmergedlo.so
 ?? () from /usr/lib/libreoffice/program/libmergedlo.so
 __run_exit_handlers (status=0, listp=0x7f008a730698 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
Title: soffice.bin crashed with SIGSEGV in Application::GetSolarMutex()
UpgradeStatus: Upgraded to vivid on 2015-04-11 (1 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev pulse-access sambashare sudo

[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 #1418551, 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.