With Libreoffice 4.4.3.2, the python URE bridge is broken on windows 7 Using the provided python in Libreoffice, the following code fails: import uno import unohelper localContext = uno.getComponentContext() resolver = localContext.getServiceManager().createInstanceWithContext( "com.sun.star.bridge.UnoUrlResolver", localContext ) remote_ctx = resolver.resolve( "uno:pipe,name=hello;urp;StarOffice.ComponentContext" ) smgr = remote_ctx.getServiceManager() desktop = smgr.createInstanceWithContext( "com.sun.star.frame.Desktop",remote_ctx) print(dir(desktop)) Note that it does not make a difference if a pipe or a socket is used. soffice verified to be running the background Additionally, the following: uno.getConstantByName('com.sun.star.i18n.NumberFormatIndex.TEXT') Throws a runtime exception. This works on linux, unsure what the issue is without knowing a lot about the UNO bridge.
On Windows I ran C:\Program Files (x86)\LibreOffice 4\program\python.exe With remote_ctx = resolver.resolve( "uno:pipe,name=hello;urp;StarOffice.ComponentContext" ) I get Traceback (most recent call last): File "<stdin>", line 1, in <module> __main__.NoConnectException: Connector : couldn't connect to pipe hello(1) But this also happens on Linux. I am inputting the lines one by one, copying & pasting. Am I doing something wrong?
Hmm...I know there are issues with some of the versions on linux, but I think perhaps for different reasons. I've got it working there before... Let me get back to you on this.
(In reply to Beluga from comment #1) > On Windows I ran C:\Program Files (x86)\LibreOffice 4\program\python.exe > > With > > remote_ctx = resolver.resolve( > "uno:pipe,name=hello;urp;StarOffice.ComponentContext" ) > > I get > > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > __main__.NoConnectException: Connector : couldn't connect to pipe hello(1) > > But this also happens on Linux. > > I am inputting the lines one by one, copying & pasting. Am I doing something > wrong? This is probably not the place to be learning how you can do this, to get this working even on Linux you have to run some legwork to get the appropriate libraries loaded. The best I can do for you on Linux is attempt to configure it in a clean VM and link you to it, or if you can provide contact information I can work with you that way. The Bugzilla mailing list is not the place to be doing this.
@smaudet is this issue still reproducible using latest LibO 5.2.4.2? if bug persists revert status to UNCONFIRMED if bug is gone change it to RESOLVED WORSKSFORME in the meantime status -> NEEDINFO
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20170628
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20170727