Bug 695984 - [abrt] AttributeProperties::ImpRemoveStyleSheet (undo destruction) signal 11 (SIGSEGV)
Summary: [abrt] AttributeProperties::ImpRemoveStyleSheet (undo destruction) signal 11 ...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5d8102ceff40bfe87de65cd9318...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-13 02:02 UTC by Ray
Modified: 2015-11-13 01:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-17 21:44:39 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (60.40 KB, text/plain)
2011-04-13 02:02 UTC, Ray 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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
Note You need to log in before you can comment on or make changes to this bug.