Bug 695984

Summary: [abrt] AttributeProperties::ImpRemoveStyleSheet (undo destruction) signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Ray <rtai>
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, nobody
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5d8102ceff40bfe87de65cd9318926ed198f16c8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-17 21:44:39 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 Ray 2011-04-13 02:02:46 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 61848 bytes
cmdline: /usr/lib64/openoffice.org3/program/soffice.bin -quickstart -nologo -nodefault
component: openoffice.org
Attached file: coredump, 250900480 bytes
executable: /usr/lib64/openoffice.org3/program/soffice.bin
kernel: 2.6.35.12-88.fc14.x86_64
package: openoffice.org-brand-1:3.3.0-20.2.fc14
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/soffice.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1302613139
uid: 500

How to reproduce
-----
1.double click on open office and tried to retrieve a missing / hang document and the program crashed.
2.
3.
Comment 1 Ray 2011-04-13 02:02:55 UTC 
Created attachment 491621 [details]
File: backtrace
Comment 2 Caolan McNamara 2011-04-13 08:02:13 UTC 
Looks like a crash on deleting the undo stack. Its possible that there shouldn't have been any undo information in the first place.

Is this reproducible ?, I imagine its not
Comment 3 Caolan McNamara 2011-04-17 21:44:39 UTC 
Can't fix this one unless I can get a document or route to reproduce it unfortunately :-(

If anyone can reproduce this feel free to reopen with the required information