To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=94993
User jbu changed the following:
What |Old value |New value
================================================================================
Assigned to|jbu |chemwords
--------------------------------------------------------------------------------
Status|STARTED |NEW
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Mon Oct 20 20:58:07 +0000
2008 -------
Hi,
sorry for the confusion around python23.dll, this actually solves a problem but
not the bibus one.
The bibus stuff is very hard to debug (it is binary compiled python code).
The actual error message points to a problem not related to pyuno directly. It
actually says, that OOo has no bibOOo_NoConnect element, which acutally can
only occur, when the module OOo somehow exists, but all the
bibOOoBase.py/bibOOoPlus.py has not been imported. To, this looks like some
other initialization error.
I currently doubt, that the office connection code has ever been reached. In
order to give more support here, I actually need the exception, that comes from
the bibOOoBase.__init__ code.
Can you provide such a stacktrace ?
When I look into the bibus installation directory, I find a pyuno.dll and a
python23.dll. Where are these dlls from ? Do they get used ?
Bye,
Joerg
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
