Bug 142245 - After installing, libreglo.so can't be found
Summary: After installing, libreglo.so can't be found
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
7.1.3.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-12 20:19 UTC by Steve Kelem
Modified: 2021-05-13 05:17 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 Steve Kelem 2021-05-12 20:19:48 UTC
I downloaded LibreOffice_7.1.3_Linux_x86-64_deb_helppack_en-US.tar.gz and
LibreOffice_7.1.3_Linux_x86-64_deb.tar.gz, and installed with dpkg.
When I run swriter, I get the message:
/usr/lib/libreoffice/program/javaldx: error while loading shared libraries: libreglo.so: cannot open shared object file: No such file or directory
Warning: failed to read path from javaldx
/usr/lib/libreoffice/program/soffice.bin: error while loading shared libraries: libreglo.so: cannot open shared object file: No such file or directory
Comment 1 Julien Nabet 2021-05-12 21:04:27 UTC
tar.gz are more for maintainers of distributions.
Indeed, it's more a start to create a package and deal with dependencies.

I think you should remove it completely and install LO from the repository of your distribution.

BTW, on which distrib are you and with which version?
Comment 2 Steve Kelem 2021-05-12 22:14:51 UTC
I'm on Ubuntu 21.04, and LibreOffice notifies me that new versions are available, so I follow the links and download them from libreoffice.org.

I thought this is the mechanism for notifying the developers that there's a problem.
Comment 3 Aron Budea 2021-05-13 00:39:33 UTC
libreglo.so is in libreoffice7.1-ure_7.1.3.2-2_amd64.deb, which was in LibreOffice_7.1.3_Linux_x86-64_deb.tar.gz in my case.
Comment 4 Steve Kelem 2021-05-13 05:17:54 UTC
I fixed my symbolic links (/etc/alternatives never points to the new version if left to itself!), and it works now. The /usr/bin/swriter and /bin/swriter were pointing to the wrong version.