Comment 47 for bug 132042

Dan Buch (meatballhat) wrote :

After running NetworkManager in the foreground for a few more days I thought I'd go back to running it via the upstart service. Within a minute of `service network-manager start` I began getting prompted for new network credentials (same old busted behavior.) I kill'd wpa_supplicant to see if the behavior was similar to when I was running NetworkManager in the foreground, but it only made the situation better for 2 minutes at most per restart. Only after stopping the network-manager service and going back to running NetworkManager in the foreground did the situation improve.

Based on the experience of the past week, my next steps will likely be to dig into the NetworkManager source to see if there's anything special going on when the process is daemonized especially wrt wpa_supplicant.