Bug 663780 - [abrt] openoffice.org-writer-1:3.2.0-12.33.fc13: _gcry_ath_mutex_lock: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 6 (SIGABRT)
Summary: [abrt] openoffice.org-writer-1:3.2.0-12.33.fc13: _gcry_ath_mutex_lock: Proces...
Keywords:
Status: CLOSED DUPLICATE of bug 661809
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 13
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8dbac94a115d95e03ed0ba4908f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-16 20:20 UTC by Máté Wierdl
Modified: 2010-12-16 20:38 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-16 20:38:10 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (93.72 KB, text/plain)
2010-12-16 20:20 UTC, Máté Wierdl 		no flags Details
View All

Description Máté Wierdl 2010-12-16 20:20:45 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/swriter.bin -writer
component: openoffice.org
crash_function: _gcry_ath_mutex_lock
executable: /usr/lib64/openoffice.org3/program/swriter.bin
kernel: 2.6.34.7-63.fc13.x86_64
package: openoffice.org-writer-1:3.2.0-12.33.fc13
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1292528308
uid: 503

How to reproduce
-----
1. During editing a new file.  Pressed a letter on the keyboard, and crashed.
2.
3.
Comment 1 Máté Wierdl 2010-12-16 20:20:47 UTC 
Created attachment 469214 [details]
File: backtrace
Comment 2 Caolan McNamara 2010-12-16 20:38:10 UTC 
Nah, there was another thread trying to download images from a website or something of that nature. That's the problem. Lets add the extra bits back to F-13 for the next respin of that.

*** This bug has been marked as a duplicate of bug 661809 ***
Note You need to log in before you can comment on or make changes to this bug.