NetworkManager Troubles Since Last Night's Updates.
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.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,107
Rep:
NetworkManager Troubles Since Last Night's Updates.
First, I've always set NetworkManager to NOT auto connect. I prefer to manually connect and disconnect.
Installed last night -current updates and, at first things appeared to be OK. (The sound works, BTW. )
Brought up NetworkManager (hereafter NM) and it appeared OK.
Clicked on "Connect" and nothing happened. Logged out and logged in as root. Ditto. Same problem.
Changed the settings to "auto connect" and rebooted. Logged in as user and NM looked OK, that is the applet came up and the word "Connect" was displayed as if I wasn't connect, BUT I was connected. I can click on "Connect" and it will disconnect, but it doesn't show that. The word "Connect" remains. Once disconnect I cannot reconnect.. If I log off and then log back in, I'm once again auto connected.
Any ideas?
Thanks.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,107
Original Poster
Rep:
Today I "removepkg"-ed NetworkManager, deleted /etc/NetworkManager, then "upgradepkg --reinstall --install-new"-ed NetworkManager and ran the network configuration utility from pkgtool.
As I type this the NetworkManager applet indicates I'm not connected, but, of course,
I am.
Next I'm going to revert to an older version and see if that "fixes" the problem.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,107
Original Poster
Rep:
OK, I ran removepkg on NetworkManager, curl and bind and deleted /etc/NetworkManager.
Then I installed
bind-9.16.18-x86_64-1,
curl-7.77.0-x86_64-1
and
NetworkManager-1.26.4-x86_64-1.
Then I ran netconfig via pkgtool and, finally, rebooted.
All is now back to what passes as normal.
I'm NOT making any more changes to any of the aforementioned packages unless it gets to the point it is absolutely necessary.
Last edited by cwizardone; 08-19-2021 at 12:51 PM.
Reason: Typo.
OK, I ran removepkg on NetworkManager, curl and bind and deleted /etc/NetworkManager.
Then I installed
bind-9.16.18-x86_64-1,
curl-7.77.0-x86_64-1
and
NetworkManager-1.26.4-x86_64-1.
Then I ran netconfig via pkgtool and, finally, rebooted.
All is now back to what passes as normal.
I'm NOT making any more changes to any of the aforementioned packages unless it gets to the point it is absolutely necessary.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.