Red Hat Bugzilla – Bug 202008
NetworkManager crashes upon boot
Last modified: 2008-04-08 03:55:43 EDT
Description of problem: NetworkManager crashes at boot time (1 out of 4 times or so) Version-Release number of selected component (if applicable): [pontus@kesella ~]$ rpm -q NetworkManager glibc NetworkManager-0.6.4-1.fc5 glibc-2.4-8 How reproducible: I have so far only seen this during boot, but it does not occur every time on boot (perhaps 1 out of 4 times) If i start the NetworkManager from the console after such a crash it starts up happily! Steps to Reproduce: 1. boot up 2. check if the NetworkManager actually managed to start 3. Actual results: see attached log from /var/log/messages Expected results: Additional info: log consists of the grep:ed messages (grepping for NetworkManager) with the snippet of the trace of the crash inserted by me on the correct place Since i am not a hacker, i filed this under NetworkManager although the trace point to a glibc file.
Created attachment 133931 [details] snippets from /var/log/messages
Is this still an issue? Can you install NetworkManager-debuginfo to get a better backtrace?
Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are 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. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers
OK i have reeenabled the NM and the NMD to see whether this still is a problem - i know that this have been coinsistent for me up to at least F7 and possibly F8 (i cannot recall correctly whether i have suffered any crashes during F8 since i have it disabled due to the crashes... but i will investigate it further i feel pretty confident that it was not that long ago that i had a crash on the NM/NMD)
OK after some days of quite intense testing due to other unrelated investigation i now dare say that this works for me again. is WORKSFORME the correct resolution of this bug then ? brg Pontus