GNOME Bugzilla – Bug 35239
MS Works 4 file format
Last modified: 2011-05-04 19:15:12 UTC
Package: gnumeric Severity: normal Version: 0.58 Synopsis: crashes on opening MS Works 4 (wks) file Class: sw-bug System: Linux 2.2.16-22 i686 unknown C library: glibc-2.1.92-14 C compiler: 2.96 glib: 1.2.8 GTK+: 1.2.8 ORBit: ORBit 0.5.5 gnome-libs: gnome-libs 1.2.8 libxml: 1.8.10 gnome-print: gnome-print-0.25-8_helix_1 gnome-core: gnome-core 1.2.4 Description: Opened Gnumeric, selected "open" from File menu, browsed to wks file, pressed open. Gnumeric crashed. Debugging information: (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x4070b5a9 in __wait4 () from /lib/libc.so.6
+ Trace 136
------- Additional Comments From jgoldberg@home.com 2000-12-15 09:07:41 ---- Subject: Re: Bug#35239: crashes on opening MS Works 4 (wks) file From: Jody Goldberg <jgoldberg@home.com> To: 35239@bugs.gnome.org Cc: Eric Sproul <theman@ericsproul.to> Message-Id: <20001215090741.B21281@parallel.tymbri.org> Date: Fri, 15 Dec 2000 09:07:41 -0500 On Fri, Dec 15, 2000 at 12:40:44AM -0500, Eric Sproul wrote: > Package: gnumeric > Severity: normal > Version: 0.58 > Synopsis: crashes on opening MS Works 4 (wks) file > Class: sw-bug > > Description: > Opened Gnumeric, selected "open" from File menu, browsed to wks file, > pressed open. Gnumeric crashed. > > #4 0x80aa4c0 in rendered_value_new () > #5 0x806fb69 in cell_render_value () > #6 0x806ef44 in cell_eval_content () > #7 0x807b462 in cell_eval () > #8 0x807aa81 in dependent_eval () > #9 0x807bf41 in workbook_recalc () Interesting. Would it be possible to get a copy of the problem file ? It can be kept confidential if required. Thanks ------- Additional Comments From terra@diku.dk 2000-12-15 11:01:24 ---- Subject: http://bugs.gnome.org/db/35/35239.html From: Morten Welinder <terra@diku.dk> To: 35239@bugs.gnome.org Cc: theman@ericsproul.to Message-Id: <20001215160124.4541.qmail@tyr.diku.dk> Date: 15 Dec 2000 16:01:24 -0000 Thanks for your bug report. May we have a copy of the sheet in question so we can track this down? It can be kept confidential if needed. Morten ------- Bug moved to this database by debbugs-export@bugzilla.gnome.org 2001-01-27 12:33 ------- This bug was previously known as bug 35239 at http://bugs.gnome.org/ http://bugs.gnome.org/show_bug.cgi?id=35239 Originally filed under the Gnumeric product and general component. The original reporter (theman@ericsproul.to) of this bug does not have an account here. Reassigning to the exporter, debbugs-export@bugzilla.gnome.org. Reassigning to the default owner of the component, jgoldberg@home.com.
It was determined that the file in question was an MS Works file and Gnumeric treated it as a Lotus 123 file. The Lotus detection was made smarter.
The last line in this bug, from Morten, sounds as though the issue which caused the bug to be created no longer exists. If I misunderstood and Gnumeric still crashes on this file then leave the bug open. Otherwise, please change the bug status to FIXED or another resolution as appropriate.
Things no longer crash, but we leave it open as a placeholder to remind us of the difference.
Hello, Some news about this bug ?
*** Bug 557911 has been marked as a duplicate of this bug. ***
I am marking this as a duplicate of bug #647492 since that one has a patch attached. *** This bug has been marked as a duplicate of bug 647492 ***