Description of problem: Updating to 0.9.3.995-0.4.git20120302.fc17 causes the network to fail to come up. Reverting to 0.2.git20120215 fixes. systemctl start network.service also brings the network up. Mar 6 04:36:45 vmf17 NetworkManager[6029]: <info> Networking is enabled by state file Mar 6 04:36:45 vmf17 NetworkManager[6029]: <warn> failed to allocate link cache Mar 6 04:36:45 vmf17 NetworkManager[6029]: <info> (eth0): carrier is OFF Mar 6 04:36:45 vmf17 NetworkManager[6029]: <error> [1331033805.940807] [nm-device-ethernet.c:456] real_update_permanent_hw_address(): (eth0): unable to read permanent MAC address (error 0) Mar 6 04:36:45 vmf17 NetworkManager[6029]: <info> (eth0): new Ethernet device (driver: 'virtio_net' ifindex: 2) Mar 6 04:36:45 vmf17 NetworkManager[6029]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0 Mar 6 04:36:45 vmf17 dbus-daemon[437]: dbus[437]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. Mar 6 04:36:45 vmf17 NetworkManager[6029]: <info> (eth0): now managed Mar 6 04:36:46 vmf17 NetworkManager[6029]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Mar 6 04:36:46 vmf17 NetworkManager[6029]: <info> (eth0): bringing up device. Mar 6 04:36:46 vmf17 NetworkManager[6029]: <info> (eth0): carrier now ON (device state 20) Mar 6 04:36:46 vmf17 NetworkManager[6029]: <info> (eth0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40] Mar 6 04:36:46 vmf17 NetworkManager[6029]: <info> (eth0): preparing device. Mar 6 04:36:46 vmf17 NetworkManager[6029]: <info> (eth0): deactivating device (reason 'managed') [2]
I'm seeing the same problem (I think): - it only affects f17; f16 and rawhide not showing the same problem - affects both i686 and x86_64 - ifconfig shows an IPV6 address, but no IPV4 - "service network restart" works
I'm seeing the same problem: - it only affects f17 -- f16 not showing the same problem -- rawhide not showing the same problem even though it has the same version of NM <<<<<NB - affects both i686 and x86_64 - ifconfig shows an IPV6 address, but no IPV4 <<<<<NB - "service network restart" works - confirmed that reverting to 0.9.3-0.2.git20120215 works on both i686 and x86_64
Mind giving: https://admin.fedoraproject.org/updates/NetworkManager-0.9.3.995-0.5.git20120313.fc17 a shot? If that doesn't work, can you, as root: 1) systemctl stop NetworkManager 2) NetworkManager --no-daemon --log-level=debug and see what happens for me?
Created attachment 569790 [details] NetworkManager --no-daemon --log-level=debug output New update doesn't work
It may have partially worked for me. ifconfig now shows an IP4 address, but the machine is still inaccessible because a number of other deamons are now not getting started. I noticed: sshd, avaihi-daemon, and gpm were not started. There might be others. I have to out ... I'll generate a trace from --no-daemon in a couple of hours and attach here....
For me, when I installed the update and restarted NM, the network stayed up. But when I rebooted, NM could not bring the network up.
Sorry. Ignore comment #5. I was looking at the wrong virtual machine. Basically no change from the fix. Still no IP4 address assigned.
Created attachment 569853 [details] output from "NetworkManager --no-daemon --log-level=debug >output 2>&1" This was the output from NM startup. I did not include the ^C termination part.
NetworkManager-0.9.3.995-0.6.git20120314.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/NetworkManager-0.9.3.995-0.6.git20120314.fc17
NetworkManager-0.9.3.995-0.6.git20120314.[fc17|fc18].[i686|x86_64] all work for me.
(In reply to comment #10) > NetworkManager-0.9.3.995-0.6.git20120314.[fc17|fc18].[i686|x86_64] > all work for me. Great, thanks for testing; if you can Karma+1 it like Orion did, that'd also be great :)
Package NetworkManager-0.9.3.995-0.6.git20120314.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing NetworkManager-0.9.3.995-0.6.git20120314.fc17' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-3861/NetworkManager-0.9.3.995-0.6.git20120314.fc17 then log in and leave karma (feedback).
NetworkManager-0.9.3.995-0.6.git20120314.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.