soffice.bin crashed with SIGSEGV in pthread_mutex_lock()

[Colan Schwartz]

I initiated a system restart and then briefly got a message that Libreoffice was blocking the shutdown. This only lasted a few seconds, after which the system restarted. (I didn't need to kill it.) Once the system came back up, I saw this error.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libreoffice-core 1:3.3.2-1ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Jul 7 00:54:22 2011
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin -draw -splash-pipe=5
ProcEnviron:
 LANGUAGE=en_CA:en
 LANG=en_CA.UTF-8
 SHELL=/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x7fc31ab2c394 <pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
 PC (0x7fc31ab2c394) 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: Upgraded to natty on 2011-04-30 (67 days ago)
UserGroups: adm admin cdrom dialout dip fax floppy fuse logcheck lp lpadmin mail netdev plugdev powerdev sambashare tape vboxusers video

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