I've installed Openoffice 3.0beta several months ago, and it had troubles integrating with bibus 1.4.3. I have to switch back to openoffice 2.4.1 as a result.
Now, Ooo 3.0 release candidate 1 is out. The final release of 3.0 is very close - estimated on late September. Just wonder if the integration to openoffice 3.0 is fixed already or not? If not, when would it be?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For windows, if there is a problem it is just with the installer that may not detect the OOo installation path (I have to check). You can fix by editing the file bibus.cfg and setting the OOo path to the correct value. I however suspect that the problem is just due to the fact that OOo3 is installed in parallel with OOo2.4 and that will change with the official final release.
For linux, you have to wait for the distribution specific release. It is very difficult to make bibus working with the openoffice.org release because of python incompatibility.
Pierre
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This time, I can use the first connection wizard to open the activation page, and after that the Openoffice.org menu showed up successfully.
However, none of the functions in that menu work. Here's what happened when I tried to insert a reference:
Traceback (most recent call last):
File "..\BibFrame.py", line 1460, in onMenuOOoInsert
File "..\BibFrame.py", line 1449, in __connectToWriter
AttributeError: 'module' object has no attribute 'bibOOo_NoConnect'
Also, when I restart Bibus, the menu disappeared, and no connections showed up.
Then I tried to setup the connection using the "preference" menu, and then the Oo.org menu showed up again, and (as expected) none of the functions worked.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
they may have upgraded the python version. Could you please check (I'm using linux and the problem is Windows specific).
Go to:
C:\Program Files\OpenOffice.org 3\program
and look for python.bat
double-click:
you should get something like:
Python 2.5.2 (r252:60911, Jul 31 2008, 17:28:52)
[GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>
The first line gives you the version (here 2.5.2)
The "compiled" Windows bibus version is for python2.3 and cannot work with a more recent version.
In that case, you must use the "non-compiled" bibus version and use the same python version that the one included in OOo3.
Pierre
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I still did not try, but there is a bug report for the python-uno module for the last rc.
The communication between OOo3 and bibus cannot ork, until the bug is solved.
Pierre
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
however all of these are not related to programes such as Bibus that are used widely.
I would not be able to get the technical points right, so I think it would perhaps speed things up if you could write a comment into one of these bugs.
Cheers
Oliver
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Today I tried out the final 3.0 release of OpenOffice (Windows XP SP3) to see if the problem has been solved. I installed Bibus 1.4.3-3 (Full Windows Install) after installing the OpenOffice on a virgin system (no previous OOo nor Bibus installs).
Bottom line: the pyUNO problem has still not been solved.
On the first run of Bibus there was an error message ("cx_Freeze:Python Error in Main Script", screenshot available), but restarting Bibus a second time solved this, and I had an "OpenOffice.org" menu item in Bibus!
However, inserting a reference into the OpenOffice document generated invariably the aforementioned
'bibOOo_NoConnect' error.
Better stick to OpenOffice 2.4 for now...
Regards,
Martijn
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
please file a bug for this in the OO system. Even if this is not their fault, i think that they should be aware of it, especially as there seem to be also other problems with python and UNO :
I'm afraid we cannot solve the problem for Windows until upstream pyuno bug is fixed in OOo3.
Under linux (at least Ubuntu), you can use the pyuno bridge from 2.4 with the stock openoffice3. Don't do anything special, just install Ubuntu 2.4 with the python-uno pacjage, install stock OOo3 (I have just tested the last rc3) wihout desinstalling 2.4 (installation in /opt is fine) and everything should work.
Pierre
PS: I will try to experiment a bit with Windows but my home computer is still broken.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Everyone, please vote for the issue! You can vote once you have registered on the OOo website (just e-mail address and username and password required, so this is very fast) and logged in.
thanks Martijn for the effort.
I just tried the workaround suggested by jbu on the OO issues website, it does not seem to work.
Below the description of what I did that I submitted to the OO issue. I'd like to mention that I'm using the compiled version of bibus
---------
The workaround suggested by jbu does not seem to work :
I just installed OO3.0. I checked before installation : I do not have python23.dll in the windows system directory
Then after installation I moved phython23.dll from basis/program to program/
I was able to run the uno connection wizard supplied by Bibus, checking the connection using this wizard said that the uno connection is open using a pipe.
However when running bibus, there was no automaic detection of OO presence (no menu itme); I could get the menu item by manually changing the preferences.
however when trying to insert a reference I get the same 'bibOOo_NoConnect' error as everybody else.
So I guess something else is going on
Cheers
Oliver
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
it seems that your filing an issue has started things.
There is a page with workaround for python uno problems http://udk.openoffice.org/source/browse/udk/www/python/python-bridge.html?rev=1.39
number 1 and 3 don't seem to work, and for number 2 the bibus source code needs to be changed. I cannot do that, dos anybody volunteer ??
here is workaround number 2 as copied from above webpage :
--------snip
(windows only) When you try to connect to a running office process, you get
__main__.com.sun.star.connection.NoConnectException: Connector couldn't connect to socket (WSANOTINITIALISED, WSAStartup() has not been called)
You can workaround this, by placing a
import socket
in the top of your script (95028)
-----------snip end
if it would be only that it would be an easy solution
Cheers
Oliver
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm sorry but I can't really work on this bug for soem stupid reasons:
1) My computer at home is broken. I'm waiting for a new hard drive to re-install everything and start working
2) I have a computer with a VirutalBox with XP installed but I can't install OOo3 on it since I always get an error on OOo startup saying:
"The program cannot be started. Language could not be determined"
Google and OOo bug database did not help me. I tried OOo3 in english and French and also Novel OOo3 without any success!
3) Here what you should try:
a) Install the source bibus version
b) Edit the file bibus.cfg and change oopath to:
oopath = C:\Program Files\OpenOffice.org 3\URE\bin;C:\Program Files\OpenOffice.org 3\Basis\program;C:\Program Files\OpenOffice.org 3\program
If your OOo install is not in "C:\\Program Files\OpenOffice.org 3" you must of course adapt this value.
c) Edit bibusStart.py and add just before the last line:
os.environ["URE_BOOTSTRAP"]="file:///C:/Program%20Files/OpenOffice.org%203/program/fundamental.ini"
d) Activate the pyuno bridge in OOo3 by first setting the security to Medium level then opening the file bibus/Setup/UnoConnectionListener.odg
e) Restart OOo then try to connect.
f) If you still get the "com.sun.star.util.URL" error you can fix it by opening bibOOo/bibOOoBase.py then lines 38-39 remove
URL = uno.getClass("com.sun.star.util.URL")
and replace it with
from com.sun.star.util import URL
(you just have to uncomment line 38 and comment line 39)
Pierre
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I get the same error: "The program cannot be started. Language could not be determined" when I add the URE_BOOTSTRAP variable on windows vista 32. So maybe your OOo3 does not start because of this?
Hope that helps,
Mike
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
this is a very good news but you must first thank Joerg Budischewsk, the author of the python-uno bridge who posted the "URE_BOOTSRAP" fix that I would have never found by myself.
Could you please make a small page on the site to explain the procedure?
Is step f) needed or did c) fix f ?
The problem is that we need to compile a new bibus for Windows because I know that many users don't want to use the "source" version.
I will do that as soon as I get a working OOo ... and I don't have a clue. I think I will borrow a computer to make it.
Thanks,
Pierre
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Pierre,
I will make a page on site detailing the procedure. In my case, point f was not required.
I don't know how you create the windows installer but can I help you to compile a new version?
Cheers,
Hilaire
PS: I wrote on the bug report on openoffice.org site that the problem was solved. I will thank jbu for his help
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Pierre,
It doesn't work for me. I get:
Traceback (most recent call last):
File "C:\Program Files\bibus\bibus.py", line 191, in ?
bibframe1 = BibFrame.BibFrame(None, -1, BIB.TITLE, name=APPNAME)
File "C:\Program Files\bibus\BibFrame.py", line 34, in __init__
self.__loadConnectionModule()
File "C:\Program Files\bibus\BibFrame.py", line 1371, in __loadConnectionModule
import OOo
File "C:\Program Files\bibus\OOo.py", line 54, in ?
from bibOOo.bibOOoPlus import *
File "C:\Program Files\bibus\bibOOo\bibOOoPlus.py", line 22, in ?
from bibOOo.bibOOoBase import *
File "C:\Program Files\bibus\bibOOo\bibOOoBase.py", line 39, in ?
URL = uno.getClass("com.sun.star.util.URL")
File "C:\Program Files\OpenOffice.org 3\Basis\program\uno.py", line 74, in getClass
return pyuno.getClass(typeName)
uno.com.sun.star.uno.RuntimeException: pyuno.getClass: uno exception com.sun.star.util.URL is unknown
Cheers,
Hilaire
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No luck here (Vista 32).
I uninstalled the compiled version and installed the source exactly following your instructions.
Activating the UNO listener works fine, however when i try to insert a citation, I get the wxPython stdout/stderr window with:
Traceback (most recent call last):
And that's it. No error message.
It also seems that the source version does not save the word processor preference, as every time it starts there is no menu for OOo and I have to run the First Connection Wizzard to get it.
I'll try it tomorrow at work on WinXP and post here.
Best regards,
Mike
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've installed Openoffice 3.0beta several months ago, and it had troubles integrating with bibus 1.4.3. I have to switch back to openoffice 2.4.1 as a result.
Now, Ooo 3.0 release candidate 1 is out. The final release of 3.0 is very close - estimated on late September. Just wonder if the integration to openoffice 3.0 is fixed already or not? If not, when would it be?
This should work with OOo3.
What is your system ?
For windows, if there is a problem it is just with the installer that may not detect the OOo installation path (I have to check). You can fix by editing the file bibus.cfg and setting the OOo path to the correct value. I however suspect that the problem is just due to the fact that OOo3 is installed in parallel with OOo2.4 and that will change with the official final release.
For linux, you have to wait for the distribution specific release. It is very difficult to make bibus working with the openoffice.org release because of python incompatibility.
Pierre
I tried installing 3.0rc2 today.
This time, I can use the first connection wizard to open the activation page, and after that the Openoffice.org menu showed up successfully.
However, none of the functions in that menu work. Here's what happened when I tried to insert a reference:
Traceback (most recent call last):
File "..\BibFrame.py", line 1460, in onMenuOOoInsert
File "..\BibFrame.py", line 1449, in __connectToWriter
AttributeError: 'module' object has no attribute 'bibOOo_NoConnect'
Also, when I restart Bibus, the menu disappeared, and no connections showed up.
Then I tried to setup the connection using the "preference" menu, and then the Oo.org menu showed up again, and (as expected) none of the functions worked.
Hi,
they may have upgraded the python version. Could you please check (I'm using linux and the problem is Windows specific).
Go to:
C:\Program Files\OpenOffice.org 3\program
and look for python.bat
double-click:
you should get something like:
Python 2.5.2 (r252:60911, Jul 31 2008, 17:28:52)
[GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>
The first line gives you the version (here 2.5.2)
The "compiled" Windows bibus version is for python2.3 and cannot work with a more recent version.
In that case, you must use the "non-compiled" bibus version and use the same python version that the one included in OOo3.
Pierre
It shows:
Python 2.3.4 (#53, Jul 29 2008, 14:34:12) [ MSC v.1500 23 bit (Intel] on win32
I should say that I even tried to reinstall Bibus 1.4.3, but nothing improved.
The path in bibus.cfg is correct though:
[PATH]
oopath=C:\Program Files\OpenOffice.org 3\program
It shows:
Python 2.3.4 (#53, Jul 29 2008, 14:34:12) [MSC v.1500 32 bit (Intel)] on win32
I still did not try, but there is a bug report for the python-uno module for the last rc.
The communication between OOo3 and bibus cannot ork, until the bug is solved.
Pierre
Hello Pierre,
I think that it might perhaps be a good idea to file a bug for this also for OpenOffice.
I had a look and it seems to me (who really does not know a lot about UNO connections and Python :-) that there are already three bugs filed, some of them unconfirmed, that might have a similar reason.
http://qa.openoffice.org/issues/show_bug.cgi?id=93885
http://qa.openoffice.org/issues/show_bug.cgi?id=92661
http://qa.openoffice.org/issues/show_bug.cgi?id=93994
however all of these are not related to programes such as Bibus that are used widely.
I would not be able to get the technical points right, so I think it would perhaps speed things up if you could write a comment into one of these bugs.
Cheers
Oliver
Dear all,
Today I tried out the final 3.0 release of OpenOffice (Windows XP SP3) to see if the problem has been solved. I installed Bibus 1.4.3-3 (Full Windows Install) after installing the OpenOffice on a virgin system (no previous OOo nor Bibus installs).
Bottom line: the pyUNO problem has still not been solved.
On the first run of Bibus there was an error message ("cx_Freeze:Python Error in Main Script", screenshot available), but restarting Bibus a second time solved this, and I had an "OpenOffice.org" menu item in Bibus!
However, inserting a reference into the OpenOffice document generated invariably the aforementioned
'bibOOo_NoConnect' error.
Better stick to OpenOffice 2.4 for now...
Regards,
Martijn
Martijn,
please file a bug for this in the OO system. Even if this is not their fault, i think that they should be aware of it, especially as there seem to be also other problems with python and UNO :
http://qa.openoffice.org/issues/show_bug.cgi?id=93885
http://qa.openoffice.org/issues/show_bug.cgi?id=92661
http://qa.openoffice.org/issues/show_bug.cgi?id=93994
Oliver
I'm afraid we cannot solve the problem for Windows until upstream pyuno bug is fixed in OOo3.
Under linux (at least Ubuntu), you can use the pyuno bridge from 2.4 with the stock openoffice3. Don't do anything special, just install Ubuntu 2.4 with the python-uno pacjage, install stock OOo3 (I have just tested the last rc3) wihout desinstalling 2.4 (installation in /opt is fine) and everything should work.
Pierre
PS: I will try to experiment a bit with Windows but my home computer is still broken.
Hi all,
Same problem on Vista 32 bits, Bibus 1.4.3, OpenOffice 3.0. Please do fix this if possible.
Thank you for your great work!
Dear all,
I have filed a bug report in the OpenOffice issue tracker.
http://www.openoffice.org/issues/show_bug.cgi?id=94993
Pierre, I hope I described the problem correctly.
Everyone, please vote for the issue! You can vote once you have registered on the OOo website (just e-mail address and username and password required, so this is very fast) and logged in.
http://www.openoffice.org/servlets/Login?cookieCheck=on
Let's hope that the problem will be solved shortly.
Martijn
PS I have casted votes for the related issues suggested by Oliver Brendel.
Hello everybody,
thanks Martijn for the effort.
I just tried the workaround suggested by jbu on the OO issues website, it does not seem to work.
Below the description of what I did that I submitted to the OO issue. I'd like to mention that I'm using the compiled version of bibus
---------
The workaround suggested by jbu does not seem to work :
I just installed OO3.0. I checked before installation : I do not have python23.dll in the windows system directory
Then after installation I moved phython23.dll from basis/program to program/
I was able to run the uno connection wizard supplied by Bibus, checking the connection using this wizard said that the uno connection is open using a pipe.
However when running bibus, there was no automaic detection of OO presence (no menu itme); I could get the menu item by manually changing the preferences.
however when trying to insert a reference I get the same 'bibOOo_NoConnect' error as everybody else.
So I guess something else is going on
Cheers
Oliver
Hello Martijn,
it seems that your filing an issue has started things.
There is a page with workaround for python uno problems
http://udk.openoffice.org/source/browse/udk/www/python/python-bridge.html?rev=1.39
number 1 and 3 don't seem to work, and for number 2 the bibus source code needs to be changed. I cannot do that, dos anybody volunteer ??
here is workaround number 2 as copied from above webpage :
--------snip
(windows only) When you try to connect to a running office process, you get
__main__.com.sun.star.connection.NoConnectException: Connector couldn't connect to socket (WSANOTINITIALISED, WSAStartup() has not been called)
You can workaround this, by placing a
import socket
in the top of your script (95028)
-----------snip end
if it would be only that it would be an easy solution
Cheers
Oliver
I'm sorry but I can't really work on this bug for soem stupid reasons:
1) My computer at home is broken. I'm waiting for a new hard drive to re-install everything and start working
2) I have a computer with a VirutalBox with XP installed but I can't install OOo3 on it since I always get an error on OOo startup saying:
"The program cannot be started. Language could not be determined"
Google and OOo bug database did not help me. I tried OOo3 in english and French and also Novel OOo3 without any success!
3) Here what you should try:
a) Install the source bibus version
b) Edit the file bibus.cfg and change oopath to:
oopath = C:\Program Files\OpenOffice.org 3\URE\bin;C:\Program Files\OpenOffice.org 3\Basis\program;C:\Program Files\OpenOffice.org 3\program
If your OOo install is not in "C:\\Program Files\OpenOffice.org 3" you must of course adapt this value.
c) Edit bibusStart.py and add just before the last line:
os.environ["URE_BOOTSTRAP"]="file:///C:/Program%20Files/OpenOffice.org%203/program/fundamental.ini"
this comes from:
http://udk.openoffice.org/source/browse/udk/www/python/python-bridge.html?rev=1.39
You MUST use "%20" instead of space in your path. If your OOo install is not in "C:\\Program Files\OpenOffice.org 3" you must of course adapt this value.
d) Activate the pyuno bridge in OOo3 by first setting the security to Medium level then opening the file bibus/Setup/UnoConnectionListener.odg
e) Restart OOo then try to connect.
f) If you still get the "com.sun.star.util.URL" error you can fix it by opening bibOOo/bibOOoBase.py then lines 38-39 remove
URL = uno.getClass("com.sun.star.util.URL")
and replace it with
from com.sun.star.util import URL
(you just have to uncomment line 38 and comment line 39)
Pierre
Hi Pierre,
Your procedure works like a charm for me!
Thanks you very much!
Hilaire
Hi Pierre,
I get the same error: "The program cannot be started. Language could not be determined" when I add the URE_BOOTSTRAP variable on windows vista 32. So maybe your OOo3 does not start because of this?
Hope that helps,
Mike
Hi Hilaire,
this is a very good news but you must first thank Joerg Budischewsk, the author of the python-uno bridge who posted the "URE_BOOTSRAP" fix that I would have never found by myself.
Could you please make a small page on the site to explain the procedure?
Is step f) needed or did c) fix f ?
The problem is that we need to compile a new bibus for Windows because I know that many users don't want to use the "source" version.
I will do that as soon as I get a working OOo ... and I don't have a clue. I think I will borrow a computer to make it.
Thanks,
Pierre
Hi Pierre,
I will make a page on site detailing the procedure. In my case, point f was not required.
I don't know how you create the windows installer but can I help you to compile a new version?
Cheers,
Hilaire
PS: I wrote on the bug report on openoffice.org site that the problem was solved. I will thank jbu for his help
Hi again ...
I just realize that we may not have to modify bibus code if the "URL" bug is fixed by step c)
Make the modification (b). This can be done with the compiled version.
For (c), set an environment variable named URE_BOOTSRAP with the correct value. You can follow instructions at http://support.microsoft.com/default.aspx?scid=kb;en-us;310519
It should now work.
Pierre
Hi Pierre,
It doesn't work for me. I get:
Traceback (most recent call last):
File "C:\Program Files\bibus\bibus.py", line 191, in ?
bibframe1 = BibFrame.BibFrame(None, -1, BIB.TITLE, name=APPNAME)
File "C:\Program Files\bibus\BibFrame.py", line 34, in __init__
self.__loadConnectionModule()
File "C:\Program Files\bibus\BibFrame.py", line 1371, in __loadConnectionModule
import OOo
File "C:\Program Files\bibus\OOo.py", line 54, in ?
from bibOOo.bibOOoPlus import *
File "C:\Program Files\bibus\bibOOo\bibOOoPlus.py", line 22, in ?
from bibOOo.bibOOoBase import *
File "C:\Program Files\bibus\bibOOo\bibOOoBase.py", line 39, in ?
URL = uno.getClass("com.sun.star.util.URL")
File "C:\Program Files\OpenOffice.org 3\Basis\program\uno.py", line 74, in getClass
return pyuno.getClass(typeName)
uno.com.sun.star.uno.RuntimeException: pyuno.getClass: uno exception com.sun.star.util.URL is unknown
Cheers,
Hilaire
Hi Mike,
Thanks for the tips. I will have a look tomorrow.
Did the fix work for you also ?
Pierre
Pierre,
No luck here (Vista 32).
I uninstalled the compiled version and installed the source exactly following your instructions.
Activating the UNO listener works fine, however when i try to insert a citation, I get the wxPython stdout/stderr window with:
Traceback (most recent call last):
And that's it. No error message.
It also seems that the source version does not save the word processor preference, as every time it starts there is no menu for OOo and I have to run the First Connection Wizzard to get it.
I'll try it tomorrow at work on WinXP and post here.
Best regards,
Mike