Greetings
In the past month or so a few apps that did work before now fail with "libgnutls.so.30 not found" error message. I use zero apps that automate dependencies and have done no base system upgrades in years since I made the move to v14.0 32 bit. I always thought that in almost every case that without upgrades any app that worked yesterday should/would work today. Now things as basic as rc.cups fail with this error. Maybe I'm jut dense or going senile but how can this happen?

Accidental deletion when you thought you were deleting something else.

Issue with the underlying disk causing corruption in the filesystem.

Change in the library path variable in /etc/profile or other file such as bashrc or bash_profile either in /etc or for specific user?

Change in /etc/ld.so.conf

Have you done a find for the file?

Have you examined dmesg output and /var/log/messages?

If you really think you've changed nothing I'd suggest doing an immediate full backup then doing a boot with full fsck on your filesystems.

If you're running 14.0 then you should have a symlink '/usr/lib/libgnutls.so.28' and the file '/usr/lib/libgnutls.so.28.41.9'.

If some other stuff wants 'libgnutls.so.30', you have wrongly installed other stuff that was built for -current (or a different distro) instead of Slackware 14.0. Get rid of the other stuff. Go back and get the right other stuff. It's not your libgnutls that's wrong -- it's the other stuff that's wrong.

If you've got the file 'libgnutls.so.28.10.2', then you are using the original Slackware 14.0 gnutls package. That package has multiple serious security vulerabilities. You should upgrade it using http://slackware.uk/slackware/slackw..._slack14.0.txz. Note, this is nothing to do with your problem -- it's just good advice while you're considering that file.

Lastly, if some plonker rocks up in this thread and suggests creating a symlink 'libgnutls.so.30' pointing to 'libgnutls.so.28', ignore them. You'll regret it, sooner or later.

3 members found this post helpful.

slackpkg update slackpkg upgrade-all and slackpkg install-new and make sure you are letting it update aaa_elflibs
by the way that is black listed in 14.1 and earlier and it should not be.
that has been corrected in the latest /etc/slackpkg/blacklist
that will cause it. reinstall it.

Thank you Drakeo but I do not nor will EVER use an automated dependency resolving app/package manager.

No automated dependency resolving is done by slackpkg.

@55020 - To my knowledge I have never installed anything that could let alone would do this. As I said (and for one example) I compiled Chrome from source and it worked fine until one day it just didn't. By launching from CLI i saw the error message

In /usr/lib I find libgnutls.so.26, libgnutls.so.28 and libgnutls.so.28.10.2 so I downloaded the upgrade you recommended but I am still at a loss for what to do about broken packages or even how this happened. Right now I am mainly concerned with cups which will not run for the same reason. Chrome is no big loss but there are no alternatives for cups. So I guess I just keep hunting and watching this thread. FWIW as I mentioned to Drakeo, I am extremely conservative about updates/upgrades of any kind. I have little need for "latest" and don't always agree they are "greatest". I never blindly upgrade. I have to see a truly compelling reason to warrant changing a working system, so this has me a bit upset.

Edit: I did upgrade cups so that one is understandable. I just have no idea what happened to chrome.

Would it be possible that Chrome performed a cheeky background update?

EDIT: Disclaimer - I only use Chrome for netflix lately, haven't got a clue if auto-updates are even a thing.

Chrome? No you didn't (unless you mean Chromium). Chrome is closed source, and Patrick's SlackBuild in extra/ just repackages the binary from Google, and your problem indicates that apparently Google have started linking the binary against a newer gnutls. Which means you're basically out of luck.

If you've kept an older version of Chrome, you can go back to that; I doubt Google have any older versions of Chrome still available (they tend not to do that) but you might find one somewhere. If you want a newer version of Chrome, you can upgrade Slackware (it would need to be 14.2RC). That's the way it is with closed source, unfortunately; no easy choices.

There's an outside chance that something really nasty would work. Maybe you could installpkg (not upgradepkg) gnutls-3.4.10-i586-1.txz from slackware-current and then installpkg gnutls-3.3.17.1-i486-1_slack14.0 from slackware-14.0 patches to fixup the symlinks.

Otherwise, Alien BOB has a prebuilt Chromium 37 for 32 bit 14.0 at http://slackware.uk/people/alien/sla...mium/pkg/14.0/

(If you were really building Chromium from source, you'd know about it. Chromium is the biggest build in the whole of SlackBuilds.org and typically needs three hours to a whole day, depending on your cpu and memory.)

1 members found this post helpful.

If you're running -current, this probably happened after one of the updates to gnutls. The solution is to recompile the broken packages.

The OP is running Slackware 14.0 32-bit if I understand well.

Merci, Didier, I stand corrected, or mostly since I still prefer manually seeing the file before I install it

Thank you very much 55020 ! You nailed it. It IS Chrome, not chromium, and my memory was off. I had recalled downloading Chrome-foo.deb and forgotten that's how the SlackBuild is handled due to pam iirc. I was not very concerned about Chrome as I have several browsers and Chrome didn't "knock me out". I was very concerned about cups and apparently forgotten that I'd tried a newer one to attempt to handle a new HP OfficeJet All-in-One. Now it is a reminder to try to finish a job once started and not leave it for another day without notes.

So, as you noted, Chrome was changed as to how it is linked, and I'm out of luck on that score until I finally install 14.2 possibly. Cups was a my fault in jumping one version too far, to the one in -Current. I simply tried the cups version from 14.1 and the very reason that I haven't "upgraded" to 14.1, not that much changed, worked in my favor as that version, libgnutls.so.30.6.2 is new enough to work with the updated cups to handle my printer but by not replacing the updated (patched) libgnutls.so.28.41.9, all the 14.0 stuff still works just fine.

Just FTR, MensaWater, I never delete an important file without having renamed it first to determine no problems result. Once established safe then I delete.

Everything is copacetic now. Thanks all. Solved.

I LOVE THAT WORD!!! It does one job, and does it well.
Learned it (and much more) from this guy.
*Thanks* for triggering the memory.