Bug 672759 - [abrt] openoffice.org-brand-1:3.3.0-19.2.fc14: __libc_message: Process /usr/lib64/openoffice.org3/program/soffice.bin was killed by signal 6 (SIGABRT)
Summary: [abrt] openoffice.org-brand-1:3.3.0-19.2.fc14: __libc_message: Process /usr/l...
Keywords:
Status: CLOSED DUPLICATE of bug 613530
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c2541f79f6bee6fa54314752dc0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-26 09:31 UTC by Dimar van Rietchoten
Modified: 2011-01-26 09:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-26 09:42:29 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (72.68 KB, text/plain)
2011-01-26 09:31 UTC, Dimar van Rietchoten 		no flags Details
View All

Description Dimar van Rietchoten 2011-01-26 09:31:02 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/soffice.bin -quickstart -nologo -nodefault
component: openoffice.org
crash_function: __libc_message
executable: /usr/lib64/openoffice.org3/program/soffice.bin
kernel: 2.6.35.10-74.fc14.x86_64
package: openoffice.org-brand-1:3.3.0-19.2.fc14
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/soffice.bin was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1296032976
uid: 500

How to reproduce
-----
1. Open existing openoffice document
2. Save as, choose CIFS filesystem (mounted 'on the spot', entered root password for mount)
3. Choose office 2003 XML format
4. Press save
5. Openoffice crashed
Comment 1 Dimar van Rietchoten 2011-01-26 09:31:04 UTC 
Created attachment 475354 [details]
File: backtrace
Comment 2 David Tardon 2011-01-26 09:42:29 UTC 

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