Ubuntu
gnumeric package

gnumeric crashed with signal 7 in gsf_infile_msole_new()

Bug #325902 reported by Alexander Jones on 2009-02-05

10

Affects		Status	Importance	Assigned to	Milestone
	gnumeric (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

Binary package hint: gnumeric

Opening a file on a FAT32 USB drive where the FAT32 filesystem was a bit broken.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gnumeric
NonfreeKernelModules: nvidia
Package: gnumeric 1.8.3-6ubuntu2
ProcCmdline: gnumeric /media/disk/lab.xls
ProcEnviron:
LANG=en_GB.UTF-8
SHELL=/bin/bash
Signal: 7
SourcePackage: gnumeric
StacktraceTop:
?? () from /usr/lib/libgsf-1.so.114
gsf_infile_msole_new ()
excel_file_probe ()
?? () from /usr/lib/libgoffice-0.6.so.6
wb_view_new_from_input ()
Title: gnumeric crashed with signal 7 in gsf_infile_msole_new()
Uname: Linux 2.6.28-6-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse kvm libvirtd lpadmin plugdev pulse-rt sambashare video

See original description

Tags:

Revision history for this message

Alexander Jones (alex-weej) wrote on 2009-02-05:

#1

Dependencies.txt Edit (4.3 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (626 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (46.2 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (798 bytes, text/plain; charset="utf-8")
Registers.txt Edit (1.0 KiB, text/plain; charset="utf-8")
Stacktrace.txt Edit (529 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (556 bytes, text/plain; charset="utf-8")

description:

updated

Revision history for this message

Apport retracing service (apport) wrote on 2009-02-05: Symbolic stack trace

#2

Stacktrace.txt (retraced) Edit (2.0 KiB, text/plain)

StacktraceTop:gsf_infile_msole_new (source=0x127dac0, err=0x0)
excel_file_probe (fo=<value optimized out>,
go_plugin_file_opener_probe (fo=0x13f7300,
wb_view_new_from_input (input=0x127dac0,
wb_view_new_from_uri (

Revision history for this message

Apport retracing service (apport) wrote on 2009-02-05: Symbolic threaded stack trace

#3

ThreadStacktrace.txt (retraced) Edit (2.1 KiB, text/plain)

Changed in gnumeric:
importance:	Undecided → Medium

Revision history for this message

Connor Imes (ckimes) wrote on 2009-02-06:

#4

The upstream gnome bugzilla dup-finder found a match at http://bugzilla.gnome.org/show_bug.cgi?id=570285
I have asked the upstream triager to determine if the root cause is the same. Thanks for filing this.

Revision history for this message

Charlie Kravetz (cjkgeek) wrote on 2010-02-28:

#5

Upstream can not determine if the bugs are the same without the file used when the crash occurred. Is it possible to attach the file? Please do not attach a file with private data in it.

Changed in gnumeric (Ubuntu):
status:	New → Incomplete

Revision history for this message

Charlie Kravetz (cjkgeek) wrote on 2010-03-26:

#6

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message

Charlie Kravetz (cjkgeek) wrote on 2010-05-10:

#7

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in gnumeric (Ubuntu):
status:	Incomplete → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

gnome-bugs #570285
[RESOLVED OBSOLETE] Edit

Bug watches keep track of this bug in other bug trackers.