Bug 672161

Summary: [abrt] openoffice.org-writer-1:3.3.0-19.2.fc14: cp_gtk_gdk_env: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Jens Hansen <jhansen>
Component: openoffice.orgAssignee: Caolan McNamara <caolanm>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: caolanm
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:110b8a0485444569ba9fcc557fb5bea0af8f5ba6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-24 12:07:29 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 Jens Hansen 2011-01-24 09:28:07 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/swriter.bin -writer file:///home/jens/.cache/evolution/tmp/evolution-jens-upbvg2/Programm%20RT%202011%20Waldenserkirche.doc
component: openoffice.org
crash_function: cp_gtk_gdk_env
executable: /usr/lib64/openoffice.org3/program/swriter.bin
kernel: 2.6.35.10-74.fc14.x86_64
package: openoffice.org-writer-1:3.3.0-19.2.fc14
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1295855438
uid: 500

How to reproduce
-----
1. ho lavorato con il database mysql, connessione diretta
2. per problemi di report ho cambiato java scegliendo sun-java
3. ho chiuso openoffice per riavviarlo con il nuovo java, durante la chiusura si รจ verivicato il crash
Comment 1 Jens Hansen 2011-01-24 09:28:11 UTC 
Created attachment 474923 [details]
File: backtrace
Comment 2 Caolan McNamara 2011-01-24 12:07:29 UTC 

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