Re: Serious side effect of #6299 (silencing salut so gabble can connect)

2008-02-18 Thread Ricardo Carrano
(...). We should therefore be OK. That' s good to know. We need someone at 1cc to test (...). I'm not based at 1CC and don't have enough XOs for a meaningful test.. Since I am not going to Cambridge until next week, maybe someone else could run this tests. Let me clarify how Presence

Re: Serious side effect of #6299 (silencing salut so gabble can connect)

2008-02-17 Thread David Woodhouse
On Thu, 2008-02-14 at 17:56 -0200, Ricardo Carrano wrote: If you don't turn many XOs on at the same time, you won't have salut preventing gabble to work. My fear is that we are complicating things unnecessarily. But we _do_ turn on many XOs at the same time. Hell, we've seen one teacher

Re: Serious side effect of #6299 (silencing salut so gabble can connect)

2008-02-17 Thread Ricardo Carrano
On Thu, 2008-02-14 at 17:56 -0200, Ricardo Carrano wrote: If you don't turn many XOs on at the same time, you won't have salut preventing gabble to work. My fear is that we are complicating things unnecessarily. But we _do_ turn on many XOs at the same time. Hell, we've seen one teacher

Re: Serious side effect of #6299 (silencing salut so gabble can connect)

2008-02-17 Thread Morgan Collett
Ricardo Carrano wrote: Two premises (that need confirmation) 1 - It seems that running neither of two (salut and gabble) brings us some serious troubles (for now, at least). In case you missed some of the mails, it turned out only Pippy needed fixing in the short term, and that's now done as

Re: Serious side effect of #6299 (silencing salut so gabble can connect)

2008-02-15 Thread John Gilmore
Many activities are calling PS get_preferred_connection() ... However, during the period when we stop salut to let gabble try to connect, this call fails as there is no running plugin in PS. If an activity is launched during this time ... crash with a gray screen. This affects:

Re: Serious side effect of #6299 (silencing salut so gabble can connect)

2008-02-15 Thread Morgan Collett
Hi John Your points are valid. If we weren't in RC phase this would have been a non-issue to fix the activities. It turns out the all the activities (except Pippy) were defensively coded enough to not crash with this particular failure - despite there being an open bug about this failure being

Re: Serious side effect of #6299 (silencing salut so gabble can connect)

2008-02-15 Thread Dafydd Harries
Ar 14/02/2008 am 12:19, ysgrifennodd John Watlington: On Feb 14, 2008, at 11:52 AM, Jim Gettys wrote: On Thu, 2008-02-14 at 16:58 +0200, Morgan Collett wrote: We're testing patches to Presence Service to not start salut (or stop it) for a while to give gabble a chance to connect to

Re: Serious side effect of #6299 (silencing salut so gabble can connect)

2008-02-15 Thread Dafydd Harries
Ar 15/02/2008 am 00:09, ysgrifennodd John Gilmore: Many activities are calling PS get_preferred_connection() ... However, during the period when we stop salut to let gabble try to connect, this call fails as there is no running plugin in PS. If an activity is launched during this time

Re: Serious side effect of #6299 (silencing salut so gabble can connect)

2008-02-15 Thread Morgan Collett
Dafydd Harries wrote: There is still a problem there: when you hit the Share button, there might not be a connection that you can use for collaboration. The activity can tell that this is the case, but can't tell when sharing does become available. Ideally, we would enable and disable the

Re: Serious side effect of #6299 (silencing salut so gabble can connect)

