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.
Check if your openssl package was upgraded to 0.9.8a along with all the other "-current" packages (I assume you upgraded everything to -current?).
This was changed on feb 9th: openssl-solibs-0.9.8a-i486-1.tgz and openssl-0.9.8a-i486-1.tgz
Also worth mentioning with Slackware -current: when Slackware is in development towards a new release, new packages may get added. If you only upgrade packages you already had installed, you will miss all the new stuff, and some applications will refuse to run if they depend on these new ones.
Just to name a few from the ChangeLog:
openldap-client
db44
db42
cairo
amarok
libmusicbrainz
libtunepimp
linuxdoc-tools
I had the same exact problem yesterday. Try compiling OpenSSH from source. I'm not completely sure of why this works but I've learned not to use .tgz's, as they're too irritating (unreliable) to work with.
Also worth mentioning with Slackware -current: when Slackware is in development towards a new release, new packages may get added. If you only upgrade packages you already had installed, you will miss all the new stuff, and some applications will refuse to run if they depend on these new ones.
Yes, I followed the Changelog. So I also have the new packages. But I don't have the official packages of openldap-client, cairo and libmusicbrainz since they are included in Gware.
I had the same exact problem yesterday. Try compiling OpenSSH from source. I'm not completely sure of why this works but I've learned not to use .tgz's, as they're too irritating (unreliable) to work with.
Do you mean *all* .tgz's, or just the ones for OpenSSH?
I've encountered a wealth of supposed "official" Slackware packages that have done not but to leave me slocating througout my directories only to find that nothing has been installed or extracted anywhere.
i'm not familiar with "supposedly" official packages.
they are either officially maintained and appear on
the official mirrors or not. if, on the other hand, you
are referring to repo packages maintained by cluebies...
then i certainly agree with you.
if the official packages are not installing correctly,
then something is seriously wrong with your setup.
It's indeed a strange problem. I removed the openssh, openssl and openssl-solibs packages, downloaded them from a USA mirror and reinstalled them. SSH is working again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.