Bug 196506

Sorry about this, I omitted release#

Version-Release number of selected component (if applicable):
0.6.0  

 -> Release #3

on a 32-bit (i386) machine

Can you update to the latest NetworkManager included in Fedora Core 5 Updates? 
It should be 0.6.3 or later.

I have the same problem using Fedora 6 (NetworkManager-0.6.5-7.fc7.)

I have configured my system to turn on my wireless connection when booting
(ifcfg-wlan0.)  If I start this interface using "ifup wlan0," then the interface
is brought up properly.  But, if I execute "NetworkManager start" then the
interface is brought down.

I've noticed that if I restart the interface after starting NetworkManager, then
the nm-applet does not recognize this existing connection.

It seems that NetworkManager is not compatible with some common configurations.
 The reason I start my wireless connection on boot is that I use Kerberos to
authenticate.  Requiring that a user logs in before the network interface is
brought up presents a catch-22 for network-based authentication.  Note that
"System-wide Configuration" is a target of NetworkManager 0.7, see
http://live.gnome.org/NetworkManagerToDo.

Fedora Core 6 is no longer maintained. Is this bug still present in Fedora 7 or
Fedora 8?

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

This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

This really ought to be fixed by [1]. I am presently reviewing Fedora 12 Alpha and will provide feedback.

[1] https://fedoraproject.org/wiki/Features/NetworkManagerSystemConnections