Bug 161300 - Can't run Draw (or Impress) with libsdlo error
Summary: Can't run Draw (or Impress) with libsdlo error
Status: RESOLVED DUPLICATE of bug 119408
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
7.5.9.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-28 02:38 UTC by N.P.
Modified: 2024-08-15 11:04 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description N.P. 2024-05-28 02:38:39 UTC
Same problem with 7.5.9.2.

When I start LibreOffice, and attempt to select a type for o new document, it works fine for all types of documents EXCEPT Impress and Draw. With Impress, absolutely nothing happens. With Draw, I get a popup with the following error message:

----------

Component can not be loaded, possibly broken or incomplete installation.

Full error message:

loading component library <file:///tmp/.mount_LibreOxxxxxx/opt/libreoffice24.2/program/../program/libsdlo.so> failed at /home/buildslave/source/libo-core/cppuhelper/source/shlib.cxx:312.

----------

I verified that the file does indeed exist in the AppImage:

$ find /tmp/.mount_LibreOxxxxxx/ -name '*sdlo*'
/tmp/.mount_LibreOxxxxxx/opt/libreoffice24.2/program/libsdlo.so

Any idea what could cause this? Thank you in advance.
Comment 1 Stéphane Guillou (stragu) 2024-05-28 04:51:25 UTC
What are your OS details? How did you install LO?

I thought it might be related to xmlsec (see bug 155034) but the fact that 7.5.9.2 has the same issue doesn't make sense.
Comment 2 N.P. 2024-05-28 05:35:36 UTC
> What are your OS details? How did you install LO?

I run Gentoo (completely up to date).

I downloaded the AppImage from:

https://appimages.libreitalia.org/

Searching for the error message does bring up instances where people running Linux (or FreeBSD) installed LibreOffice via their distribution package manager.

One of the Linux threads refers to bug 119408 (actually, that looks like EXACTLY the same bug - from six years ago).
Comment 3 QA Administrators 2024-05-29 03:15:02 UTC Comment hidden (obsolete)
Comment 4 Stéphane Guillou (stragu) 2024-05-29 04:41:37 UTC
Can you please try to install libavahi and see if it fixes it?
Comment 5 N.P. 2024-05-29 10:25:58 UTC
> Can you please try to install libavahi and see if it fixes it?

"Our security policy prohibits the installation of avahi."

I thought I could overcome this by compiling avahi, and just adding the directory containing the library to my $LD_LIBRARY_PATH, but after wasting hours trying to build avahi, I completely understand why people won't use it.

I will indulge myself a brief (off-topic) mini-rant describing my travails. 
I never intended to *install* avahi (that would require adding news users to the system, and installing several dependencies not present on the system - something I can't do). I thought I could at least get it to compile, though. The documentation seems hopelessly out of date (it mentions gtk+2, but doesn't mention a required dependency that I assume the developers added recently). The configure script represents a nightmare. If it didn't find something optional ("can't find Mono C# compiler"), it failed instead of continuing without that feature. I eventually got the configure script to complete by adding five --disable-feature options to it. The attempted compilation produced more warnings than I have ever seen before while compiling a piece of software. The build eventually aborted because the developers forgot to include a script in the tarball (the latest release occurred more than four years ago, and while they developers added that script to the tree last year, they have not released an updated tarball). After tracking down this issue, I downloaded that script and placed it in the proper directory of the source tree, but alas, the compile still failed, but for a different reason (cannot stat some file supposedly created during the build). At that point, I abandoned trying to compile avahi to create libavahi (and would describe the avahi soucre code as something that rhymes with "map"). Maybe it works adequately when compiled and installed, but I have no desire to engage with it further.

As a final comment, I will say (agreeing with some comments in bug 119408) that LibreOffice should not *require* any networking tools to function.
Comment 6 QA Administrators 2024-05-30 03:15:57 UTC Comment hidden (obsolete)
Comment 7 Buovjaga 2024-08-15 11:04:33 UTC

*** This bug has been marked as a duplicate of bug 119408 ***