Tomeu, Following code traces of ListConnections from the NMSettings class within Network.py, I've come across the following sequence of calls from NM's code: NetworkManager.c's main function calls nm-manager-get (from nm-manager.c). Within nm-mannager-get the function initial_get_connections gets called. I think it is this the function we are looking for since it invokes other functions (query_connections and poke_system_settings_daemon_cb) that call the ListConnections through the d-bus (dbus_gproxy_begin_call()). So effectively I think that ListConnections is the one NM calls at startup. Hope I helped. Cheers <div class="gmail_quote">2010/9/8 Tomeu Vizoso <<a href="mailto:tomeu@sugarlabs.org">tomeu@sugarlabs.org</a>> <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On Wed, Sep 8, 2010 at 13:42, Franco Miceli <<a href="mailto:fmiceli@plan.ceibal.edu.uy">fmiceli@plan.ceibal.edu.uy</a>> wrote: > For what I've been able to see load_wifi_connections collects all wifi > connections from /home/olpc/.sugar/default/nm/connections.cfg. This function > gets called by load_connections who gets called by get_settings. > > I think that the class NMSettings is where sugar communicates this to NM, > but I don't seem to find a "main loop" that I can follow in order to > determine what happens when the process starts for the first time. > > Could it be that this first "connection culling" is not provided by Sugar, > but in fact by other entity? > > Sorry that I can't be of much help, but I'm very new to python and am still > trying to understand some of the basics. > > Please tell me what I can do to help in solving this, since I've made > changes in the autoconnection feature for the XO in NM, and in order to get > the algorithms working well I need to get reliable data of the favourite > connections. So I'm very interested in getting this solved. </div>Hi Franco, I'm not familiar with this part of Sugar, but if you can check if this is the method that NM calls at startup to retrieve the available connections, we may get a step closer: <a href="http://git.sugarlabs.org/projects/sugar/repos/nops/blobs/master/src/jarabe/model/network.py#line354" target="_blank">http://git.sugarlabs.org/projects/sugar/repos/nops/blobs/master/src/jarabe/model/network.py#line354</a> Regards, Tomeu <div class="im"> > Thanks for everything. > > Cheers > > 2010/9/8 Sugar Labs Bugs <<a href="mailto:bugtracker-noreply@sugarlabs.org">bugtracker-noreply@sugarlabs.org</a>> >> >> #2295: Sugar 0.88 [Dextrose] not reporting all favourite connections to >> NetworkManager at startup >> >> ------------------------------------------+--------------------------------- >> Reporter: fmiceli | Owner: tomeu >> Type: defect | Status: new >> Priority: Unspecified by Maintainer | Milestone: Unspecified by >> Release Team >> Component: sugar | Version: 0.88.x >> Severity: Minor | Keywords: >> Distribution: Dextrose | Status_field: Unconfirmed >> >> ------------------------------------------+--------------------------------- >> >> Comment(by tomeu): >> >> Hi Franco, have you found the place in Sugar that provides that single >> connection to NM? >> >> -- >> Ticket URL: <<a href="http://bugs.sugarlabs.org/ticket/2295#comment:2" target="_blank">http://bugs.sugarlabs.org/ticket/2295#comment:2</a>> >> Sugar Labs <<a href="http://sugarlabs.org/" target="_blank">http://sugarlabs.org/</a>> >> Sugar Labs bug tracking system > > > > -- > Ing. Franco Miceli > CITS - Plan Ceibal - Investigación & Desarrollo > Av. Italia 6201 - Montevideo, Uruguay > CP: 11500 > Tel: (598 2) 601 5773 int.: 2227 > </div>> _______________________________________________ > Sugar-devel mailing list > <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> > <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > > </blockquote></div> -- Ing. Franco Miceli CITS - Plan Ceibal - Investigación & Desarrollo Av. Italia 6201 - Montevideo, Uruguay CP: 11500 Tel: (598 2) 601 5773 int.: 2227