<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Jim; I want to my 2 cents to this. Here is a brief history as I remember it: I have done a lot of testing of collaboration using the (default) jabber.sugarlabs.org connection. It is provided by caroline's solutiongrove.com and maintained by Dave Bauer (daveb) . Several months ago the jabber had gadget installed ( I think by tomeu? )In an effort to make  the jabber handle  the large numbers of connections that were swamping the server in 1 to 2 days times , effectively  freezing it up cold. The result is that now it keeps running fine but only serves up 20 (random?)buddies when you make a connection. (You will not get a new  set of  20  buddies if you restart Sugar... ) Also: there are many "ghost" connections littering the jabberserver.  ( on a 0.86 version of sugar you will notice that these "ghosts" have the user color.) They occupy spots that should  be showing new connections. When daveb restarts the jabber this is momentarily cleared up until the loading of new users gets too large. The overall result seems to be a non-functional collaboration neighborhood. It is a sham. This does not appear to be a problem for school-server setups using their own jabber (I assume without gadget loaded) as I have not heard of any complaints about it on the list. Hint: If you are on the same network, you can collaborate if you delete the entry for jabber.sugarlabs.org in the control panel on your sugar entities. Tom Gilliard satellit Jim Simmons wrote: <blockquote cite="mid:abb0965a1001250745j1db6ef94w35ba5c89b35342f2@mail.gmail.com" type="cite"> <pre wrap="">Sascha, I tried a few things on F11 this morning, none of which worked: I tried building sugar-jhbuild on a second Linux user id, and after that running sugar-jhbuild run on two different Linux user ids at the same time with the Jabber server in each set to an empty string. They could not see each other. At some point in that test I started F11's sugar-emulator, which may account for the database error. The sugar-jhbuilds weren't seeing each other before I did that though. The avahi demon looks like it was running. I'll try clearing out the .sugar/default/logs directory and running a test with just sugar-emulators running. F10 still works with no jabber server if both instances run under separate accounts. I'm going to try SUGAR_PROFILE again on F10 tonight to see if that works with two profiles running on the same Linux id. Your suggestion that F10 does not support jabber.sugarlabs.org seems right on the money. The wiki page says that jabber.sugarlabs.org is for those running the very latest Sugar. The idea that jabber.sugarlabs.org only shows 20 users no matter how many are connected also seems to be right, because when I use that server on F11 I see 20 others besides myself on each instance of sugar-emulator I run. The thing is, its always the same 20 users. I guess they never turn their computers off, ever. I'd be a little concerned if a Jabber server could only support 20 concurrent users. When I was a kid class size of 30 kids was not unusual, and our school district was well off. You'd need one Jabber server for each classroom and it wouldn't be enough. I don't think I'll be able to diagnose this with you over IRC, though I wish I could. Between work and my other responsibilities I have very little time to work on Sugar and getting the two of us on the same schedule seems unlikely. I do have something working for now, and I'll document everything I've learned in the book. Thanks, James Simmons On Mon, Jan 25, 2010 at 8:08 AM, Sascha Silbe <a class="moz-txt-link-rfc2396E" href="mailto:sascha-ml-reply-to-2010-1@silbe.org"><sascha-ml-reply-to-2010-1@silbe.org></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">On Mon, Jan 25, 2010 at 07:49:34AM -0600, Jim Simmons wrote: </pre> <blockquote type="cite"> <pre wrap="">The logs are attached from this morning.  Something about Salut crashing. </pre> </blockquote> <pre wrap="">For which installation exactly? F10/F11? Native packages/sugar-jhbuild? Do you use sugar-emulator or run sugar as a native session? datastore.log might contain a clue: DatabaseLockError: Unable to acquire database write lock on /home/jim/.sugar/default/datastore/index: already locked It looks like there's another instance of Sugar already running (as the same user, with the same profile). This might explain the Salut issue as well. If you've got some time you could join #sugar on Freenode and we'll try to debug it interactively. CU Sascha -- <a class="moz-txt-link-freetext" href="http://sascha.silbe.org/">http://sascha.silbe.org/</a> <a class="moz-txt-link-freetext" href="http://www.infra-silbe.de/">http://www.infra-silbe.de/</a> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iQEcBAEBAgAGBQJLXaXVAAoJELpz82VMF3Dax4MH/RL3FhQMKB2ZaIGuLp+hgi00 NV3X5g+COikc5YTYhQ8yDpaJAajtxeMNOOtmSfkEZfjZN6gIwgI6OMDh3WU3/DMY 59mXn1w6BELYNGo6TUMAUEqT7ErxFOfUuWi9e4DUfGkikQiFSA8DvJU/2RprbStP Sq7K1Zc1qUYppy5/8uMM27O4uw55gahXhC53HmE8FEo/K6VPFn1m41UWyHpAwCrC XLg8+grtzdGlMdqR0wUtoYYOOKI5m+hak7kCYDN54UFRwmDXk6LXcQbTyRTVwXwq Dx50y70tQDuPiFH7WGx1ygg2iZOz8RXovYwIRkznqxY5gwEBTo6CixISGZB4Q6c= =QIqH -----END PGP SIGNATURE----- </pre> </blockquote> <pre wrap="">_______________________________________________ Sugar-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </pre> </blockquote> </body> </html>