On boot: Aug 17 19:51:50 init[1]: Failed to load configuration for NetworkManager-by-dbus.service: No such file or directory Aug 17 19:51:50 init[1]: D-Bus activation failed for NetworkManager-by-dbus.service: Invalid argument Aug 17 19:51:50 kernel: init[1]: Failed to load configuration for NetworkManager-by-dbus.service: No such file or directory Aug 17 19:51:50 kernel: init[1]: D-Bus activation failed for NetworkManager-by-dbus.service: Invalid argument Aug 17 19:51:53 dbus: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.62" (uid=500 pid=1925 comm="nautilus) interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply=0 destination=":1.20" (uid=0 pid=1519 comm="/usr/sbin/console-kit-daemon)) Aug 17 19:52:48 arekh init[1]: D-Bus activation failed for NetworkManager-by-dbus.service: Invalid argument Aug 17 19:52:48 arekh kernel: init[1]: D-Bus activation failed for NetworkManager-by-dbus.service: Invalid argument Version-Release number of selected component (if applicable): dbus-1.3.2-0.1.885483.fc14.x86_64 dbus-c++-0.5.0-0.11.20090203git13281b3.fc13.x86_64 dbus-glib-0.86-4.fc14.x86_64 dbus-libs-1.3.2-0.1.885483.fc14.x86_64 dbus-python-0.83.0-7.fc14.x86_64 dbus-x11-1.3.2-0.1.885483.fc14.x86_64 NetworkManager-0.8.1-4.git20100817.fc14.x86_64 NetworkManager-glib-0.8.1-4.git20100817.fc14.x86_64 NetworkManager-gnome-0.8.1-4.git20100817.fc14.x86_64 systemd-7-3.fc14.x86_64 systemd-gtk-7-3.fc14.x86_64 systemd-sysvinit-7-3.fc14.x86_64 systemd-units-7-3.fc14.x86_64
Apart from message NetworkManager-by-dbus.service: No such file or directory same issue here. The latest update of NetworkManager fails to bring up the network init[1]: D-Bus activation failed for NetworkManager-by-dbus.service: Invalid argument kernel: init[1]: D-Bus activation failed for NetworkManager-by-dbus.service: Invalid argument NetworkManager[2814]: <info> NetworkManager (version 0.8.1-4.git20100817.fc14) is starting... NetworkManager[2814]: <info> Read config file /etc/NetworkManager/NetworkManager.conf NetworkManager[2814]: <info> trying to start the modem manager... modem-manager: ModemManager (version 0.4-4.git20100720.fc14) starting... init[1]: D-Bus activation failed for NetworkManager-by-dbus.service: Invalid argument kernel: init[1]: D-Bus activation failed for NetworkManager-by-dbus.service: Invalid argument
Downgrading package NetworkManager to version 0.8.1-1.fc14 allows to restore network connectivity.
BTW NetWorkManager can be started through "service NetworkManager start", only systemd integration is broken.
I am also getting this on rawhide: NetworkManager-0.8.1-4.git20100817.fc15.x86_64 init[1]: Failed to load configuration for NetworkManager-by-dbus.service: No such file or directory init[1]: D-Bus activation failed for NetworkManager-by-dbus.service: Invalid argument kernel: init[1]: Failed to load configuration for NetworkManager-by-dbus.service: No such file or directory kernel: init[1]: D-Bus activation failed for NetworkManager-by-dbus.service: Invalid argument init[1]: D-Bus activation failed for NetworkManager-by-dbus.service: Invalid argument kernel: init[1]: D-Bus activation failed for NetworkManager-by-dbus.service: Invalid argument init[1]: D-Bus activation failed for NetworkManager-by-dbus.service: Invalid argument kernel: init[1]: D-Bus activation failed for NetworkManager-by-dbus.service: Invalid argument # /etc/rc.d/init.d/NetworkManager restart Stopping NetworkManager daemon: [FAILED] Setting network parameters... [ OK ] Starting NetworkManager daemon: [ OK ]
Workaround # systemctl enable NetworkManager.service # systemctl start NetworkManager.service
No problems anymore after upgrading to NetworkManager-0.8.1-5.git20100818.fc14.
(In reply to comment #5) > Workaround > > # systemctl enable NetworkManager.service > # systemctl start NetworkManager.service This does work.
NetworkManager-0.8.1-5.git20100818.fc14 fixed the problem for me as well
NetworkManager-0.8.1-5.git20100818.fc14 has been submitted as an update for Fedora 14. http://admin.fedoraproject.org/updates/NetworkManager-0.8.1-5.git20100818.fc14
*** Bug 625837 has been marked as a duplicate of this bug. ***
*** Bug 625386 has been marked as a duplicate of this bug. ***
NetworkManager-0.8.1-5.git20100818.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
Just did a fresh preupgrade from F13 -> F14 and a yum update after that: NetworkManager-0.8.1-5.git20100818.fc14.i686 NetworkManager-glib-0.8.1-5.git20100818.fc14.i686 NetworkManager-gnome-0.8.1-5.git20100818.fc14.i686 NetworkManager-vpnc-0.8.1-1.fc14.i686 systemd-7-3.fc14.i686 systemd-sysvinit-7-3.fc14.i686 I have the latest NetworkManager package but the problem still exists. /var/log/messages after boot: Aug 25 15:42:47 l3f1199 init[1]: Failed to load configuration for dbus-org.freedesktop.NetworkManager.service: No such file or directory Aug 25 15:42:47 l3f1199 init[1]: D-Bus activation failed for dbus-org.freedesktop.NetworkManager.service: Invalid argument Aug 25 15:42:47 l3f1199 kernel: init[1]: Failed to load configuration for dbus-org.freedesktop.NetworkManager.service: No such file or directory Aug 25 15:42:47 l3f1199 kernel: init[1]: D-Bus activation failed for dbus-org.freedesktop.NetworkManager.service: Invalid argument Aug 25 15:42:49 l3f1199 init[1]: D-Bus activation failed for dbus-org.freedesktop.NetworkManager.service: Invalid argument Aug 25 15:42:49 l3f1199 kernel: init[1]: D-Bus activation failed for dbus-org.freedesktop.NetworkManager.service: Invalid argument The systemctl workaround works for me too. I still have to test if it fixes the problem permanently, i.e. after a reboot.
Just doing a yum update isn't going to cause NetworkManager to magically start up. You'll need to reboot after the update to NetworkManager-0.8.1-5.git20100818.fc14 to actually see the fix.
Sorry, I forgot to mention that I *did* reboot after "yum update" and still the problem wasn't fixed. Only the manual systemctl commands fixed it for my machine.
Not an issue anymore as f14 didn't ship with systemd, and this issue is not present on F15 where systemd is used.