Re: [Sugar-devel] #2295 UNSP: Sugar 0.88 [Dextrose] not reporting all favourite connections to NetworkManager at startup
On Fri, Sep 10, 2010 at 16:52, Franco Miceli fmic...@plan.ceibal.edu.uy wrote: Effectively by debugging both Sugar and NM I found that ListConnections shows all of the favourite connections on connetions.cfg -Double checked within sugar and in NM- but then NM doesn't pass them to real_get_best_autoconnection. So It's NM's fault, and doesn't involve Sugar. I'll report this to NM list and open a ticket in their track. Thanks for all your efforts to try to narrow this down. Nice work, good luck on the other side! Regards, Tomeu Cheers 2010/9/9 James Cameron qu...@laptop.org On Thu, Sep 09, 2010 at 10:26:40AM +0200, Tomeu Vizoso wrote: If anybody wants to reproduce James' tests, I would recommend redirecting dbus-monitor to a file and filtering afterwards the unwanted events. Yes, that's an alternate method, but it doesn't prove execution of code in Sugar in response to events. Instrumenting Sugar is fairly easy, although it does require a restart. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Ing. Franco Miceli CITS - Plan Ceibal - Investigación Desarrollo Av. Italia 6201 - Montevideo, Uruguay CP: 11500 Tel: (598 2) 601 5773 int.: 2227 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] #2295 UNSP: Sugar 0.88 [Dextrose] not reporting all favourite connections to NetworkManager at startup
On 09/10/2010 04:52 PM, Franco Miceli wrote: Effectively by debugging both Sugar and NM I found that ListConnections shows all of the favourite connections on connetions.cfg -Double checked within sugar and in NM- but then NM doesn't pass them to real_get_best_autoconnection. So It's NM's fault, and doesn't involve Sugar. I'll report this to NM list and open a ticket in their track. Thanks for all your efforts to try to narrow this down. Cheers Hi Franco, thank you for going as well where it hurts and debugging the issue so thoroughly. I have seen that you already contributed to our upstream NM. Dan and the other guys at NM are very responsive from my experiences and therefore I am positive you will be able to upstream this just fine. Please, keep us posted :) Thanks for this, as working with our upstreams is a very important part to make Sugar an even better and more stable platform. Regards, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] #2295 UNSP: Sugar 0.88 [Dextrose] not reporting all favourite connections to NetworkManager at startup
Effectively by debugging both Sugar and NM I found that ListConnections shows all of the favourite connections on connetions.cfg -Double checked within sugar and in NM- but then NM doesn't pass them to real_get_best_autoconnection. So It's NM's fault, and doesn't involve Sugar. I'll report this to NM list and open a ticket in their track. Thanks for all your efforts to try to narrow this down. Cheers 2010/9/9 James Cameron qu...@laptop.org On Thu, Sep 09, 2010 at 10:26:40AM +0200, Tomeu Vizoso wrote: If anybody wants to reproduce James' tests, I would recommend redirecting dbus-monitor to a file and filtering afterwards the unwanted events. Yes, that's an alternate method, but it doesn't prove execution of code in Sugar in response to events. Instrumenting Sugar is fairly easy, although it does require a restart. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Ing. Franco Miceli CITS - Plan Ceibal - Investigación Desarrollo Av. Italia 6201 - Montevideo, Uruguay CP: 11500 Tel: (598 2) 601 5773 int.: 2227 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] #2295 UNSP: Sugar 0.88 [Dextrose] not reporting all favourite connections to NetworkManager at startup
On Thu, Sep 9, 2010 at 02:33, James Cameron qu...@laptop.org wrote: On Wed, Sep 08, 2010 at 06:53:24PM +0200, Tomeu Vizoso wrote: You mentioned that NM is only considering one connection, but if you can check that Sugar returns alls of them in ListConnections, why is NM only taking one of them? I agree. I don't see evidence on Sugar side that only one connection is being requested. On Sugar 0.84 traced NewConnection, ListConnections and GetSettings using logging, and the log shows: If anybody wants to reproduce James' tests, I would recommend redirecting dbus-monitor to a file and filtering afterwards the unwanted events. And you can make diagrams out of it if you want: http://willthompson.co.uk/bustle/ http://alban.apinc.org/blog/2008/03/08/99-how-to-make-a-diagram-from-dbus-monitor-logs/ Regards, Tomeu 1283991592.492549 ERROR root: NewConnection '/org/freedesktop/NetworkManagerSettings/0' 1283991592.499109 ERROR root: NewConnection '/org/freedesktop/NetworkManagerSettings/1' 1283991592.569510 ERROR root: ListConnections [jarabe.model.network.NMSettingsConnection at /org/freedesktop/NetworkManagerSettings/1 at 0x99f352c, jarabe.model.network.NMSettingsConnection at /org/freedesktop/NetworkManagerSettings/0 at 0x99f346c] 1283991592.574368 ERROR root: GetSettings '/org/freedesktop/NetworkManagerSettings/0' 1283991592.597896 ERROR root: GetSettings '/org/freedesktop/NetworkManagerSettings/1' 1283991592.615200 ERROR root: GetSettings '/org/freedesktop/NetworkManagerSettings/1' 1283991592.620522 ERROR root: GetSettings '/org/freedesktop/NetworkManagerSettings/0' The above was on build os852, with only one connections.cfg entry, with no mesh or ad-hoc support enabled. There is only one access point powered on, and I'm 10km from the next nearest. I don't understand why there are two NewConnection signals. I think the extra NewConnection signal might have to do with the GSM support. If I discard network history, so that there is no connection for wireless, what the trace shows is: 1283991817.029766 ERROR root: NewConnection '/org/freedesktop/NetworkManagerSettings/0' 1283991817.101088 ERROR root: ListConnections [jarabe.model.network.NMSettingsConnection at /org/freedesktop/NetworkManagerSettings/0 at 0x88743ec] 1283991817.104933 ERROR root: GetSettings '/org/freedesktop/NetworkManagerSettings/0' 1283991817.122063 ERROR root: GetSettings '/org/freedesktop/NetworkManagerSettings/0' Still, it is odd that NetworkManager calls GetSettings method twice, and NetworkManager calls ListConnections only once *after* Sugar has provided the two NewConnection signals. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] #2295 UNSP: Sugar 0.88 [Dextrose] not reporting all favourite connections to NetworkManager at startup
On Thu, Sep 09, 2010 at 10:26:40AM +0200, Tomeu Vizoso wrote: If anybody wants to reproduce James' tests, I would recommend redirecting dbus-monitor to a file and filtering afterwards the unwanted events. Yes, that's an alternate method, but it doesn't prove execution of code in Sugar in response to events. Instrumenting Sugar is fairly easy, although it does require a restart. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] #2295 UNSP: Sugar 0.88 [Dextrose] not reporting all favourite connections to NetworkManager at startup
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. Thanks for everything. Cheers 2010/9/8 Sugar Labs Bugs bugtracker-nore...@sugarlabs.org #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: http://bugs.sugarlabs.org/ticket/2295#comment:2 Sugar Labs http://sugarlabs.org/ 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 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] #2295 UNSP: Sugar 0.88 [Dextrose] not reporting all favourite connections to NetworkManager at startup
On Wed, Sep 8, 2010 at 13:42, Franco Miceli fmic...@plan.ceibal.edu.uy 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. 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: http://git.sugarlabs.org/projects/sugar/repos/nops/blobs/master/src/jarabe/model/network.py#line354 Regards, Tomeu Thanks for everything. Cheers 2010/9/8 Sugar Labs Bugs bugtracker-nore...@sugarlabs.org #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: http://bugs.sugarlabs.org/ticket/2295#comment:2 Sugar Labs http://sugarlabs.org/ 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 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] #2295 UNSP: Sugar 0.88 [Dextrose] not reporting all favourite connections to NetworkManager at startup
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 2010/9/8 Tomeu Vizoso to...@sugarlabs.org On Wed, Sep 8, 2010 at 13:42, Franco Miceli fmic...@plan.ceibal.edu.uy 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. 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: http://git.sugarlabs.org/projects/sugar/repos/nops/blobs/master/src/jarabe/model/network.py#line354 Regards, Tomeu Thanks for everything. Cheers 2010/9/8 Sugar Labs Bugs bugtracker-nore...@sugarlabs.org #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: http://bugs.sugarlabs.org/ticket/2295#comment:2 Sugar Labs http://sugarlabs.org/ 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 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Ing. Franco Miceli CITS - Plan Ceibal - Investigación Desarrollo Av. Italia 6201 - Montevideo, Uruguay CP: 11500 Tel: (598 2) 601 5773 int.: 2227 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] #2295 UNSP: Sugar 0.88 [Dextrose] not reporting all favourite connections to NetworkManager at startup
On Wed, Sep 8, 2010 at 18:34, Franco Miceli fmic...@plan.ceibal.edu.uy wrote: 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. You mentioned that NM is only considering one connection, but if you can check that Sugar returns alls of them in ListConnections, why is NM only taking one of them? Regards, Tomeu Hope I helped. Cheers 2010/9/8 Tomeu Vizoso to...@sugarlabs.org On Wed, Sep 8, 2010 at 13:42, Franco Miceli fmic...@plan.ceibal.edu.uy 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. 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: http://git.sugarlabs.org/projects/sugar/repos/nops/blobs/master/src/jarabe/model/network.py#line354 Regards, Tomeu Thanks for everything. Cheers 2010/9/8 Sugar Labs Bugs bugtracker-nore...@sugarlabs.org #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: http://bugs.sugarlabs.org/ticket/2295#comment:2 Sugar Labs http://sugarlabs.org/ 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 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Ing. Franco Miceli CITS - Plan Ceibal - Investigación Desarrollo Av. Italia 6201 - Montevideo, Uruguay CP: 11500 Tel: (598 2) 601 5773 int.: 2227 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] #2295 UNSP: Sugar 0.88 [Dextrose] not reporting all favourite connections to NetworkManager at startup
On Wed, Sep 08, 2010 at 06:53:24PM +0200, Tomeu Vizoso wrote: You mentioned that NM is only considering one connection, but if you can check that Sugar returns alls of them in ListConnections, why is NM only taking one of them? I agree. I don't see evidence on Sugar side that only one connection is being requested. On Sugar 0.84 traced NewConnection, ListConnections and GetSettings using logging, and the log shows: 1283991592.492549 ERROR root: NewConnection '/org/freedesktop/NetworkManagerSettings/0' 1283991592.499109 ERROR root: NewConnection '/org/freedesktop/NetworkManagerSettings/1' 1283991592.569510 ERROR root: ListConnections [jarabe.model.network.NMSettingsConnection at /org/freedesktop/NetworkManagerSettings/1 at 0x99f352c, jarabe.model.network.NMSettingsConnection at /org/freedesktop/NetworkManagerSettings/0 at 0x99f346c] 1283991592.574368 ERROR root: GetSettings '/org/freedesktop/NetworkManagerSettings/0' 1283991592.597896 ERROR root: GetSettings '/org/freedesktop/NetworkManagerSettings/1' 1283991592.615200 ERROR root: GetSettings '/org/freedesktop/NetworkManagerSettings/1' 1283991592.620522 ERROR root: GetSettings '/org/freedesktop/NetworkManagerSettings/0' The above was on build os852, with only one connections.cfg entry, with no mesh or ad-hoc support enabled. There is only one access point powered on, and I'm 10km from the next nearest. I don't understand why there are two NewConnection signals. I think the extra NewConnection signal might have to do with the GSM support. If I discard network history, so that there is no connection for wireless, what the trace shows is: 1283991817.029766 ERROR root: NewConnection '/org/freedesktop/NetworkManagerSettings/0' 1283991817.101088 ERROR root: ListConnections [jarabe.model.network.NMSettingsConnection at /org/freedesktop/NetworkManagerSettings/0 at 0x88743ec] 1283991817.104933 ERROR root: GetSettings '/org/freedesktop/NetworkManagerSettings/0' 1283991817.122063 ERROR root: GetSettings '/org/freedesktop/NetworkManagerSettings/0' Still, it is odd that NetworkManager calls GetSettings method twice, and NetworkManager calls ListConnections only once *after* Sugar has provided the two NewConnection signals. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
