Bug 140758 – gnumeric-1.4.3-r3 is broken - undefined symbol: gsf_xml_in_parse

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description John Green 2006-07-17 03:39:33 UTC]

Gnumeric cannot open a .xls file.  The file was itself saved by an earlier version of gnumeric.  Here are the console error messages.

E Unable to open module file "/usr/lib/gnumeric/1.4.3/plugins/excel/excel".
  E /usr/lib/gnumeric/1.4.3/plugins/excel/excel.so: undefined symbol: gsf_xml_in_parse

It used to work.

[Comment 1 John N. Laliberte (RETIRED) 2006-07-17 08:38:25 UTC]

does this still happen if you upgrade to gnumeric-1.6 ?

I will probably request 1.6 to be stable if this is the case.

It looks like its just missing a link in the makefile to the libgsf libs, but its probably time to move 1.6 to stable.

[Comment 2 Allan Gottlieb 2006-07-17 09:33:07 UTC]

(In reply to comment #1)
> does this still happen if you upgrade to gnumeric-1.6 ?

No that fixes it.  You also need to stablize goffice

# for gnumeric
~app-office/gnumeric-1.6.3
~x11-libs/goffice-0.2.1

thanks,
allan

[Comment 3 Rick Jenkins 2006-07-19 11:32:21 UTC]

My gnumeric 1.4.3 broke completely after this weeks emerge -Dua world. It would not open .xls, or even .gnumeric files. An open .gnumeric file was zeroed when I tried to save it.

Updating to 1.6 by adding the lines from comment #2 to my /etc/portage/package.keywords fixed the problem. Pity my zeroed file didn't come back!

[Comment 4 John Green 2006-07-19 15:26:02 UTC]

(In reply to comment #1)
> does this still happen if you upgrade to gnumeric-1.6 ?
> 
> I will probably request 1.6 to be stable if this is the case.
> 
> It looks like its just missing a link in the makefile to the libgsf libs, but
> its probably time to move 1.6 to stable.

The upgrade fixed it for me (the original poster).

As comment #2 doesn't say, the three lines must be added to /etc/portage/package.keywords.

Many thanks.

John Green

[Comment 5 Robert Forsman 2006-07-24 13:33:09 UTC]

And 1.4.3 is marked stable why?

[Comment 6 Josh Sled 2006-07-25 09:31:29 UTC]

Yeah, this is pretty crazy.  Glad I have backups. :/  Can someone mark gnumeric-1.4.3-r3 *unstable*?

[Comment 7 Mr. Bones. (RETIRED) 2006-07-25 09:52:25 UTC]

*** Bug 141341 has been marked as a duplicate of this bug. ***

[Comment 8 Michael Wilcox 2006-07-30 14:04:29 UTC]

This workaround worked for me:
LDFLAGS="/usr/lib/libgsf-1.so.1" emerge gnumeric

[Comment 9 Todd 2006-08-03 16:43:29 UTC]

Can gnumeric-1.4.3-r3 please be marked unstable?  I've just lost a lot of very important data on account of this bug.

I think this could be avoided pretty easily.

[Comment 10 Jakub Moc (RETIRED) 2006-08-06 11:27:18 UTC]

*** Bug 143001 has been marked as a duplicate of this bug. ***

[Comment 11 Jakub Moc (RETIRED) 2006-08-06 11:30:41 UTC]

Ping; please, stabilize something that's not broken, thanks.

[Comment 12 Jakub Moc (RETIRED) 2006-08-08 14:07:11 UTC]

*** Bug 143254 has been marked as a duplicate of this bug. ***

[Comment 13 Owen Berry 2006-08-14 17:08:35 UTC]

Apparently we're not the only ones having problems with 1.4.3:

http://mail-index.netbsd.org/pkgsrc-bugs/2005/12/12/0000.html

Hmmm ... time to upgrade?

[Comment 14 Aron Griffis (RETIRED) 2006-10-14 18:43:01 UTC]

Since 1.6.3 has the same keyword list as 1.4.3-r3, I just removed the older version, so this bug should be fini