[Libreoffice-bugs] [Bug 134106] Binary URP bridge disposed during call to ServiceManager.createInstanceWithContext

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Fri Jun 26 09:33:10 UTC 2020


https://bugs.documentfoundation.org/show_bug.cgi?id=134106

--- Comment #4 from Konstantin Kharlamov <hi-angel at yandex.ru> ---
(In reply to Stephan Bergmann from comment #3)
> Yes, this only fails if the python side uses a sufficiently old LO
> installation (e.g., using python3-3.8.3-1.fc32.x86_64 and
> libreoffice-6.4.4.2-2.fc32.x86_64 on Fedora 32).
> 
> <https://git.libreoffice.org/core/+/
> f0a50d230756fc0a60780d992b807f9eb82106c2%5E!>
> "tdf#127205 split Desktop::terminate process" introduced a new
> css.frame.XDesktopInternal UNOIDL interface type (which an "old python side"
> thus does not know) and made the C++ implementation of the css.frame.Desktop
> UNOIDL service (framework::Desktop in framework/inc/services/desktop.hxx)
> implement it.
> 
> PyUNO uses the UNO introspection framework to translate between Python and
> UNO, and what presumably happens is that the python side, to translate the
> Python code
> 
>   desktop.CurrentComponent
> 
> in test.py (attachment 153473 [details]) into UNO, asks the soffice side for
> a sequence of all UNOIDL interface types supported by that desktop UNO
> object.  It thus gets back, among others, a UNO TYPE value for
> css.frame.XDesktopInternal, but which it does not know, so it disposes the
> bridge and throws an exception.
> 
> This would appear to be a general, by-design issue when connecting an "old
> python side" to a "new soffice side".

Thanks for explanation! Given pyuno is provided by libreoffice, this means
whenever users update their libreoffice instance, they won't have such problem.

So, this kinda "not a bug"… But I wonder if it would make sense to make PyUNO
print a warning whenever it detects that it connects to a different version of
LibreOffice? Because it is pretty common for QA to ask a user to test their bug
on a newer version of LibreOffice, and then if their bug is because of PyUNO,
they for sure would test with the system version of PyUNO. And then they gonna
get this or another similar problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20200626/fa0b3ee1/attachment.htm>


More information about the Libreoffice-bugs mailing list