soffice.bin crashed with SIGSEGV in pthread_mutex_lock()

[Rand Brittain]

Binary package hint: libreoffice

I tried to open LibreOffice Writer from the Unity bar, and was told that either another instance of LibreOffice was running or my personal settings were locked. I opted not to continue. The report function popped up and asked me to report a bug. So I did!

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libreoffice-core 1:3.3.2-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Mon Apr 11 16:01:53 2011
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin -writer -splash-pipe=5
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f7bb48db394 <pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
 PC (0x7f7bb48db394) ok
 source "0x10(%rdi)" (0x00000011) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 pthread_mutex_lock () from /lib/x86_64-linux-gnu/libpthread.so.0
 osl_acquireMutex () from /usr/lib/libreoffice/program/../basis-link/ure-link/lib/libuno_sal.so.3
 ?? () from /usr/lib/libreoffice/basis3.3/program/libvclplug_gtklx.so
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: soffice.bin crashed with SIGSEGV in pthread_mutex_lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

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