Bug 666251 - [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)
Summary: [abrt] openoffice.org-writer-1:3.3.0-18.2.fc14: sem_wait@@GLIBC_2.1: Process ...
Keywords:
Status: CLOSED DUPLICATE of bug 610103
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:580171c36b789f45de85e79be85...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-29 21:17 UTC by Jeff
Modified: 2010-12-30 06:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-30 06:55:20 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (2.07 KB, text/plain)
2010-12-29 21:17 UTC, Jeff 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.