Follow steps from bug 126582, copied below slightly modified: 1. Run LO Impress as `soffice --impress --accept="socket,host=localhost,port=2002;urp;StarOffice.ServiceManager"` 2. Dismiss a "Template" window, so you're left with a new presentation of a single slide 3. Run the attached python script, attachment 153018 [details] (it creates 2 new slides and puts a text on them) => Error when connecting to LO: ... File "test.py", line 16, in connectToLO return (desktop.CurrentComponent, smgr) __main__.RuntimeException: Binary URP bridge disposed during call Observed in LO 7.2.0.0.alpha1+ (e96554b67b17f9d3d91b0bb1f29ab0b9cdc43dcb) / Ubuntu. No issue in 7.1.0.3. This is a regression from the following commit. Adding CC: to Noel Grandin. https://cgit.freedesktop.org/libreoffice/core/commit/?id=857caa5fc69b92e781457a1b67a89aa051c2d70f author Noel Grandin <noel@peralex.com> 2021-04-30 13:00:35 +0200 committer Noel Grandin <noel.grandin@collabora.co.uk> 2021-04-30 16:03:35 +0200 tdf#79049 speed up OOXML workbook load
How do I set up my environment so the script can run? (Currently it can't find the uno import)
Not sure, I didn't have to do anything special in Ubuntu 20.04, and I haven't even built it with internal Python. By the way, I can see the following in the console of the soffice process when running the script: warn:sal.osl:3110642:3110738:sal/osl/unx/socket.cxx:1570: receive socket [0] failed: EOL warn:binaryurp:3110642:3110738:binaryurp/source/reader.cxx:123: caught UNO exception 'N3com3sun4star3uno9ExceptionE msg: acc_socket.cxx:SocketConnection::read: error - Success /home/valaki/projects/libreoffice/io/source/acceptor/acc_socket.cxx:175' warn:binaryurp:3110642:3110738:binaryurp/source/bridge.cxx:840: undisposed bridge "" in state 2, potential deadlock ahead
Eh, I don't have a OS-installed LibreOffice, only a development build, so probably some PATH/etc stuff needs to be configured, but no idea what
Are you sure about this bisect? If I revert my commit, then run your test (a) in gtk mode, I get a solid deadlock because of different threads taking different mutexes in different orders (b) in gen mode, I get the same exception as without reverting my commit
(In reply to Noel Grandin from comment #4) > Are you sure about this bisect? I have now built LO at 857caa5fc69b92e781457a1b67a89aa051c2d70f, and got an error with the steps. I have also built LO at 857caa5fc69b92e781457a1b67a89aa051c2d70f~1, and the steps succeeded.
After installing python3-uno on Ubuntu 20.04, steps work for me with: Version: 7.1.0.3 / LibreOffice Community Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded But I get the RuntimeException with 7.2: Version: 7.2.7.2 / LibreOffice Community Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded I can confirm Aron's bisect with the linux-64-7.2 repo, the issue starts at commit a056f689c5e1137af73589f207f9fe27648ac4fc which points to core commit 857caa5fc69b92e781457a1b67a89aa051c2d70f Noel, could you have another look?
(same result for gen VCL by the way)
Hi For install uno execute command: sudo apt-get install libreoffice-script-provider-python Sergey
Dear Aron Budea, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug