Bug 681530

Summary: [abrt] openoffice.org-writer-1:3.3.0-20.2.fc14: SvStream::Write: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Simon <simon>
Component: openoffice.orgAssignee: Caolan McNamara <caolanm>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: caolanm, dtardon, michelenani
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:3f1884c10fe3bb07db1a679a429e0eae1b98027b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-17 22:24:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Simon 2011-03-02 13:50:20 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 79004 bytes
cmdline: /usr/lib/openoffice.org3/program/swriter.bin -writer file:///tmp/3301580DOCIssue%2068.doc
comment: this is the first time this has happened, openoffice has never crashed on me before and I have saved numerous files in word format
component: openoffice.org
Attached file: coredump, 259383296 bytes
crash_function: SvStream::Write
executable: /usr/lib/openoffice.org3/program/swriter.bin
kernel: 2.6.35.11-83.fc14.i686.PAE
package: openoffice.org-writer-1:3.3.0-20.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: 1299072120
uid: 500

How to reproduce
-----
1. Downloaded newsletter in word format
2. Saving dialogue box asked if I wanted to save in word format
3. Chose yes -crash
Comment 1 Simon 2011-03-02 13:50:23 UTC 
Created attachment 481869 [details]
File: backtrace
Comment 2 David Tardon 2011-03-02 16:33:31 UTC 
Could you attach the file here?
Comment 3 Simon 2011-03-02 16:53:30 UTC 
I can't I'm afraid, it's copyright, and I'm pretty certain the problem was caused when I didn't log out after a software update because I've been doing the same thing with a lot of similar files after logging out and back in, with no problems.

Sorry if I've wasted your time, but I always report crashes so the experts can deal with them.
Thanks for responding, but I've got no problem now.

best wishes
Comment 4 Caolan McNamara 2011-03-17 20:16:15 UTC 
*** Bug 688104 has been marked as a duplicate of this bug. ***
Comment 5 Caolan McNamara 2011-04-17 22:24:24 UTC 
if anyone can supply a document which triggers this, feel free to reopen this bug with the extra info