Bug 666205

Summary: [abrt] openoffice.org-calc-1:3.3.0-18.2.fc14: rtl_uString_assign: Process /usr/lib/openoffice.org3/program/scalc.bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: thanosk <thanosk>
Component: openoffice.orgAssignee: Caolan McNamara <caolanm>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: caolanm, dtardon
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:6e2d8736c084f9d1cd6815af4cdc85e74e10c828
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-29 16:36:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
Another backtrace from the same crash
none
The xls file that causes the crashes none

Description thanosk 2010-12-29 15:02:01 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/openoffice.org3/program/scalc.bin -calc file:///tmp/statdeltio2009_9Hb-1.xls
component: openoffice.org
crash_function: rtl_uString_assign
executable: /usr/lib/openoffice.org3/program/scalc.bin
kernel: 2.6.35.10-74.fc14.i686.PAE
package: openoffice.org-calc-1:3.3.0-18.2.fc14
rating: 4
reason: Process /usr/lib/openoffice.org3/program/scalc.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1293629062
uid: 500

How to reproduce
-----
1. I was attempting to open an xls file from owl.ly
2.
3.
Comment 1 thanosk 2010-12-29 15:02:09 UTC 
Created attachment 471066 [details]
File: backtrace
Comment 2 thanosk 2010-12-29 15:11:21 UTC 
Created attachment 471067 [details]
Another backtrace from the same crash
Comment 3 thanosk 2010-12-29 15:12:57 UTC 
Created attachment 471068 [details]
The xls file that causes the crashes
Comment 4 David Tardon 2010-12-29 16:36:19 UTC 

*** This bug has been marked as a duplicate of bug 657807 ***