soffice.bin crashed with SIGSEGV in pthread_mutex_lock()

Bug #729145 reported by gogo
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
LibreOffice
Incomplete
Undecided
Unassigned
libreoffice (Ubuntu)
Confirmed
Medium
Unassigned
openoffice.org (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: libreoffice

soffice.bin crashed with SIGSEGV in pthread_mutex_lock()

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libreoffice-core 1:3.3.1-1ubuntu4
Uname: Linux 2.6.38-020638rc7-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Fri Mar 4 16:46:42 2011
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin -writer /media/SEAGATE200/backup500GB/Documents/FPZ/Tehnologija\ TK\ prometa\ I/AnalizaTKmreze.doc -splash-pipe=5
ProcEnviron:
 LANGUAGE=hr_HR:hr:en_US:en
 LANG=hr_HR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ff52ad3c394 <pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
 PC (0x7ff52ad3c394) 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/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/libglib-2.0.so.0
 ?? () from /lib/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

Revision history for this message
gogo (trebelnik-stefina) wrote :
gogo (trebelnik-stefina)
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __pthread_mutex_lock (mutex=0x1) at pthread_mutex_lock.c:50
 osl_acquireMutex () from /usr/lib/libreoffice/program/../basis-link/ure-link/lib/libuno_sal.so.3
 userEventFn () from /usr/lib/libreoffice/basis3.3/program/libvclplug_gtklx.so
 g_main_dispatch (context=0x2287b80) at /build/buildd/glib2.0-2.28.1/./glib/gmain.c:2440
 g_main_context_dispatch (context=0x2287b80) at /build/buildd/glib2.0-2.28.1/./glib/gmain.c:3013

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in libreoffice (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
penalvch (penalvch) wrote :

gogo, thank you for reporting this bug and helping make Ubuntu better. Please answer the following questions:

+ Could you please attach the AnalizaTKmreze.doc file that was open when this crash occurred?
+ Is this issue reproducible?
+ What specific steps should we take to reproduce the crash?

Changed in libreoffice (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.]

Changed in libreoffice (Ubuntu):
status: Incomplete → Expired
penalvch (penalvch)
Changed in libreoffice (Ubuntu):
status: Expired → New
Revision history for this message
Colan Schwartz (colan) wrote :
Changed in libreoffice (Ubuntu):
status: New → Confirmed
Revision history for this message
Björn Michaelsen (bjoern-michaelsen) wrote :

Incomplete => needs upstream bug as per http://wiki.documentfoundation.org/BugReport

Changed in openoffice.org (Ubuntu):
status: New → Won't Fix
Changed in df-libreoffice:
status: New → Incomplete
Revision history for this message
Björn Michaelsen (bjoern-michaelsen) wrote :

Judging by the description of bug 807088 this is yet another sideeffect of bug 562027.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.