Bug 669712 - [abrt] openoffice.org-writer-1:3.2.0-12.33.fc13: GetIndex: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] openoffice.org-writer-1:3.2.0-12.33.fc13: GetIndex: Process /usr/lib64...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 13
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c42db4d7801413df3b5a2b89c7f...
: 665170 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-14 14:01 UTC by Markus Schulze
Modified: 2011-01-15 17:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-15 17:24:20 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (30.19 KB, text/plain)
2011-01-14 14:01 UTC, Markus Schulze 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Markus Schulze 2011-01-14 14:01:35 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/swriter.bin -writer file:///home/schulze/Desktop/Anforderungen_neue_Proxy_Gruppen.doc
component: openoffice.org
crash_function: GetIndex
executable: /usr/lib64/openoffice.org3/program/swriter.bin
kernel: 2.6.34.7-66.fc13.x86_64
package: openoffice.org-writer-1:3.2.0-12.33.fc13
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1295012854
uid: 500

How to reproduce
-----
1. Edited a MS Word Document 
2. Changed the top bordersize with the slider
3. Oo crashed
Comment 1 Markus Schulze 2011-01-14 14:01:38 UTC 
Created attachment 473525 [details]
File: backtrace
Comment 2 David Tardon 2011-01-14 14:20:17 UTC 
Could you attach the document here?
Comment 3 David Tardon 2011-01-14 14:23:40 UTC 
*** Bug 665170 has been marked as a duplicate of this bug. ***
Comment 4 Markus Schulze 2011-01-15 13:55:52 UTC 
Unfortunately it was a company document for internal use only. I'm not allowed to give someone access to it.

Sorry...
Comment 5 Caolan McNamara 2011-01-15 17:24:20 UTC 
Hopefully someone else can provide an example of this if another instance of this appears.
Note You need to log in before you can comment on or make changes to this bug.