On 26 Jan 2012, at 17:10, Dan Williams wrote: > On Thu, 2012-01-26 at 16:52 +0000, David Röthlisberger wrote: >> On 25 Jan 2012, at 22:02, Dan Williams wrote: >>> On Mon, 2012-01-23 at 15:27 -0600, Dan Williams wrote: >>>> On Thu, 2012-01-19 at 19:35 +0000, David Röthlisberger wrote: >>>>> NetworkManager doesn't reply to the method call >>>>> org.freedesktop.NetworkManager.ActivateConnection. >>>>> >>>>> 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. >>> >>> The issue here is that, because it was simpler, the "default wired >>> connection" actually changes it's object path when it's updated. >> >> Thanks for the analysis. In the meantime we can work around this in our >> client by creating a new connection rather than using the existing one. >> How do we tell whether a Connection is the default one? By checking that >> GetSettings()["connection"]["id"] is something like "Auto eth0"? > > When you say default, do you mean the "default wired connection" that NM > automatically creates when the interface has no other connection? (i'll > assume yes). If so, there's really no good way to tell since it's > supposed to look like any other connection. One way to get around this > would be if you start up and there is only one connection defined, and > it's called "Auto eth0" and is DHCP and it is MAC-locked to the wired > device, delete it, and create your own connection called something > different.
Yes, that's exactly what I meant (sorry about the poor wording). :-) Thanks! David Röthlisberger. _______________________________________________ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
