Bug 637738

Summary: [abrt] using neon not-thread safe (through no fault of its own)
Product: [Fedora] Fedora Reporter: balustre <balustre>
Component: openoffice.orgAssignee: Caolan McNamara <caolanm>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: caolanm
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:31e307b37d4f76885791f3a17f782bfec7d8d51c
Fixed In Version: openoffice.org-3.2.0-12.33.fc13 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-27 22:34:24 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 balustre 2010-09-27 09:48:34 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/swriter.bin -writer
component: openoffice.org
crash_function: raise
executable: /usr/lib64/openoffice.org3/program/swriter.bin
kernel: 2.6.34.6-54.fc13.x86_64
package: openoffice.org-writer-1:3.2.0-12.31.fc13
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1285540538
uid: 500

How to reproduce
-----
1. Copier une image sur internet
2. Ouvrir Open Office Writer
3. Coller l'image sur open office
Comment 1 balustre 2010-09-27 09:48:37 UTC 
Created attachment 449857 [details]
File: backtrace
Comment 2 Caolan McNamara 2010-09-27 10:03:37 UTC 
This is probably that pesky threading problem we tried to solve before, but which broke cups. Thread 1 and Thread 7 are both using neon, and while *neon* is thread-safe, the underlying libraries they're using is only thread safe if initialized correctly the first time. Cups ends up being the first one to initialize it, but not thread-safely, hence the problems.

Bottom line is that we probably have to mutex up our neon stuff :-(
Comment 3 balustre 2010-09-27 10:10:12 UTC 
Im' sorry I wrote that in french, steps to reproduce were :
1. Copy an image on firefox
2. Open openoffice
3. paste the image

But curioulsy, it's not that much reproducible : that is as soon as i closed openoffice, i did the same thing again with the same steps, and it worked... But from time to time, it makes the same bug.
Comment 4 Caolan McNamara 2010-09-27 10:24:38 UTC 
Yeah, that's the nature of threads and races. They're difficult to reproduce, but I'm fairly confident I know what the problem is and how to improve the chances of this not happening.
Comment 5 Caolan McNamara 2010-09-27 12:39:31 UTC 
added a workaround to protect the ne_dispatches and similar potentially troublesome calls that may call into libgcrypt with a mutex.

Will be available for testing eventually as >= 3.2.0-12.32
Comment 6 Fedora Update System 2010-10-12 19:17:12 UTC 
openoffice.org-3.2.0-12.32.fc13 has been submitted as an update for Fedora 13.
https://admin.fedoraproject.org/updates/openoffice.org-3.2.0-12.32.fc13
Comment 7 Fedora Update System 2010-10-14 06:27:06 UTC 
openoffice.org-3.2.0-12.32.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update openoffice.org'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/openoffice.org-3.2.0-12.32.fc13
Comment 8 Fedora Update System 2010-10-16 05:43:56 UTC 
openoffice.org-3.2.0-12.33.fc13 has been submitted as an update for Fedora 13.
https://admin.fedoraproject.org/updates/openoffice.org-3.2.0-12.33.fc13
Comment 9 Fedora Update System 2010-10-27 22:33:56 UTC 
openoffice.org-3.2.0-12.33.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.