Bug 682966 - [abrt] openoffice.org-writer-1:3.3.0-20.2.fc14: SwViewImp::StartAction: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] openoffice.org-writer-1:3.3.0-20.2.fc14: SwViewImp::StartAction: Proce...
Keywords:
Status: CLOSED DUPLICATE of bug 669523
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:84d4e5302b0794a69aa47ed0faf...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-08 06:33 UTC by marc
Modified: 2011-03-29 14:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-29 14:20:54 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (207.61 KB, text/plain)
2011-03-08 06:33 UTC, marc
no flags Details

Description marc 2011-03-08 06:33:13 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 212597 bytes
cmdline: /usr/lib64/openoffice.org3/program/swriter.bin -writer file:///tmp/34984392021EOIB1601%2020110302.doc
component: openoffice.org
Attached file: coredump, 129093632 bytes
crash_function: SwViewImp::StartAction
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-20.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: 1299519265
uid: 500

How to reproduce
-----
1.opening

2.
3.

Comment 1 marc 2011-03-08 06:33:19 UTC
Created attachment 482842 [details]
File: backtrace

Comment 2 David Tardon 2011-03-08 08:14:38 UTC
It crashed when you cancelled a print job. Did you do anything special, like printing a selection, comments etc.?

Note to myself: could be duplicate of bug 657783.

Comment 3 Caolan McNamara 2011-03-29 14:20:54 UTC

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


Note You need to log in before you can comment on or make changes to this bug.