Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [SOLVED] Libreoffice error: libboost_locale.so (no such file or directory) (Read 824 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

[SOLVED] Libreoffice error: libboost_locale.so (no such file or directory)

After the latest update, I got this message when I ran libreoffice.
Code: [Select]
$ libreoffice
/usr/lib/libreoffice/program/soffice.bin: error while loading shared libraries: libboost_locale.so.1.78.0: cannot open shared object file: No such file or directory
I'm using libreoffice-fresh.

Re: Libreoffice error: libboost_locale.so (no such file or directory)

Reply #1 –
I can confirm this
Create problems which don't have solution

Re: Libreoffice error: libboost_locale.so (no such file or directory)

Reply #2 –
Can also confirm
Edit: fixed with libreoffice-fresh-7.3.4-2

Re: Libreoffice error: libboost_locale.so (no such file or directory)

Reply #3 –
libreoffice-fresh 7.3.4-2 is available from extra repo.
Code: [Select]
world/libreoffice-fresh 7.3.4-1 [sudah terpasang]
    usr/bin/libreoffice
omniverse/libreoffice-still 7.2.7-1
    usr/bin/libreoffice
extra/libreoffice-fresh 7.3.4-2 [sudah terpasang: 7.3.4-1]
    usr/bin/libreoffice
extra/libreoffice-still 7.2.7-3
    usr/bin/libreoffice

Edit: It's now available from world repo and working properly.

Re: Libreoffice error: libboost_locale.so (no such file or directory)

Reply #4 –
Just a note to say that the error still exists with libreoffice-still, I have resolved it by uninstalling libreoffice-still and installing libreoffice-fresh.
 

Re: [SOLVED] Libreoffice error: libboost_locale.so (no such file or directory)

Reply #5 –
We don't carry libreoffice-still. It looks like arch should have updated that though?

Re: [SOLVED] Libreoffice error: libboost_locale.so (no such file or directory)

Reply #6 –
Quote from: Dudemanguy – on
We don't carry libreoffice-still. It looks like arch should have updated that though?

They may well have by now, I am not sure what the version was that I was experiencing the problem with, it was fully updated at the time though.

I will be sticking with 'fresh' from now on!  ;D