Bug 697705 - [abrt] openoffice.org-writer-1:3.2.0-12.35.fc13: __pthread_mutex_lock: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 6 (SIGABRT)
Summary: [abrt] openoffice.org-writer-1:3.2.0-12.35.fc13: __pthread_mutex_lock: Proces...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 13
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5300f838dd7e7855e34bc95c9be...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-19 01:21 UTC by William Eastman
Modified: 2011-05-23 08:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-23 08:11:26 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (2.14 KB, text/plain)
2011-04-19 01:21 UTC, William Eastman 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description William Eastman 2011-04-19 01:21:20 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/openoffice.org3/program/swriter.bin -writer
comment: Is there something wrong with OpenOffice 3.2 or is this a memory problem?
component: openoffice.org
crash_function: __pthread_mutex_lock
executable: /usr/lib/openoffice.org3/program/swriter.bin
kernel: 2.6.34.8-68.fc13.i686
package: openoffice.org-writer-1:3.2.0-12.35.fc13
rating: 4
reason: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1303155703
uid: 500

How to reproduce
-----
1. Opened 2 calc files
2. Both crashed
3. Recovery didn't work
Comment 1 William Eastman 2011-04-19 01:21:22 UTC 
Created attachment 493056 [details]
File: backtrace
Comment 2 David Tardon 2011-04-19 06:00:22 UTC 
There is no useable information in the stack trace, unfortunately. Did it crash just after you opened the files or after you made some changes to either of them? How exactly did recovery not work? Did it crash too or did it open empty spreadsheet only?
Note You need to log in before you can comment on or make changes to this bug.