Bug 651636 - [abrt] openoffice.org-brand-1:3.3.0-13.3.fc14: Window::IsSystemWindow: Process /usr/lib64/openoffice.org3/program/soffice.bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] openoffice.org-brand-1:3.3.0-13.3.fc14: Window::IsSystemWindow: Proces...
Keywords:
Status: CLOSED DUPLICATE of bug 610103
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ea59a6d3822dc3391834eaa959b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-09 23:36 UTC by Philip Schroeder
Modified: 2010-11-10 05:49 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-10 05:49:17 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (29.99 KB, text/plain)
2010-11-09 23:36 UTC, Philip Schroeder 		no flags Details
View All

Description Philip Schroeder 2010-11-09 23:36:31 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/soffice.bin -quickstart -nologo -nodefault
comment: It should work to lauch the appropriate Office application from an email attachment.
component: openoffice.org
crash_function: Window::IsSystemWindow
executable: /usr/lib64/openoffice.org3/program/soffice.bin
kernel: 2.6.35.6-48.fc14.x86_64
package: openoffice.org-brand-1:3.3.0-13.3.fc14
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/soffice.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1289342227
uid: 500

How to reproduce
-----
1.Was launching Open Office Calc 3.3 from an attachment in an email message
2.Received warning that Open Office had crashed
3.
Comment 1 Philip Schroeder 2010-11-09 23:36:34 UTC 
Created attachment 459287 [details]
File: backtrace
Comment 2 David Tardon 2010-11-10 05:49:17 UTC 

*** This bug has been marked as a duplicate of bug 610103 ***
Note You need to log in before you can comment on or make changes to this bug.