Bug 669855 - gnash module won't load in python
Summary: gnash module won't load in python
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: python-goopy
Version: 13
Hardware: i686
OS: Linux
low
high
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-15 03:58 UTC by Bob Nolty
Modified: 2011-01-15 04:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-15 04:00:11 UTC
Type: ---


Attachments (Terms of Use)

Description Bob Nolty 2011-01-15 03:58:34 UTC
Description of problem:

[nolty@BobVirtF13 ~]$ python
Python 2.6.4 (r264:75706, Jun  4 2010, 18:20:16) 
[GCC 4.4.4 20100503 (Red Hat 4.4.4-2)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import gnash
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: /usr/lib/python2.6/site-packages/gtk-2.0/gnash.so: undefined symbol: _ZN5gnash19create_Renderer_aggEPKc
>>> 

This looks like a packaging inconsistency.  In the gnash RPM, symbol _ZN5gnash19create_Renderer_aggEPKc lives in /usr/lib/gnash/libgnashrender.so.  In the python-gnash RPM, the gnash python module is in 
/usr/lib/python2.6/site-packages/gtk-2.0/gnash.so.  That .so references the create_Renderer_agg symbol mentioned above, but does not mention the libgnashrender library (it does mention four gnash libraries, libgnashcore, -base, -sound and -media).



Version-Release number of selected component (if applicable):

gnash-0.8.8-4.fc13.i686
python-gnash-0.8.8-4.fc13.i686


How reproducible:

Every time.


Steps to Reproduce:
1. Start python
2. type 'import gnash'
3.
  
Actual results:

ImportError with traceback, shown above

Expected results:

module loads


Additional info:

Comment 1 Bob Nolty 2011-01-15 04:00:11 UTC
Sorry, this got submitted with the wrong component.  I am closing and will refile.


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