python-uno can't be imported

[Rob Wilco]

Binary package hint: python-uno

~$ python -c "import uno"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python2.5/site-packages/uno.py", line 37, in <module>
    import pyuno
SystemError: dynamic module not initialized properly

~$ python -V
Python 2.5.1

~$ dpkg -l | grep python-uno
ii python-uno 2.3.0~src680m224-1ubuntu2

TEST CASE:

If you can run `python -c "import uno"` then the bug is corrected

[Douglas Sculley (dsculley)]

I can confirm this error for Gutsy

~$ python -c "import uno"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python2.5/site-packages/uno.py", line 37, in <module>
    import pyuno
SystemError: dynamic module not initialized properly
~$ python -V
Python 2.5.1
~$ dpkg -l | grep python-uno
ii python-uno 1:2.3.0-1ubuntu2 Python interface for OpenOffice.org

[pmartino (p-martineau)]

I just installed Gutsy and I confirm this bug or at least this change.
The problem is that before Gutsy, the path to the Openoffice library was set in the pyuno.so and it is no more the case.
I don't know if it is a change in the policy in debian or a bug.
To use python-uno in Gutsy you must first set the LD_LIBRARY_PATH

> export LD_LIBRARY_PATH="/usr/lib/openoffice/program"
> python
>>> import uno

[pmartino (p-martineau)]

It seems to be a ldconfig problem.
As said in bug 139077

> ldconfig /usr/lib/openoffice/program

solve the bug

[Vincenzo Ciancia (vincenzo-ml)]

My impression is that the fix is just to put the two lines below in /etc/ld.so.conf.d/python-uno.conf

#python-uno configuration
/usr/lib/openoffice/program

and launch ldconfig after installing the package.

If so, could the fix be committed as soon as possible?

[Martin Pitt (pitti)]

Accepted into gutsy-proposed, please test:

openoffice.org (1:2.3.0-1ubuntu5.2) gutsy-proposed; urgency=low

  * debian/rules: Rename intro.bmp to openintro_ubuntu.bmp.
    Closes LP: #155125
  * debian/rules move libdba680lx.so from openoffice.org-base to
    openoffice.org-core.
    Closes LP: #24975, #52847, #117648, #134276, #156852, #157512
  * ooo-build/patches/src680/pyuno-rpath-ooodir.diff:
    Closes LP: #132583
  * ooo-build/patches/src680/ooo82608.vcl.gtkbadfree.diff:
    Closes LP: #131526
  * ubuntu/openintro_ubuntu.bmp:
    Update splash screen to right bitmap depth. Closes LP: #157176

 -- Chris Cheney <email address hidden> Sat, 24 Nov 2007 20:07:29 -0600

[Pedro Villavicencio (pedro)]

Verification done:

Test with openoffice.org 1:2.3.0-1ubuntu5 the python -c "import uno" fails.
Tested with openoffice.org 1:2.3.0-1ubuntu5.3 the python -c "import uno" works fine.

thanks,

[Martin Pitt (pitti)]

Copied to gutsy-updates.

[Martin Pitt (pitti)]

Chris, please ensure that his gets fixed ASAP in hardy, too. Or is it already fixed in the current source? Then it just needs to build on amd64 eventually.

Bumping priority since this is a fixed SRU which is not yet fixed in Hardy, and thus violating SRU policy.

[Kit (svartalfar13)]

Confirming this error on latest Hardy:

/$ python -c "import uno"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python2.5/site-packages/uno.py", line 37, in <module>
    import pyuno
SystemError: dynamic module not initialized properly
/$ python -V
Python 2.5.2a0
/$ dpkg -l | grep python-uno
ii python-uno 1:2.3.0-1ubuntu5 Python interface for OpenOffice.org

[Pedro Villavicencio (pedro)]

This is fixed for me with python-uno 1:2.3.1-3ubuntu2, can someone else confirm?

[Steve Langasek (vorlon)]

confirmed, this module imports fine; marking as "fix released" in hardy.