After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 74705 - Gnumeric crashes
Gnumeric crashes
Status: VERIFIED INCOMPLETE
Product: Gnumeric
Classification: Applications
Component: Main System
1.0.x
Other other
: Urgent major
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2002-03-14 20:59 UTC by koresko
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description koresko 2002-03-14 21:00:07 UTC
Package: Gnumeric
Severity: normal
Version: 1.0.4 (Ximian binary)
Synopsis: Gnumeric crashes
Bugzilla-Product: Gnumeric
Bugzilla-Component: Main System

Description:
I just experienced three Gnumeric crashes in the space of 15 minutes. 
The crashes occurred while I was resizing and/or hiding columns in a
spreadsheet.  Gnumeric hung and had to be killed using a 'kill' command;
the first time, it held on to the focus and it was necessary to switch
to a textmode virtual console to do the kill.  GNOME continued normally
after Gnumeric was killed.

The Gnumeric crashes didn't cause the normal crash dialog box to launch.
 I am suspicious that they are caused by bugs or incompatibilities with
the latest Ximian GNOME libraries.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-03-14 16:00 -------

The original reporter (koresko@fitzgerald.jpl.nasa.gov) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, jody@gnome.org.

Comment 1 Jody Goldberg 2002-03-14 21:28:20 UTC
I would be very surprised if this was not an installtion issue.
Can you give me a specific set of steps to replicate this ?
Comment 2 Jody Goldberg 2002-03-21 01:57:57 UTC
This was one very strange bug.  There was a typo in the span code that has now
been fixed in 1.0 and 1.1.  I don't know why this worked on some machines when
run locally and not others.