Bugzilla Bug 140758

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.

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.

(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

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!

(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

And 1.4.3 is marked stable why?

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

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

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

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.

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

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

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

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?

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