Re: NetworkManager 0.8.6 doesn't reply to ActivateConnection

[Dan Williams <dcbw redhat com>]

On Thu, 2012-01-19 at 19:35 +0000, David Röthlisberger wrote:
> We are using NetworkManager 0.8.6 on a device without the official NM applet,
> so we do all communication with NM over DBus ourselves. If there is no entry in
> the system-connections directory *and* no "no-auto-default" entry in
> NetworkManager.conf, then NetworkManager doesn't reply to the method call
> org.freedesktop.NetworkManager.ActivateConnection.
> 
> NM *does* receive the method call and does apply the configuration, but simply
> doesn't reply; the caller eventually gets a DBus timeout.
> 
> After this first call (which times out), NM has created its configuration file
> in system-connections, and the next call works correctly.
> 
> I can consistently reproduce this behaviour by:
> * killing NM, 
> * removing any "no-auto-default" entry in NetworkManager.conf,
> * removing everything in the system-connections directory; then
> * starting NM
> * and sending NM a series of method calls culminating in ActivateConnection. 

I can reproduce this with a small python program.  Clearly a bug, fixing
it now.

Dan