NetworkManager seems to have disappeared when I updated to Fedora 30. Not only didn't my network start on reboot after upgrade, there is no NetworkManager.service to enable or start with systemctl. Running dnf list NetworkManager replies:
Last metadata expiration check: 0:16:45 ago on Sun 12 May 2019 08:02:12 AM PDT. Error: No matching Packages to list
Running dnf list NetworkManager* returns:
Installed Packages NetworkManager-config-connectivity-fedora.noarch 1:1.16.0-1.fc30 @fedora NetworkManager-libnm.x86_64 1:1.16.0-1.fc30 @fedora Available Packages NetworkManager-adsl.x86_64 1:1.16.0-1.fc30 fedora NetworkManager-bluetooth.x86_64 1:1.16.0-1.fc30 fedora NetworkManager-config-server.noarch 1:1.16.0-1.fc30 fedora NetworkManager-dispatcher-routing-rules.noarch 1:1.16.0-1.fc30 fedora NetworkManager-fortisslvpn.x86_64 1.2.10-1.fc30 fedora NetworkManager-fortisslvpn-gnome.x86_64 1.2.10-1.fc30 fedora NetworkManager-iodine.x86_64 1.2.0-8.fc30 fedora NetworkManager-iodine-gnome.x86_64 1.2.0-8.fc30 fedora NetworkManager-l2tp.x86_64 1.2.12-1.fc30 fedora NetworkManager-l2tp-gnome.x86_64 1.2.12-1.fc30 fedora NetworkManager-libnm.i686 1:1.16.0-1.fc30 fedora NetworkManager-libnm-devel.i686 1:1.16.0-1.fc30 fedora NetworkManager-libnm-devel.x86_64 1:1.16.0-1.fc30 fedora NetworkManager-libreswan.x86_64 1.2.10-1.fc30.1 fedora NetworkManager-libreswan-gnome.x86_64 1.2.10-1.fc30.1 fedora NetworkManager-openconnect.x86_64 1.2.4-11.fc30 fedora NetworkManager-openconnect-gnome.x86_64 1.2.4-11.fc30 fedora NetworkManager-openvpn.x86_64 1:1.8.10-1.fc30 fedora NetworkManager-openvpn-gnome.x86_64 1:1.8.10-1.fc30 fedora NetworkManager-ovs.x86_64 1:1.16.0-1.fc30 fedora NetworkManager-ppp.x86_64 1:1.16.0-1.fc30 fedora NetworkManager-pptp.x86_64 1:1.2.8-1.fc30.1 fedora NetworkManager-pptp-gnome.x86_64 1:1.2.8-1.fc30.1 fedora NetworkManager-ssh.x86_64 1.2.9-1.fc30 fedora NetworkManager-ssh-gnome.x86_64 1.2.9-1.fc30 fedora NetworkManager-sstp.x86_64 1:1.2.6-3.fc30 fedora NetworkManager-sstp-gnome.x86_64 1:1.2.6-3.fc30 fedora NetworkManager-strongswan.x86_64 1.4.4-2.fc30 fedora NetworkManager-strongswan-gnome.x86_64 1.4.4-2.fc30 fedora NetworkManager-team.x86_64 1:1.16.0-1.fc30 fedora NetworkManager-tui.x86_64 1:1.16.0-1.fc30 fedora NetworkManager-vpnc.x86_64 1:1.2.6-2.fc30 fedora NetworkManager-vpnc-gnome.x86_64 1:1.2.6-2.fc30 fedora NetworkManager-wifi.x86_64 1:1.16.0-1.fc30 fedora NetworkManager-wwan.x86_64 1:1.16.0-1.fc30 fedora
So what to I install to get Network manager back.
I've managed to get my network functional by using network scripts and systemctl start network, But I would like to be able to select also connect to a wireless network.
What am I missing?
Note that running nm-coonnection-editor give me a network manager dialog, but none of the fields are enabled.
Emmett
On 5/12/19 11:29 PM, Emmett Culley via users wrote:
So what to I install to get Network manager back.
FWIW, I have the following installed after an upgrade to F29 to F30 and no issues.
[egreshko@meimei ~]$ rpm -qa | grep -i ^network NetworkManager-wwan-1.16.0-1.fc30.x86_64 NetworkManager-1.16.0-1.fc30.x86_64 NetworkManager-l2tp-1.2.12-1.fc30.x86_64 NetworkManager-libnm-1.16.0-1.fc30.x86_64 NetworkManager-libreswan-1.2.10-1.fc30.1.x86_64 NetworkManager-openvpn-1.8.10-1.fc30.x86_64 NetworkManager-adsl-1.16.0-1.fc30.x86_64 NetworkManager-pptp-1.2.8-1.fc30.1.x86_64 NetworkManager-wifi-1.16.0-1.fc30.x86_64 NetworkManager-bluetooth-1.16.0-1.fc30.x86_64 NetworkManager-team-1.16.0-1.fc30.x86_64 NetworkManager-openconnect-1.2.4-11.fc30.x86_64 NetworkManager-vpnc-1.2.6-2.fc30.x86_64
What do you get for....
systemctl status NetworkManager
On 5/12/19 4:58 PM, Ed Greshko wrote:
On 5/12/19 11:29 PM, Emmett Culley via users wrote:
So what to I install to get Network manager back.
FWIW, I have the following installed after an upgrade to F29 to F30 and no issues.
[egreshko@meimei ~]$ rpm -qa | grep -i ^network NetworkManager-wwan-1.16.0-1.fc30.x86_64 NetworkManager-1.16.0-1.fc30.x86_64 NetworkManager-l2tp-1.2.12-1.fc30.x86_64 NetworkManager-libnm-1.16.0-1.fc30.x86_64 NetworkManager-libreswan-1.2.10-1.fc30.1.x86_64 NetworkManager-openvpn-1.8.10-1.fc30.x86_64 NetworkManager-adsl-1.16.0-1.fc30.x86_64 NetworkManager-pptp-1.2.8-1.fc30.1.x86_64 NetworkManager-wifi-1.16.0-1.fc30.x86_64 NetworkManager-bluetooth-1.16.0-1.fc30.x86_64 NetworkManager-team-1.16.0-1.fc30.x86_64 NetworkManager-openconnect-1.2.4-11.fc30.x86_64 NetworkManager-vpnc-1.2.6-2.fc30.x86_64
What do you get for....
systemctl status NetworkManager
[root@ws1 network-scripts]# systemctl status NetworkManager Unit NetworkManager.service could not be found.
On 5/13/19 7:51 AM, Emmett Culley via users wrote:
On 5/12/19 4:58 PM, Ed Greshko wrote:
On 5/12/19 11:29 PM, Emmett Culley via users wrote:
So what to I install to get Network manager back.
FWIW, I have the following installed after an upgrade to F29 to F30 and no issues.
[egreshko@meimei ~]$ rpm -qa | grep -i ^network NetworkManager-wwan-1.16.0-1.fc30.x86_64 NetworkManager-1.16.0-1.fc30.x86_64 NetworkManager-l2tp-1.2.12-1.fc30.x86_64 NetworkManager-libnm-1.16.0-1.fc30.x86_64 NetworkManager-libreswan-1.2.10-1.fc30.1.x86_64 NetworkManager-openvpn-1.8.10-1.fc30.x86_64 NetworkManager-adsl-1.16.0-1.fc30.x86_64 NetworkManager-pptp-1.2.8-1.fc30.1.x86_64 NetworkManager-wifi-1.16.0-1.fc30.x86_64 NetworkManager-bluetooth-1.16.0-1.fc30.x86_64 NetworkManager-team-1.16.0-1.fc30.x86_64 NetworkManager-openconnect-1.2.4-11.fc30.x86_64 NetworkManager-vpnc-1.2.6-2.fc30.x86_64
What do you get for....
systemctl status NetworkManager
[root@ws1 network-scripts]# systemctl status NetworkManager Unit NetworkManager.service could not be found.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
I fond the problem:
[root@ws1 yum.repos.d]# grep NetworkMan * fedora.repo:exclude=NetworkManager
I had disabled updating NetworkManager when attempting to resolve another issue a few months ago. Sorry for the noise
Emmett
-
Ed Greshko -
Emmett Culley