I think I've figured out some interesting interactions between .gconf and NetworkManager. If anyone has any insight why, I'd be glad to hear it, but for the moment I plan to avoid Evolution, at least from a backup archive.
I am switching back to Fedora after being on Ubuntu for one release (10.04 doesn't do modesetting on my nVidia 6150 Go graphics). While in Ubuntu, I started using Evolution as an email/calendar/contacts tool, and that worked pretty well. When I decided to change to F13, I told Evolution to make a backup archive from which to restore on my new system. I picked Fedora 13 KDE, which I figure shouldn't be an issue.
When I restored from the archive (a tar.gz), everything seemed to be OK. On restarting, however, NetworkManager refused to manage any of my devices (wired or wireless). I tried following the directions from other posts, thinking that NM was being controlled by the network daemon. After much pain and re-installing, I think I have it figured out.
The Evolution backup contained a backup of my .gconf from my Ubuntu system. When I restored it, that backup of .gconf was put into the .evolution folder, where I wouldn't expect it. Every time Evolution was run, it would restore that backup to my home directory. Apparently, that .gconf had enough conflicting material to tell NetworkManager to leave my devices unmanaged. I don't know any particulars, but that's what it seems to be. I'm going to be trying out KMail for the time being,
I think this is a fairly limited issue -- if anyone else is migrating from Ubuntu, then maybe it'll be an issue, but I think committed Fedora users should be fine.
---------- Post added at 03:52 PM CDT ---------- Previous post was at 09:44 AM CDT ----------
While I attempted to avoid the problem by not installing Evolution, it turns out that this is not
the root cause of the problem -- only a coincidence on my system. I just got the "Network Unmanaged" behavior without installing Evolution. It turns out that my user's configuration didn't actually have anything to do with it.
The issue is that the state file /var/lib/NetworkManager/NetworkManager.state gets set to have "NetworkingEnabled=false", which quite naturally would disable the networking. (It's a wonder what reading the man pages can teach you!)
This problem seems to arise on the second or third reboot after installing a lot of updates. I installed all the updates for a Fedora 13 KDE install this morning. I rebooted once, and it was fine, so I never made the connection. I'm guessing that some shutdown configuration script got changed after the first restart, so the second restart will shut down NM. If anyone else is running into this issue, just rm the state file and restart the NetworkManager.
I currently don't know what package will cause this issue, so go ahead and use Evolution all you want. It could be that I'm the only one having a problem.