Bug 653524

Summary: [abrt] openoffice.org-writer-1:3.3.0-13.3.fc14: rtl_cache_magazine_clear: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Деян <redhat>
Component: openoffice.orgAssignee: Caolan McNamara <caolanm>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: caolanm, dtardon
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:39b7cc2f13fd5002cabdb7a10215a6acdd20fe67
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-25 15:25:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Деян 2010-11-15 16:43:35 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/swriter.bin -writer file:///tmp/Conference%20Nov.%2010.doc
component: openoffice.org
crash_function: rtl_cache_magazine_clear
executable: /usr/lib64/openoffice.org3/program/swriter.bin
kernel: 2.6.35.6-48.fc14.x86_64
package: openoffice.org-writer-1:3.3.0-13.3.fc14
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1289832379
uid: 500

Comment 1 Деян 2010-11-15 16:43:37 UTC
Created attachment 460577 [details]
File: backtrace

Comment 2 Caolan McNamara 2010-11-15 16:51:08 UTC
Clearly a crash on exit.

Can you reproduce this, does it always crash, or only after opening e.g. a particular document ?

Comment 3 Деян 2010-11-15 17:10:41 UTC
Yes, I believe it was a crash on exit. My wife had a couple of documents open and when I closed OpenOffice it crashed.

I quickly tried to reproduce it by reopening those documents and closing them all but I could not.

Comment 4 Caolan McNamara 2010-11-25 15:25:44 UTC
A pity. Can't reproduce this.

Comment 5 David Tardon 2010-12-13 05:51:12 UTC

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