Bug 758403

Summary: [fix available] ath.c:193: _gcry_ath_mutex_lock: Assertion `*lock == ((ath_mutex_t) 0)' failed. gcrypt+neon+cups locking disaster
Product: Red Hat Enterprise Linux 6 Reporter: Michal Nowak <mnowak>
Component: openoffice.orgAssignee: Caolan McNamara <caolanm>
Status: CLOSED CURRENTRELEASE QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: ohudlick, tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-08 15:33:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Michal Nowak 2011-11-29 18:23:21 UTC 
Description of problem:

I get this:

*** glibc detected *** /usr/lib64/openoffice.org3/program/swriter.bin: malloc(): memory corruption (fast): 0x00007f52f5bfbc40 ***
/usr/lib64/openoffice.org3/program/soffice: line 123: 10534 Segmentation fault      (core dumped) "$sd_prog/$sd_binary" "$@"

or this:

swriter.bin: ath.c:193: _gcry_ath_mutex_lock: Assertion `*lock == ((ath_mutex_t) 0)' failed.
/usr/lib64/openoffice.org3/program/soffice: line 123: 10645 Aborted                 (core dumped) "$sd_prog/$sd_binary" "$@"

crash when I try to copy text from http://pruned.blogspot.com/2011/04/atomic-gardens.html.

I selected everything from "\\\\\ Atomic Gardens" to "peter" at the end -> Ctrl-C and then Ctrl-V in oowriter, then immediately scrolled upwards and got the crash. Similar issue is on Fedora-16 with LO but there I saw SIGSEGV in Java in ~/.xsession-errors, unlike here.

The last I can see before crash is loading of remote images, it may be related to the crash.

Version-Release number of selected component (if applicable):

openoffice.org-core-3.2.1-19.6.el6_0.5.x86_64
java-1.6.0-openjdk-1.6.0.0-1.41.1.10.4.el6.x86_64

How reproducible:

always
Comment 2 Caolan McNamara 2011-11-29 20:44:01 UTC 
Probably gcrypt + neon + cups locking woes, e.g. bug #553834, bug #569803 but #544619 and so forth. See https://bugs.g10code.com/gnupg/issue1197 for some discussion. We can backport some of the extra "treat neon as thread-unsafe and lock it ourselves" workarounds we have in later versions of LibreOffice to help.

If you have a Fedora 16 crash, let the abrt tool report it for you so we can get the backtrace for it.
Comment 3 Michal Nowak 2011-11-30 09:43:04 UTC 
(In reply to comment #2)
> If you have a Fedora 16 crash, let the abrt tool report it for you so we can
> get the backtrace for it.

Unfortunately it wasn't caught by ABRT on F-16 since the crash was in Java (I think there are some limitation to treating Java SEGV in ABRT). But I'll investigate it for sure.
Comment 5 Caolan McNamara 2012-02-08 09:24:57 UTC 
yes, extra layer of locking exists in LibreOffice
Comment 7 Suzanne Logcher 2012-02-14 23:21:47 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 8 Caolan McNamara 2012-06-08 15:33:21 UTC 
This should be fixed as a side effect of rebasing to LibreOffice 3.4.5