Description of problem: When NetworkManager is enabled for runlevels 3 4 and 5 via chkconfig, it fails to function correctly. A "/usr/sbin/named -f -u named -c /var/named/data/NetworkManager-named.conf" process is started, however the "NetworkManager" process is not (or it exits rather quickly). Version-Release number of selected component (if applicable): [root@windu ~]# rpm -q NetworkManager NetworkManager-0.4-15.cvs20050404 How reproducible: Always Steps to Reproduce: 1. Enable NetworkManager via chkconfig 2. Reboot 3. Actual results: NetworkManager is not started correctly. Expected results: NetworkManager starts and detects the correct network Additional info: If one uses 'service NetworkManager stop' after a reboot, it reports as failed. If NetworkManager is started from a command prompt by typing "NetworkManager", it starts up correctly and detects the appropriate network settings. NOTE: The results are the same no matter what type of network connection is being used. NetworkManager exhibits this problem with both wired and wireless networks.
This problem still exists with the latest FC4 update: [root@windu ~]# rpm -q NetworkManager NetworkManager-0.4-18.FC4 I still can't get an IP address unless "NetworkManager" is started manually as root.
I can't get an IP address even when I start NM as root after startup. The NetworkManagerInfo icon shows a wired connection, but I'm not online. Restarting eth0 via Services restores the connection. Also, when I unplug the cable to test NM's wireless, the icon disappears and again I have no connection. NetworkManager-0.4-18.FC4
This bug is old and crufty. I no longer have problems with NM. If someone else has issues, please open a new bug.