Bug 674165 - [abrt] openoffice.org-writer-1:3.3.0-19.2.fc14: SfxShell::SetDisableFlags: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] openoffice.org-writer-1:3.3.0-19.2.fc14: SfxShell::SetDisableFlags: Pr...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:48419a063e2cd848ce139584990...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-31 20:17 UTC by Marco
Modified: 2011-02-15 13:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-15 13:50:09 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (48.33 KB, text/plain)
2011-01-31 20:17 UTC, Marco 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Marco 2011-01-31 20:17:55 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/openoffice.org3/program/swriter.bin -writer '/home/marco/share/Amadeus/LCC/stima iniziale.odt'
component: openoffice.org
crash_function: SfxShell::SetDisableFlags
executable: /usr/lib/openoffice.org3/program/swriter.bin
kernel: 2.6.35.10-74.fc14.i686.PAE
package: openoffice.org-writer-1:3.3.0-19.2.fc14
rating: 4
reason: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1296504084
uid: 500

How to reproduce
-----
1. open a document
2. change a bulleting formatting
3. close the document
Comment 1 Marco 2011-01-31 20:17:59 UTC 
Created attachment 476264 [details]
File: backtrace
Comment 2 David Tardon 2011-02-04 08:53:20 UTC 
Can you reproduce the crash with the same document? If yes, could you attach it here?
Comment 3 Marco 2011-02-15 13:33:38 UTC 
The crash happen only once.
In any case it was a business document and I can't share it with you.
I'm sorry.
Note You need to log in before you can comment on or make changes to this bug.