Bug 657934 - [abrt] openoffice.org-brand-1:3.3.0-15.2.fc14: Window::SetType: Process /usr/lib64/openoffice.org3/program/soffice.bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] openoffice.org-brand-1:3.3.0-15.2.fc14: Window::SetType: Process /usr/...
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:01380cbe5b792dcf949e05229f0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-28 19:18 UTC by Rob Wills
Modified: 2010-11-28 21:31 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-28 21:31:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (42.12 KB, text/plain)
2010-11-28 19:18 UTC, Rob Wills
no flags Details

Description Rob Wills 2010-11-28 19:18:48 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/soffice.bin -quickstart -nologo -nodefault
comment: This is a rather benign excell spreadsheet in question. No special formatting, no macros, etc. Not sure why this would cause Calc to crash.
component: openoffice.org
crash_function: Window::SetType
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-15.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: 1290971720
uid: 500

How to reproduce
-----
1. Opened a .xls file
2. OO.o crashed.
3.

Comment 1 Rob Wills 2010-11-28 19:18:50 UTC
Created attachment 463366 [details]
File: backtrace

Comment 2 Caolan McNamara 2010-11-28 21:31:07 UTC
I bet it works if you try again.

*** 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.