On Mon, Apr 02, 2012 at 10:18:57AM +0200, Michael Biebl wrote: > As this seems to be a regression between 0.9.2 and 0.9.4, could you run > git bisect on > git://anongit.freedesktop.org/NetworkManager/NetworkManager > to find the faulty commit.
Bisect blames the following commit (looks plausible to me):
commit 762df85234e7a042a2a5d31053e6cc273ae3e2ec
Author: Dan Williams <d...@redhat.com>
Date: Wed Mar 21 12:37:39 2012 -0500
libnm-glib: ensure bindings-created objects work as expected (rh #802536)
Bindings (like GObject Introspection) almost always create objects
using g_object_new() by default and don't use our helper functions
like nm_client_new(). Thus we need to make sure that if the
object is created in that way, any property accesses or functions
that return properties ensure that the object is fully initialized,
which is what the _new() functions were supposed to do. In one
case in NMClient that was missing (getting active connections)
and wasn't happening at all in NMRemoteSettings, which are our two
entry points into libnm-glib.
This allows this python+GI sequence to return the expected active
connection list:
from gi.repository import NMClient
nmclient = NMClient.Client(dbus_path='/org/freedesktop/NetworkManager')
active = nmclient.get_active_connections()
print(active)
where previously it returned an empty list because the NMClient
wasn't fully initialized by the time nm_client_get_active_connections()
was called.
--
Antti-Juhani Kaijanaho, Jyväskylä, Finland
http://antti-juhani.kaijanaho.fi/newblog/
signature.asc
Description: Digital signature
