Description of problem: All of a sudden, NM fell over. That message was in the logs. Now, NM just dies with the same message every time I try to start it. Version-Release number of selected component (if applicable): NetworkManager-0.7.0-0.3.svn2983.fc8
I occasionally see this too. When this happens, restarting messagebus and haldaemon before NetworkManager doesn't seem to allow it to recover. I need to reboot for it to work again. x86_64 iwl3945
will put some debugging info into the next build to try to narrow this down
If you get this again, please update. The debugging info is there.
*** Bug 319051 has been marked as a duplicate of this bug. ***
I can almost guarantee that this is related to the execrable gconf, as rebooting did NOT fix anything for me, but deleting ~/.gconf/system/networking and rebooting DID.
Based on the date this bug was created, it appears to have been reported during the development of Fedora 8. In order to refocus our efforts as a project we are changing the version of this bug to '8'. If this bug still exists in rawhide, please change the version back to rawhide. (If you're unable to change the bug's version, add a comment to the bug and someone will change it for you.) Thanks for your help and we apologize for the interruption. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again.
I'm seeing a similar, but less severe issue in rawhide. o NetworkManager is running, connected to my home wireless Network. o I hibernate the system. (Staying logged in) o I come into the office the next morning, plug in the wired network cable, and power on the system. o When the system is done booting, I enter my screensaver password, and everything seems to be fine, except there's no NM icon. doing a 'service restart NetworkManager' as root fixes the problem. I'll attach NetworkManager's droppings in /var/log/messages from when I went into hibernate mode until after resuming. The error is the same as the one in the summary of this bug. $ rpm -q NetworkManager dbus NetworkManager-0.7.0-0.9.3.svn3623.fc9.i386 dbus-1.2.1-1.fc9.i386
Created attachment 305366 [details] Error log of crash
Robin; this should be fixed in latest rawhide/koji bits, please try svn3669 or later: http://koji.fedoraproject.org/koji/taskinfo?taskID=608605 (f8) http://koji.fedoraproject.org/koji/taskinfo?taskID=608593 (f9) http://koji.fedoraproject.org/koji/taskinfo?taskID=608599 (f10) can you test those? Also, were you connected with VPN at the time of the hibernate?
Yes, I was connected to the VPN when I hibernated (almost certainly). I've just installed the above version, and I'll let you know how it works out in the morning.
That updated version specifically fixes a refcounting issue that triggered the dbus-glib assertion after resuming from hibernate when the VPN was active before going to sleep, and I'm pretty sure your issue is the same. Let me know!
Yes, NetworkManager seems to survive hibernation now. Thanks!