Bug 667978 - [abrt] openoffice.org-brand-1:3.3.0-18.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-18.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
low
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:68d52672469623f667d8b37adc6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-07 15:01 UTC by Alex
Modified: 2011-01-07 15:28 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-01-07 15:28:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (76.77 KB, text/plain)
2011-01-07 15:03 UTC, Alex
no flags Details

Description Alex 2011-01-07 15:01:30 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/soffice.bin -quickstart -nologo -nodefault
comment: see above
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-18.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: 1294386575
uid: 500

How to reproduce
-----
1. working with Writer
2. I wanted to save the file (for the first time) on another hard disk (different from the one where Fedora and OOo are installed and working)
3. the system automatically asked for root password (which I duly inserted) when I chose that disk
4. saving it there
5 crashing

Comment 1 Alex 2011-01-07 15:03:23 UTC
Created attachment 472243 [details]
File: backtrace

Comment 2 David Tardon 2011-01-07 15:28:04 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.