Bug 971573

Summary: [abrt] gnumeric-1.12.2-1.fc18: odf_text_content_end: Process /usr/bin/gnumeric-1.12.2 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Stefan Gies <stefan998>
Component: gnumericAssignee: Huzaifa S. Sidhpurwala <huzaifas>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: aguelzow, belegdol, huzaifas, stefan998
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:a587014b7aac23cf72cf58fd03d0b79c84aa29d5
Fixed In Version: goffice-0.10.4-1.fc18 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-16 22:57:26 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
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
My file which killed gnumeric none

Description Stefan Gies 2013-06-06 20:23:57 UTC 
Description of problem:
Try to import .ods-file

Version-Release number of selected component:
gnumeric-1.12.2-1.fc18

Additional info:
reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        gnumeric
crash_function: odf_text_content_end
executable:     /usr/bin/gnumeric-1.12.2
kernel:         3.9.4-200.fc18.x86_64
runlevel:       N 5
uid:            1000
var_log_messages: Jun  6 22:20:17 athlon64x4-631 abrt[2090]: Saved core dump of pid 2070 (/usr/bin/gnumeric-1.12.2) to /var/tmp/abrt/ccpp-2013-06-06-22:20:17-2070 (88690688 bytes)
xsession_errors: 

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 odf_text_content_end at openoffice-read.c:1643
 #1 oo_cell_content_end at openoffice-read.c:4061
 #2 gsf_xml_in_end_element at gsf-libxml.c:840
 #4 xmlParseEndTag1 at parser.c:8679
 #5 xmlParseElement__internal_alias at parser.c:10082
 #6 xmlParseContent__internal_alias at parser.c:9881
 #7 xmlParseElement__internal_alias at parser.c:10054
 #8 xmlParseContent__internal_alias at parser.c:9881
 #9 xmlParseElement__internal_alias at parser.c:10054
 #10 xmlParseContent__internal_alias at parser.c:9881
Comment 1 Stefan Gies 2013-06-06 20:24:01 UTC 
Created attachment 757885 [details]
File: backtrace
Comment 2 Stefan Gies 2013-06-06 20:24:05 UTC 
Created attachment 757886 [details]
File: cgroup
Comment 3 Stefan Gies 2013-06-06 20:24:23 UTC 
Created attachment 757887 [details]
File: core_backtrace
Comment 4 Stefan Gies 2013-06-06 20:24:27 UTC 
Created attachment 757888 [details]
File: dso_list
Comment 5 Stefan Gies 2013-06-06 20:24:30 UTC 
Created attachment 757889 [details]
File: environ
Comment 6 Stefan Gies 2013-06-06 20:24:34 UTC 
Created attachment 757890 [details]
File: limits
Comment 7 Stefan Gies 2013-06-06 20:24:40 UTC 
Created attachment 757891 [details]
File: maps
Comment 8 Stefan Gies 2013-06-06 20:24:43 UTC 
Created attachment 757892 [details]
File: open_fds
Comment 9 Stefan Gies 2013-06-06 20:24:46 UTC 
Created attachment 757893 [details]
File: proc_pid_status
Comment 10 Andreas J Guelzow 2013-06-06 21:24:24 UTC 
Hi, would you be able to provide the ODF file in question?
Comment 11 Stefan Gies 2013-06-07 09:41:01 UTC 
I opened an ODS-File. It is an older format of Openoffice not ODF. An ODF-File do not cause an error.
Comment 12 Andreas J Guelzow 2013-06-07 17:04:03 UTC 
Files with extension .ods are typically files in the spreadsheet variant of the OpenDocument Format (ODF). 
But I am wondering whether you can provide the specific file leading to this crash. If it is confidential, would you be able to send it to me? I am one of the upstream deveopers for Gnumeric, and can make sure that it stays confidential.
Comment 13 Stefan Gies 2013-06-07 18:56:58 UTC 
Created attachment 758298 [details]
My file which killed gnumeric

@ Andreas J Guelzow : The file you requested
Comment 14 Andreas J Guelzow 2013-06-07 19:19:40 UTC 
Thank you for providing the file. I seem to be unable to trigger the crash with that file. I have, upstream, ensured that we will not crash again at that spot but I was trying to figure out how we could  have attained a null pointer in that situation.
Comment 15 Stefan Gies 2013-06-07 20:12:33 UTC 
Today I opened the file again and nothing happened. the file was opened as it should be. Everything was fine. No crash. I am astonished.
Comment 16 Andreas J Guelzow 2013-06-28 20:18:25 UTC 
This trace matches a bug I just fixed upstream (the fix will be in 1.12.4) that could be triggered by old sxc files (Those are pre-cursors to the open document format spreadsheet files). One should consider this bug fixed in 1.12.4.
Comment 17 Fedora Update System 2013-07-18 19:01:35 UTC 
goffice-0.10.4-1.fc18, gnumeric-1.12.4-1.fc18, gnome-chemistry-utils-0.14.2-4.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/goffice-0.10.4-1.fc18,gnumeric-1.12.4-1.fc18,gnome-chemistry-utils-0.14.2-4.fc18
Comment 18 Fedora Update System 2013-07-20 09:35:57 UTC 
Package goffice-0.10.4-1.fc18, gnumeric-1.12.4-1.fc18, gnome-chemistry-utils-0.14.2-4.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing goffice-0.10.4-1.fc18 gnumeric-1.12.4-1.fc18 gnome-chemistry-utils-0.14.2-4.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-13242/goffice-0.10.4-1.fc18,gnumeric-1.12.4-1.fc18,gnome-chemistry-utils-0.14.2-4.fc18
then log in and leave karma (feedback).
Comment 19 Fedora Update System 2013-08-16 22:57:26 UTC 
goffice-0.10.4-1.fc18, gnumeric-1.12.4-1.fc18, gnome-chemistry-utils-0.14.2-4.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.