Bug 603329

Summary: [abrt] crash in openoffice.org-ure-1:3.1.1-19.28.fc12: raise: Process /usr/lib/openoffice.org/ure/bin/uno.bin was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Philippe Leclercq <philec>
Component: openoffice.orgAssignee: Caolan McNamara <caolanm>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: caolanm
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:9c48c41cf5417ce658712a252ebc5e32bd260efb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-12 14:15:33 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 Philippe Leclercq 2010-06-12 12:35:36 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/openoffice.org/basis3.1/program/../ure-link/bin/uno.bin --quiet --singleaccept -u uno:pipe,name=3a92cffd2145685171c37096e0b557714d9991c9497592be2739a7c64dae66;urp;uno.ComponentContext -env:INIFILENAME= -env:JFW_PLUGIN_DO_NOT_CHECK_ACCESSIBILITY=1 -env:UserInstallation=file:///tmp/unoinstall.xZUsZR -env:INIFILENAME=vnd.sun.star.pathname:/usr/lib/openoffice.org3/program/redirectrc
component: openoffice.org
crash_function: raise
executable: /usr/lib/openoffice.org/ure/bin/uno.bin
global_uuid: 9c48c41cf5417ce658712a252ebc5e32bd260efb
kernel: 2.6.32.12-115.fc12.i686
package: openoffice.org-ure-1:3.1.1-19.28.fc12
rating: 4
reason: Process /usr/lib/openoffice.org/ure/bin/uno.bin was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
Update OpenOffice modules
Comment 1 Philippe Leclercq 2010-06-12 12:35:39 UTC 
Created attachment 423488 [details]
File: backtrace
Comment 2 Caolan McNamara 2010-06-12 14:15:33 UTC 
More than likely part of the nasty threading shutdown story

*** This bug has been marked as a duplicate of bug 599596 ***