[SOLVED] libreoffice fails to start on a -current clean install
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
libreoffice fails to start on a -current clean install
Today I did a clean install of -current on one of my main office machines using https://slackware.nl/slackware/slack...nstall-dvd.iso (2020/12/8). Everything went well but now my libreoffice 7.0.3 (from AlienBob) won't start. It fails with a non-informative
Code:
bash-5.1$ libreoffice
Application Error
bash-5.1$
This is a multilib installation. I've checked the linked libraries used by loffice.bin but everything seems to be OK.
Error:
$ libreoffice
/usr/lib64/libreoffice/program/soffice.bin: error while loading shared libraries: libicui18n.so.67: cannot open shared object file: No such file or directory
This is caused by icu4c-68.1-x86_64-1.txz (libreoffice 7.0.3 was built with icu4c-67)
Again, I do have the package icu4c-compat-68.1-x86_64-1alien installed. This is automatically done by a script that installs all AlienBob's stuff (multilib, libreoffice, jdk, chrome, etc). So, apparently, that is not the issue with my installation. What bothers me is that libreoffice fails without any reasonable excuse, even when I start is from the command line! Running as root also doesn't help.
Again, I do have the package icu4c-compat-68.1-x86_64-1alien installed. This is automatically done by a script that installs all AlienBob's stuff (multilib, libreoffice, jdk, chrome, etc). So, apparently, that is not the issue with my installation. What bothers me is that libreoffice fails without any reasonable excuse, even when I start is from the command line! Running as root also doesn't help.
The issue is not with icu4c, at least not this week. As you can read in other topic here and on my blog (I urge you to subscribe to my blog if you use my packages and scripts!), the issue is the removal of raptor2, rasqal and redland which causes libreoffice to stop working.
Report it in the bug tracker of the Document Foundation then, if you want to get meaningful messages on standard output on why the program fails to launch.
In the meantime I recompiled LO 7.0.3 using GCC10 on an up-to-date Slackware-current. The new compiler needed a bit of adjustment in the SlackBuild.
The 64bit LO programs work properly, now compiling the 32bit packages.
Eric: Just an update for you. Installing your icu4c-compat package allowed your 7.0.3 LibreOffice to launch for me, but it could not save .odt packages. Read, yes, save, no. Re-installing raptor2, rasqal and redland solved that for me.
The issue is not with icu4c, at least not this week. As you can read in other topic here and on my blog (I urge you to subscribe to my blog if you use my packages and scripts!), the issue is the removal of raptor2, rasqal and redland which causes libreoffice to stop working.
Report it in the bug tracker of the Document Foundation then, if you want to get meaningful messages on standard output on why the program fails to launch.
In the meantime I recompiled LO 7.0.3 using GCC10 on an up-to-date Slackware-current. The new compiler needed a bit of adjustment in the SlackBuild.
The 64bit LO programs work properly, now compiling the 32bit packages.
First, this is a good opportunity to thank you for your great work on slackware! I don't subscribe your blog but I visit it regularly, especially if anything breaks in multilib, java, libreoffice, wine and the like. Yesterday, even before my original post, I noticed the problem with the missing packages and installed them, unfortunately without any better results! Libreoffice still exits with the message "Application Error" and nothing more. Today I guessed that eventually I was missing a "reboot" (a la windows) but it didn't change the results :-(
Maybe this afternoon I learn how to activate libreoffice's logging to have a better understanding of what's happening. On all computers I have (and they are many) libreoffice is working correctly. They all are in the same stage as this one. The difference is that on all machines I reached the state of -current from 2020/12/8 through upgradepkg and in this particular one I did a full install from the DVD into an SSD!
I uploaded my recompiled libreoffice packages if you want to give those a try.
Thanks for the effort! Unfortunately the result is similar: "Application Error". I don't use libreoffice that much. But this is the worst time of the year for having it failing! On average, I have one thesis defense per day and the faculty post-graduation office sends me all relevant documents in .docx! Fortunately calligra is up to the job and can read and convert the documents to PDF!
Thanks for the effort! Unfortunately the result is similar: "Application Error". I don't use libreoffice that much. But this is the worst time of the year for having it failing! On average, I have one thesis defense per day and the faculty post-graduation office sends me all relevant documents in .docx! Fortunately calligra is up to the job and can read and convert the documents to PDF!
It runs without issue on my desktop, I can open DOCX files, open and save ODT and I can open and edit PDF files without errors.
Are you missing some package perhaps that got added to slackware-current recently?
But this is the worst time of the year for having it failing! On average, I have one thesis defense per day and the faculty post-graduation office sends me all relevant documents in .docx! Fortunately calligra is up to the job and can read and convert the documents to PDF!
Alienbob's LibreOffice is not your only option, if you really need it working as soon as possible you could also install from SBo (both binary and source options available).
That said, the new libreoffice packages from Alienbob's repo fixed all the startup/saving problems here (including saving .docx).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
