Bug 702629 - [abrt] openoffice.org-brand-1:3.3.0-20.5.fc14: GtkSalFrame::createNewWindow: Process /usr/lib64/openoffice.org3/program/soffice.bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] openoffice.org-brand-1:3.3.0-20.5.fc14: GtkSalFrame::createNewWindow: ...
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:bffd7fc87e8bed1c2554ac9b4e9...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-06 12:22 UTC by Aleksey Popkov
Modified: 2011-05-23 15:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-23 10:22:41 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (77.70 KB, text/plain)
2011-05-06 12:22 UTC, Aleksey Popkov 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Aleksey Popkov 2011-05-06 12:22:54 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 79568 bytes
cmdline: /usr/lib64/openoffice.org3/program/soffice.bin -quickstart -nologo -nodefault
component: openoffice.org
Attached file: coredump, 134701056 bytes
crash_function: GtkSalFrame::createNewWindow
executable: /usr/lib64/openoffice.org3/program/soffice.bin
kernel: 2.6.35.12-90.fc14.x86_64
package: openoffice.org-brand-1:3.3.0-20.5.fc14
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/soffice.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1304682633
uid: 502

How to reproduce
-----
1.Send the file from archives.
2.
3.
Comment 1 Aleksey Popkov 2011-05-06 12:22:58 UTC 
Created attachment 497334 [details]
File: backtrace
Comment 2 David Tardon 2011-05-09 10:50:36 UTC 
What were you doing when it crashed? Is it reproducible?
Comment 3 Caolan McNamara 2011-05-23 15:11:30 UTC 
GtkSalFrame::SetPluginParent

might have been related to the firefox plugin or something of that nature
Note You need to log in before you can comment on or make changes to this bug.