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.
When I ran slackpkg this morning I noticed that Saturday's files were not among the files received. (Though they have since been updated)
I don't typically use that mirror, but changed to it a week (or so) ago when kernel.org was having "technical difficulties"
I am not superstitious, as that brings misfortune.
It is a big jinx to be superstitious, so just You know.
Some clinical studies show that it is best to visit an fortune teller at that day (before sunset) or an traditional doctor (a.k.a. druid) to break the chain of misfortune...
Please forgive and direct me to the proper thread (unsure if this note is deserving of it's own), I skipped a bunch of updates in my -current, and went from kernel 5.10.34-smp to 5.13.7-smp and the only hitch I've noticed is that I had to finally leave wicd behind...networkmanager is "fine", and now my wifi LED blinks constantly...
Reverted to 5.10.34, and it works normally again even with the dweebatronic networkmanager!
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,104
Original Poster
Rep:
Year 2021, Round 52.
Another batch of updates has been scheduled for release Wednesday, 4 August 2021, at approximately 14:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Tuesday (depending on your time zone).
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,104
Original Poster
Rep:
Quote:
Originally Posted by STDOUBT
Please forgive and direct me to the proper thread (unsure if this note is deserving of it's own), I skipped a bunch of updates in my -current, and went from kernel 5.10.34-smp to 5.13.7-smp and the only hitch I've noticed is that I had to finally leave wicd behind...networkmanager is "fine", and now my wifi LED blinks constantly...
Reverted to 5.10.34, and it works normally again even with the dweebatronic networkmanager!
Thinkpad R61 (4lyf)
You are in the right place, but IIRC, there have been a couple of threads on this topic.
My memory isn't what it once was (getting old isn't for the faint of heart), but, again,
IIRC, wicd is no longer maintain and has been dropped from -current (you may already
know that?).
Quote:
+--------------------------+
Sat Aug 1 19:08:49 UTC 2020
........
l/urwid-1.0.3-x86_64-5.txz: Removed.
This is an ancient version that was only used by wicd.
..........
extra/wicd/wicd-1.7.4-x86_64-3.txz: Removed.
This is unmaintained, possibly insecure, and doesn't work with Python
versions newer than 2.7.18. NetworkManager is a better choice these days.
+--------------------------+
Seach the forum and you should find the information you need.
Last edited by cwizardone; 08-02-2021 at 10:49 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
