Bug 666251

Summary: [abrt] openoffice.org-writer-1:3.3.0-18.2.fc14: sem_wait@@GLIBC_2.1: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Jeff <1nomdeplume>
Component: openoffice.orgAssignee: Caolan McNamara <caolanm>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: caolanm, dtardon
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:580171c36b789f45de85e79be85df84a98d47f5c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-30 06:55:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Jeff 2010-12-29 21:17:10 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/openoffice.org3/program/swriter.bin -writer file:///home/jeff/Documents/reports/prelim/prelim_outline.odt
comment: Crashes are occasional and difficult to reproduce.  Tables tend to increase the frequency of crashes.
component: openoffice.org
crash_function: sem_wait@@GLIBC_2.1
executable: /usr/lib/openoffice.org3/program/swriter.bin
kernel: 2.6.35.10-72.fc14.i686.PAE
package: openoffice.org-writer-1:3.3.0-18.2.fc14
rating: 4
reason: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1293653012
uid: 500

How to reproduce
-----
1. Several large documents open
2. Leave documents open a few days over several sleep-wake cycles
3. Try to edit one document.
Comment 1 Jeff 2010-12-29 21:17:15 UTC 
Created attachment 471107 [details]
File: backtrace
Comment 2 David Tardon 2010-12-30 06:55:20 UTC 
the "wrong library or version mismatch" warning from gdb points to bug 610103. Hopefully 3.3.0-18.2.fc14 fixes all the related problems, so this will not happen again.

*** This bug has been marked as a duplicate of bug 610103 ***