2008-02-15 Thread Morgan Collett
Morgan Collett wrote: After looking through the code for these activities I tried them all on build 691, with neither gabble nor salut running - the best way to reproduce expected behaviour without a schoolserver. (To reproduce, kill telepathy-gabble if it's running, then kill

Re: Serious side effect of #6299 (silencing salut so gabble can connect)

2008-02-15 Thread Chris Ball
Hi, Only Pippy actually crashes - it fails to launch completely. Logged #6475 for Pippy, with a minimal patch attached. Applied, thanks. I've pushed a Pippy-19.xo release to Joyride. - Chris. -- Chris Ball [EMAIL PROTECTED] ___ Devel

Re: Serious side effect of #6299 (silencing salut so gabble can connect)

2008-02-15 Thread John Gilmore
Morgan, thank you for the detailed response. Also the two kids sitting under a tree somewhere scenario must Just Work. Absolutely. But ordinary Internet access doesn't work in Mongolia, and probably isn't going to work in update.1. So, everything will work eventually, when all bugs are fixed,

Re: Serious side effect of #6299 (silencing salut so gabble can connect)

2008-02-14 Thread Benjamin M. Schwartz
On Thu, 2008-02-14 at 16:58 +0200, Morgan Collett wrote: We're testing patches to Presence Service to not start salut (or stop it) for a while to give gabble a chance to connect to the schoolserver. (a) Touch all these activities now and port them to the newer cleaner API offered by PS/Sugar

Re: Serious side effect of #6299 (silencing salut so gabble can connect)

2008-02-14 Thread Ricardo Carrano
(e) make salut less chatty during this period (instead of stopping it). But I don't know if this is possible or how to do it. So it maybe not a valid suggestion. But ... I think we have a time sensitive problem. Salut clogs the network if there are many XOs running it. So, if you think of a

Re: Serious side effect of #6299 (silencing salut so gabble can connect)

2008-02-14 Thread Morgan Collett
Jim Gettys wrote: On Thu, 2008-02-14 at 16:58 +0200, Morgan Collett wrote: However, during the period when we stop salut to let gabble try to connect, this call fails as there is no running plugin in PS. If an activity is launched during this time (and there's no particular UI to show this

Re: Serious side effect of #6299 (silencing salut so gabble can connect)

2008-02-14 Thread Morgan Collett
John Watlington wrote: On Feb 14, 2008, at 11:52 AM, Jim Gettys wrote: Let me ask a different question: what happens to activities already running which are running shared? Are they going to fail? Presumably, yes It sounds like any activity trying to share until either gable connect

Re: Serious side effect of #6299 (silencing salut so gabble can connect)

2008-02-14 Thread Morgan Collett
Morgan Collett wrote: Many activities are calling PS get_preferred_connection() to interact directly with the appropriate Telepathy Connection Manager, which was required in the past before we expanded Presence Service's management of setting up channels for activities. However, during the

Re: Serious side effect of #6299 (silencing salut so gabble can connect)

2008-02-14 Thread Ricardo Carrano
I am not sure I was clear. I meant: maybe it is not necessary to turn it (salut) off _while_ trying to connect to gabble. If connected to gabble, then stop salut. Wouldn't this simplify matters? On Thu, Feb 14, 2008 at 3:44 PM, Ricardo Carrano [EMAIL PROTECTED] wrote: (e) make salut less chatty

Re: Serious side effect of #6299 (silencing salut so gabble can connect)

2008-02-14 Thread Ricardo Carrano
John, I am sure 20 laptops will melt down a channel currently. But in this case, the 20 are already turned on and running salut, right? My point is: If you turn on one laptop running salut (it is the only one turned on for a while) can it connect to a school server (even while running salut)? If

Re: Serious side effect of #6299 (silencing salut so gabble can connect)

2008-02-14 Thread John Watlington
Ricardo, That is the current situation, and the chatter generated by Salut multiplied by mesh multicast really does prevent laptops from connecting through gabble. We did a recent test here where 20 laptops really melted down a single channel. wad On Feb 14, 2008, at 2:39 PM, Ricardo

Re: Serious side effect of #6299 (silencing salut so gabble can connect)

2008-02-14 Thread Jim Gettys
You may be correct; the one other issue we have to look at carefully is Avahi (Salut's) behavior after resume. It is likely that all timeouts have expired, and that as soon as you resume a system, it may be immediately doing mdns traffic. If everyone opens up at the same time, you'd have