Description of problem: NetworkManager do not connect to eth0 after Notebook Suspended Version-Release number of selected component (if applicable): nmcli --version nmcli tool, version 0.8.0.997 Steps to Reproduce: 1. Battery of Notebook on KDE have empty and KDE suspend the Notebook 2. After plug the AC adapter and restart KDE the NetworkManager do not create eth0 connection 3. Actual results: # service network restart Desligando a interface loopback: Error org.freedesktop.NetworkManagerSettings.InvalidConnection: ifcfg file '/etc/sysconfig/network-scripts/ifcfg-lo' unknown Error org.freedesktop.NetworkManagerSettings.InvalidConnection: ifcfg file '/etc/sysconfig/network-scripts/ifcfg-lo' unknown Error org.freedesktop.NetworkManagerSettings.InvalidConnection: ifcfg file '/etc/sysconfig/network-scripts/ifcfg-lo' unknown Error org.freedesktop.NetworkManagerSettings.InvalidConnection: ifcfg file '/etc/sysconfig/network-scripts/ifcfg-lo' unknown [ OK ] Iniciando a interface loopback: Error org.freedesktop.NetworkManagerSettings.InvalidConnection: ifcfg file '/etc/sysconfig/network-scripts/ifcfg-lo' unknown Error org.freedesktop.NetworkManagerSettings.InvalidConnection: ifcfg file '/etc/sysconfig/network-scripts/ifcfg-lo' unknown Error org.freedesktop.NetworkManagerSettings.InvalidConnection: ifcfg file '/etc/sysconfig/network-scripts/ifcfg-lo' unknown Error org.freedesktop.NetworkManagerSettings.InvalidConnection: ifcfg file '/etc/sysconfig/network-scripts/ifcfg-lo' unknown [ OK ] Iniciando a interface eth0: Error: Connection activation failed: Device not managed by NetworkManager [FALHOU]
You can either run dbus_send --print-reply --system \ --dest=org.freedesktop.NetworkManager \ /org/freedesktop/NetworkManager \ org.freedesktop.NetworkManager.wake or run service network-manager stop rm /var/lib/NetworkManager/NetworkManager.state service network-manager start But i agree there's maybe a better way to handle such cases. Though i'm the wrong one for a patch, sorry Dan.
hm.. related? https://bugzilla.redhat.com/show_bug.cgi?id=583113
(In reply to comment #2) > hm.. related? https://bugzilla.redhat.com/show_bug.cgi?id=583113 Probably not, I think that's a different issue. The '/etc/sysconfig/network-scripts/ifcfg-lo' unknown' thing is an initscripts issue but that shouldn't have any effect on the OP's problem. Pasting in the state file (before removing it) as shown in comment 1 would be helpful.
See also bug #598765 , where we're working to add an "Enable Networking" option to knetworkmanager, similar to nm-applet, which I think will end up doing something simlilar to the 'wake' dbus message referenced in comment #1
I think this is fixed in latest updates by bypassing pm-utils entirely with the issues of short-lived dbus-send processes not delivering messages correctly: https://admin.fedoraproject.org/updates/NetworkManager-0.8.1-6.git20100831.fc13 This build has that change in it and should be resistant to pm-utils and dbus-send suckage.