Bug 626641

Summary: [abrt] gnumeric-1:1.10.0-2.fc13: excel_parse_name: Process /usr/bin/ssindex was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Donald Edward Winslow <dew>
Component: gnumericAssignee: Huzaifa S. Sidhpurwala <huzaifas>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: belegdol, huzaifas
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:e1df3bca2117c490d92f7b4e67f7b67d4f9b8250
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-24 09:09:41 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

Description Donald Edward Winslow 2010-08-24 01:02:51 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: ssindex -i /home/Donald/Documents/ecology/birds/California/data/cavitynesterdatafile.xls
component: gnumeric
crash_function: excel_parse_name
executable: /usr/bin/ssindex
kernel: 2.6.33.6-147.2.4.fc13.x86_64
package: gnumeric-1:1.10.0-2.fc13
rating: 4
reason: Process /usr/bin/ssindex was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1282611040
uid: 500

comment
-----
I was asked to retest this bug by the Gnumeric maintainer, so I reinstalled Beagle (which had apparently triggered it the first time.
Sure enough, after working for a while the ABRT notification came up. I think that the ssindex program crashed
when it encountered the same spreadsheet file that triggered the crash the first time.

How to reproduce
-----
1. I installed Beagle.
2. I rebooted and logged into Gnome.
3. I opened Gnumeric, and I browsed the web on Firefox for a while.
Comment 1 Donald Edward Winslow 2010-08-24 01:02:53 UTC 
Created an attachment (id=440537)
File: backtrace
Comment 2 Julian Sikorski 2010-08-24 09:09:41 UTC 

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