Bug 1188 – unable to open module file error when starting gnumeric

This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes

Bug 1188 - unable to open module file error when starting gnumeric

Summary:	unable to open module file error when starting gnumeric

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	gnumeric (Show other bugs)
Sub Component:
Version:	6.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Michael Fulbright
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-02-15 21:34 EST by Chris Runge
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-03-13 21:51:39 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Chris Runge 1999-02-15 21:34:02 EST

RH 5.8 (beta 1)

When I start gnumeric I get this error:

unable to open module file:
/usr/lib/gnumeric/plugins/libpython.so: undefined symbole:
_Py_NoneStruct

Comment 1 Dale Lovelace 1999-02-23 15:04:59 EST

Upgrading to gnumeric--0.11-2 needs libguile.so.2 and the version of
guile we ship contains libguile.so.4 ???

Comment 2 Matt Wilson 1999-03-13 21:51:59 EST

Fixed in next cut.

Note You need to log in before you can comment on or make changes to this bug.