Created attachment 46511 [details] Patch to correct pyuno bug I am using ArchLinux (x86_64) and I am having issues with pyuno. I cannot make it work properly. Here's how to reproduce: $export PYTHONPATH=/usr/lib/libreoffice/basis-link/program $export LD_LIBRARY_PATH=/usr/lib/libreoffice/basis-link/program:/usr/lib/libreoffice/basis-link/ure-link/lib $export URE_BOOTSTRAP=file:///usr/lib/libreoffice/program/fundamentalrc $python >>> import uno >>> from com.sun.star.util import URL (1st error) >>> uno.getClass("com.sun.star.util.URL") (error again) The affected file is /usr/lib/libreoffice/basis3.3/program/uno.py (in the installed package). I have made a patch that corrects the problem and seems to make everything fine (in attachment). The patch applies to the mentioned file, but I cannot seem to find it in the source files. I'm sorry I cannot be more precise about it. I have reported this bug on the Arch bugtracker and I was recommended to report it here too. https://bugs.archlinux.org/task/23733?opened=5011&type[0]=&sev[0]=&due[0]=&cat[0]=&status[0]=open&percent[0]=&reported[0]= I hope this will help improve libreoffice.
can you try with beta4 btw I don't see any of those lines ( os.environ ) in uno.py in libreoffice 3.4-beta4 following the instructions about and I don't get any errors
I have found where the offending line is added: In the source file: libreoffice-build-3.3.2.2.tar.gz (I cannot find this file for the latest beta in http://download.documentfoundation.org/libreoffice/src/), under: 'libreoffice-build-3.3.2.2/patches/dev300/pyuno-ooodir.diff' This patch will introduce the line that causes issues. Do you think it is something that should be fixed in the source, or just something that Arch has to deal with? It seems like during the build of libreoffice, the ${exec_prefix} variable doesn't get translated into "/usr" for some reason. I should also mention that during the package building, Arch passes the following to ./configure: --prefix=/usr --exec-prefix=/usr --sysconfdir=/etc \
Seems like this can be closed. It's fixed in 3.4.0.
Since nobody did it, I took the liberty of closing the bug myself. It's been fixed in 3.4.0 and didn't regress in 3.4.1.
RESOLVED, FIXED or CLOSED bugs cant be KEYWORD NEEDINFO.
Sorry about that. I'm still new to this sort of thing.