[SOLVED] SBo build of Libreoffice-6.2 fails, apparently due to incomplete source archive
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.
SBo build of Libreoffice-6.2 fails, apparently due to incomplete source archive
The Slackbuild for Libreoffice uses the rpm package as source. This package appears to be incomplete. The last few lines of output are:
Code:
./opt/libreoffice6.2/share/calc/styles.xml
./opt/libreoffice6.2/share/registry
./opt/libreoffice6.2/share/registry/calc.xcd
59673 blocks
cpio: premature end of archive
Failures:
libreoffice: libreoffice.SlackBuild return non-zero
I thought at first that it was maybe just a bad download, so I removed all trace of LO from the local SBo cache (/usr/sbo/repo), then ran sbocheck again, followed by sboupgrade. It downloaded a new file as I had hoped, then failed again in precisely the same place.
Libre Office is one of those packages I would never compile [along with things like qt5, Chromium, openjdk]. Eric does a great job with the binaries and they work perfectly.
Thanks, Eric. I just installed your LO together with the EN_GB internationalisation pack and the English dictionary, but I haven't got it to run yet. I get the splash screen and then a crash:
I found a report of a similar Arch bug from 2016 which was due to not having gtk2 installed, but I have both gtk2 and gtk3 on my system. Also found one in Debian from last year that suggested launching with the --safe-mode option. I tried that and it didn't work, so there seem to be several glitches that can cause this sort of behaviour.
I'll search a bit more but in the mean time any suggestions are welcome.
I found a dump file in ~/.config/libreoffice/4 which might give a clue to this:
Code:
ProductName=LibreOffice
Version=6.1.4.2
BuildID=9d0f32d1f0b509096fd65e0d4bec26ddd1938fd3
URL=https://crashreport.libreoffice.org/submit/
AdapterDeviceId=Gallium 0.4 on llvmpipe (LLVM 3.8, 128 bits)
AdapterVendorId=VMware, Inc.
UseOpenGL=false
Language=en-GB
ShutDown=true
What version of Slackware are you running? Where (exact URL) did you download my packages?
The dumpfile mentions 6.1.4.2 which is a version that I do not host. What is the timestamp on that file?
Do you share your homedirectory on the same computer with all these other distros you mention in your profile?
Installing package libreoffice-6.2.5-x86_64-1alien.txz:
PACKAGE DESCRIPTION:
# libreoffice (free office suite)
#
# LibreOffice is an Open Source, community-developed, office
# productivity suite. It includes key desktop applications,
# such as a word processor, spreadsheet, presentation manager,
# formula editor and drawing program, with a user interface and
# feature set similar to other office suites. LibreOffice also
# works transparently with a variety of file formats, including
# Microsoft Office File Formats.
#
# libreoffice home: http://www.documentfoundation.org/
Executing install script for libreoffice-6.2.5-x86_64-1alien.txz.
Package libreoffice-6.2.5-x86_64-1alien.txz installed.
Package libreoffice-6.1.4-x86_64-1_SBo upgraded with new package ./libreoffice-6.2.5-x86_64-1alien.txz.
So that report must have been from an earlier problem with the old version (which I can't remember btw). Anyway, I removed the entire ~/.config/libreoffice directory and tried again. It still crashes but I don't have any dump report now, so please write that off as a red herring.
My distros have a common data partition (similar to Windows MyDocuments) mounted on /home/data, but separate home directories, so no cross-contamination there!
Did you try installing via rpm and rpm2tgz or a slackbuild? I'd check to see if you've got any other versions lying around, uninstall everything related to Libre Office, then install Alien Bob's version. (Because his always work.)
The old LO was a slackbuild and was based on an rpm. I wonder if that caused any problems. OK, I'll uninstall and then clear up any LO files I find anywhere. It can't do any harm to have a clean reinstall.
Is this a Slackware 14.2 which you kept up-to-date with the updates that get released regularly (in ./patches), or is this still a Slackware 14.2 with all the original packages? My packages will usually not work on out-of-date Slackware 14.2 installations.
You might want to run it again. Also, be sure to do "slackpkg install new" after "slackpkg update," because there might be dependencies added from time to time. I'm on current, so I update every day. When I was on 14.2, I would update once a week, at a minimum, and if there were security patches, I'd update immediately.
yes you should be up to date then.
So try the following: open /etc/profile.d/libreoffice.sh in an editor and un-comment the line "export SAL_USE_VCLPLUGIN=gtk3". Then logout, login again, see if LibreOffice still crashes.
What desktop environment are you using by the way? KDE4, XFCE, ...?
Sorry I'm leading you such a dance, gentlemen! All right, I set that variable in /etc/profile.d/libreoffice.sh, logged out, logged in again, checked with printenv that it was actually set, then started X and tried again. Same result. Actually I half expected that because, like I said before, I do have both gtk libraries installed, unlike that person who posted a similar bug in the Arch forum.
The desktop is Fluxbox, my favourite WM. I don't use desktop environments because I can't understand how they work and I hate that feeling.
Now, I am going to admit something which will probably annoy you both but it may be relevant. I do not have a full Slackware install. I depend on a low-cost broadband package which has a 3GB monthly limit on downloads, so I was never able to install Slackware in the approved fashion, i.e. from a downloaded DVD image. But I think that by now I know enough about how Linux works to be able to track down most dependencies for myself and in fact it only took me a couple of weeks to get everything on my Slackware system working (including LibreOffice until now).
It is for that reason, Garpu, that I do not do an install-new when I update. It would trigger the download of huge amounts of stuff (including the whole of KDE!) and I'd end up getting fined for exceeding my quota.
But I'm aware that there are dependencies that don't show up in an ldd run for missing libraries. For example, the Slackbuild of LO expects avahi, which I do not have and do not want. It's overkill if you don't have a functioning home network. Fortunately the previous LO only required a couple of avahi libraries, not the whole package. So are there any other packages that I ought to check for? This question is particularly aimed at Eric because it's his build.
... I do not have a full Slackware install. I depend on a low-cost broadband package which has a 3GB monthly limit on downloads, so I was never able to install Slackware in the approved fashion, i.e. from a downloaded DVD image.
If it's of any help, I would gladly ship you a complete set of DVDs.
Live just across the North Sea to you, so no problem.
Just give me a call jan .reg (at) youmail .dk (remove spaces. Sorry, too new to be allowed to use pm)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
