[SOLVED] After upgrade to 14.2: X:Error loading shared libraries. libudev.so.0:cannot open shared object file
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.
Reboot and issue 'wicd-curses' from the console to connect.
(Another recommendation made by Slackware is a full install. It's probably best if you do this in future even if you don't want KDE. It makes it a lot easier in situations like this).
for the sake of clarity, can you tell us whether you have a 3G mifi router to which you connect wirelessly (802.11), or a 3G modem you plug into a USB port, which is a different type of wireless connection (wireless WAN)? I don't think wicd supports this kind of connection, but nmtui might do.
Last edited by Gerard Lally; 07-03-2016 at 07:14 AM.
I suggest you to to dump that crap and buy a real modem. You do not see that it give you transfer errors?
IF I will have to use that shit, err... "blaze ultra-crap", I would choose the downloading of the full ISO via torrent, for the sake of the pieces checksum, check the torrent four times, then I would follow very careful that UPGRADE.TXT.
From when slackpkg-ing without kernel upgrade is recommended method of upgrading on Slackware? I laugh my ass!
Last edited by Darth Vader; 07-03-2016 at 08:34 AM.
San2ban, your install seems borked: NetworkManager seems to be at the old version.
IMHO, the only way to solve is to download a slackware64-14.2 iso and reinstall all the packages.
I would choose the downloading of the full ISO via torrent, for the sake of the pieces checksum, check the torrent four times
What is the point of checking it four times? The checksum won't randomly change after it's done downloading...
This is like all the people telling Android owners to do a full wipe 3x. There's no point. One wipe is enough, just as one checking of the torrent is enough.
In this case, is just a safety measure that we do not have also a ultra-crap hard disk (unstable sectors).
IF the ISO was successfully read four times, you can bet that it will give you some fine data on the number five attempt.
This is still overkill. If there aren't any checksum errors when the file is downloaded, and it passes a second check (which many clients complete when the torrent is finished), it isn't likely anything else would happen... at least not on a semi-stable system. If your system is already running into a ton of problems that may be harddrive related, then checking a torrent should be the least of your concerns and you should work on getting replacement hardware.
Quote:
Originally Posted by zk1234
That's not true. The best wiping techniques use multiplied passes.
This is completely false... for Android. We aren't talking about securely removing files to prevent disk recovery software from finding them, we're talking about removing files so the filesystem can't see them anymore. One pass will do, and no more are needed. If you format a filesystem in Linux (or run rm file) then you can't access that data using normal tools. For all intents and purposes, that data is gone.
This fallacy has been floating around longer than using a taskmanager to kill all running applications in Android to help save your battery.
ok what i found on all my upgrades from 14.1 to current to slackware 14.2 for the last 5 months is.
For some reason networkmanager using it used eth1 instead of eth0 I only have one device. I have no clue why but when I go to the "/etc/rc./rc.intet1.conf" and add yes to the eth1 and reboot networkmanager is happy. it is only this way on an upgrade ok. from a new install that is not an issue.
I have no clue why because I stop caring I brought this up I think last year or the very begening of this year. I noticed the same thing happen again on my latest stable upgrade last night.
as for the udev problem that was solved many moons ago slackpkg install-new would have fixed that. and after your done. with the upgrade clean the system and
start fresh time. Why because this is the most incredible virgin Pat has put out and she needs to start clean only my point of view.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.