Bug 665600 - [abrt] openoffice.org-writer-1:3.3.0-17.2.fc14: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] openoffice.org-writer-1:3.3.0-17.2.fc14: Process /usr/lib64/openoffice...
Keywords:
Status: CLOSED DUPLICATE of bug 649310
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:ba8a95a55a9e7ef1d8109200584...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-25 10:58 UTC by Georg Greve
Modified: 2010-12-25 12:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-25 12:33:45 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (206.33 KB, text/plain)
2010-12-25 10:58 UTC, Georg Greve 		no flags Details
View All

Description Georg Greve 2010-12-25 10:58:40 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/swriter.bin -writer '/tmp/kde-greve/Manes Weihnachtskuchen.odt_[qC3132].odt'
comment: Start OpenOffice on Fedora 14 x64. Never got it to start even once.
component: openoffice.org
crash_function: dp_registry::backend::bundle::(anonymous namespace)::BackendImpl::PackageImpl::getBundle
executable: /usr/lib64/openoffice.org3/program/swriter.bin
kernel: 2.6.35.9-64.fc14.x86_64
package: openoffice.org-writer-1:3.3.0-17.2.fc14
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1293196882
uid: 1000

How to reproduce
-----
1. Start OpenOffice.
2. Wait for crash.
3. Works every time.
Comment 1 Georg Greve 2010-12-25 10:58:52 UTC 
Created attachment 470666 [details]
File: backtrace
Comment 2 David Tardon 2010-12-25 12:33:45 UTC 

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