Description: Using the official LibreOffice-6.0.6 32-bit Linux builds from www.libreoffice.org, Draw fails to start with this message: Error: Component cannot be loaded, possibly broken or incomplete installation. Full error message: loading component library <file:///opt/libreoffice6.0/program/../program/libsdlo.so> failed. Impress also fails to start, but with no error message. This occurs on distributions such as Slackware Linux, which do not include Avahi. Steps to Reproduce: 1. libreoffice6.0 --draw 2. libreoffice6.0 --impress Actual Results: Draw fails to start, and exits with error message. Impress fails to start, and just hangs forever with no window and no message. Expected Results: Draw starts. Impress starts. Reproducible: Always User Profile Reset: No Additional Info: The cause is a newly introduced dependency of the Linux builds on Avahi (libavahi). The change to LibreOfficeLinux.conf was made 2018-05-19 and does not seem to be linked to a specific bug report nor documented in the release notes. Here are 3 suggested ways to address this, from most desirable to least: 1. Change Draw and Impress to automatically detect availability of Avahi at runtime. If the library cannot be loaded, disable the remote-control feature in Impress, which seems to be the only use for Avahi. Draw does not seem to need Avahi for any function. or, 2. Revert the change and distribute Linux binaries that do not require Avahi and do not have the remote control Impress feature. Note that lack of support in Linux builds is documented in https://wiki.documentfoundation.org/Documentation/HowTo/Impress_Remote_%28iOS%29 or, 3. Document Avahi as a required external dependency of the distributed Linux builds. Users of Linux distributions without Avahi will have to use builds from elsewhere.
A new major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
CONFIRMED still a bug in 6.1.4 Status changed back to UNCONFIRMED as requested.
*** Bug 121846 has been marked as a duplicate of this bug. ***
Confirmed with duplicate bug
Solved installing Avahi
Dear lj308, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Confirmed bug still exists. Draw will not start (with non-helpful error message) if Avahi is not present, even though Draw does not use Avahi. Impress will not start (with no message at all) if Avahi is not present. Avahi is apparently only used for remote control of Impress. Avahi should be conditionally loaded, only if needed. From Help > About: Version: 6.4.7.2 Build ID: 639b8ac485750d5696d7590a72ef1b496725cfb5 CPU threads: 2; OS: Linux 5.10; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
Bug still exists in 7.3.5.2 (184fe81b8c8c30d8b5082578aee2fed2ea847c01), see also bug 150559 Impress will not start, Generates error -- Component cannot be loaded, possibly broken or incomplete installation. -- Full error message: -- -- loading component library -- <file:///opt/libreoffice7.3/program/../program/libsdlo.so> failed -- /home/buildslave/source/libo-core-cppuhelper/source/shlib.css:311
*** Bug 150559 has been marked as a duplicate of this bug. ***
I just did a system upgrade and now I can reproduce this as well. What's interesting is that Avahi is actually running for me, and is properly linked into libsdlo as far as I can tell. Can reproduce on both 7.4.0 and 7.3.5 in Archlinux. The Flatpak works fine, somehow. I've talked to some people on #archlinux:libera.chat and they can't reproduce this issue, which is really weird.... I've tried a new user, safe mode, reinstalling, etc.
Cross-reference: FreeBSD bug 266262 – editors/libreoffice: 7.4.0.3 fails to start Draw, Impress <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266262> See also: bug 139825
Confirmed bug on PopOS 22.04 LibreOffice 7.4.0.3 don't start. terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x41eb3)[0x7fde348ddeb3] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x42074)[0x7fde348de074] /lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x7fde2f642520] /lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x12c)[0x7fde2f696a7c] /lib/x86_64-linux-gnu/libc.so.6(raise+0x16)[0x7fde2f642476] /lib/x86_64-linux-gnu/libc.so.6(abort+0xd3)[0x7fde2f6287f3] /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa2bfe)[0x7fde2caa2bfe] /lib/x86_64-linux-gnu/libstdc++.so.6(+0xae28c)[0x7fde2caae28c] /lib/x86_64-linux-gnu/libstdc++.so.6(+0xae2f7)[0x7fde2caae2f7] /lib/x86_64-linux-gnu/libstdc++.so.6(+0xae558)[0x7fde2caae558] /usr/lib/libreoffice/program/libmergedlo.so(+0xe6686b)[0x7fde3086686b] /usr/lib/libreoffice/program/libmergedlo.so(+0x14d074d)[0x7fde30ed074d] /usr/lib/libreoffice/program/libmergedlo.so(+0x14f2080)[0x7fde30ef2080] /usr/lib/libreoffice/program/libmergedlo.so(+0x302933d)[0x7fde32a2933d] /usr/lib/libreoffice/program/libmergedlo.so(+0x302992a)[0x7fde32a2992a] /usr/lib/libreoffice/program/libmergedlo.so(_ZN3utl10ConfigItemC2ERKN3rtl8OUStringE14ConfigItemMode+0x82)[0x7fde32a225e2] /usr/lib/libreoffice/program/libmergedlo.so(+0x3063f3e)[0x7fde32a63f3e] /usr/lib/libreoffice/program/libmergedlo.so(_ZN19SvtSysLocaleOptionsC1Ev+0x12d)[0x7fde32a64dcd] /usr/lib/libreoffice/program/libmergedlo.so(+0x35131f6)[0x7fde32f131f6] /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0xf499b)[0x7fde28cf499b] /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0xf5eb5)[0x7fde28cf5eb5] /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x10832b)[0x7fde28d0832b] /usr/lib/libreoffice/program/libmergedlo.so(_Z7InitVCLv+0x502)[0x7fde32f21172] /usr/lib/libreoffice/program/libmergedlo.so(_Z10ImplSVMainv+0xf5)[0x7fde32f226a5] /usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0xa3)[0x7fde31da7cc3] /usr/lib/libreoffice/program/soffice.bin(+0x10b0)[0x55888fc700b0] /lib/x86_64-linux-gnu/libc.so.6(+0x29d90)[0x7fde2f629d90] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80)[0x7fde2f629e40] /usr/lib/libreoffice/program/soffice.bin(+0x10e5)[0x55888fc700e5]
Cloph, seeing c488328fd27a883e730d1eda47c4a4d2c07f3585, any comment on this? Or any idea what could have started it before it being explicitly enabled?
*** Bug 161300 has been marked as a duplicate of this bug. ***