This has already been offered by multiple forum members in another thread [and refused, if I recall]. OP doesn't live too far from me, I could quite easily go to her house and stick a Slackware USB through her letterbox [don't worry, I won't]. She just likes doing things her own way.

If I really wanted a full install, I could emulate one by simply downloading a few extra packages each month until I had the lot. But it definitely goes against the grain with me to deliberately download and install stuff that I don't expect ever to use. Also in my experience, most programs are very good about telling you if they haven't found a run-time dependency. One of the things I like about Linux is the very friendly and detailed error messages that you usually get from programs. Chances are they'll tell you what you have to do to clean up a mess; I'm always surprised when people post a problem here and quote an error message that says "Do so-and-so" and they haven't done it.

But I must admit the EM that I'm getting now from LibreOffice is double dutch to me.

You should learn to use your slackpkg blacklist...

2 members found this post helpful.

Wow! I never thought of that! I thought the blacklist was only for privately installed packages that you didn't want deleted or overwritten during a system upgrade. But yes, I see now that I could use it for that too. Like so many of the things in Slackware, it's a tool that you can adapt to your own requirements.

Thank you, orbea. I'm going to have a detailed look at that possibility over the next few weeks. Which doesn't unfortunately solve the current impasse.

I don't have a full install either and blacklisted all of of the kde, kdei, xfce series and many individual packages which I have found I did not need. However doing this in Slackware does not really have any use excluding bandwidth issues like you mentioned and to help learn how things work. Its also a great way to create your own problems which may even include this thread, for example you may be missing a dependency of a dependency which results in strange issues.

You could try running this script and it may show the problem, I use it to check for missing dependencies after updating current. However it takes a little time to run and may show only unrelated issues or false positives (i.e. firefox). Additionally it won't help for any perl, python or ruby programs.

https://notabug.org/orbea/SlackBuild...ipts/brokenpkg

3 members found this post helpful.

Excellent script. I've found quite a lot of stuff, mostly the same libraries over and over. These I'm gradually installing now, those I can find. There are a few that even file-search won't find and I'll have to track those down via DDG. Also some basic Qt libraries that I'm in two minds about. Better have them, I suppose. I remember someone posting that gnome libraries (as against the gnome desktop as a whole) didn't take up a lot of room and I dare say the same is true of Qt libraries compared with KDE. Anyway, I'm not short of disc space.

You can also search for files at packages.slackware.com by changing the Mode to "content".

https://packages.slackware.com/

Additionally sbbdep at SBo is useful for studying dependencies.

https://slackbuilds.org/repository/14.2/system/sbbdep/

Now here's a funny one and it's a libreoffice dependency too, so highly significant: libjawt.so. It's required by something called libofficebean and ldd shows it as not found. Yet it's actually in /usr/lib64/java/lib/amd64.

Now I always thought that anything in the /usr/lib64 tree automatically goes into the ld cache. I installed jre quite a while ago and ldconfig has been run at every boot since then, so why wasn't this one found? Where do you think libreoffice was looking for it?

No, it's not in ld.so.cache, I just checked.

GOT IT! It was either libneon or libdconf whose absence caused the crash. I just installed both of them and now it loads. It's slower than I remember it being, but it works.

I'd still like to understand the failure to find libjawt though, even though that didn't cause the crash.

PS: I just checked java environments inside LO, and it thinks I have two of them! The one in use is the jre that I installed and then there is one called "Free Software Foundation 1.5.0". That sounds like IcedTea to me but I can't find any trace of it on my system. Any explanations?

14.2 includes libjawt.so with the gcc-java package (in /usr/lib64/gcj-5.5.0-16/ on a fully patched 14.2). LibreOffice is probably looking there rather than the jre location.

2 members found this post helpful.

Then it will probably find it now because I installed that package about an hour ago. Hey, perhaps that's what stopped it crashing!

Anyway, thank you all very much, especially Eric for the software and Orbea for that marvellous script which from now on will become part of my monthly update process.

It just might be that ldd doesn't know where to look and its a false positive as far as that simple script is concerned.

Am I correct in my assumption that ldconfig searches all sub-directories of the standard (and other specified) library directories?

You are incorrect.

2 members found this post helpful.

Ah! That explains a lot.