[sugar] How to try TamTam - noob questions (sorry!)

[imm]

On 24 Aug 2007, at 1:12, Nathana?lL?caud? wrote:

> Could you check both TamTam.log and Shell.log in /home/olpc/.sugar/ 
> default/logs
> and see if there is an error ?

Here's a bit of a story. In short, it kinda works, but...
The process I've been using to try and test TamTam goes like this:

- Delete my existing TamTam.activity folder, to remove the previous  
attempt...
- ./sugar-jhbuild update
- ./sugar-jhbuild build
- wait a bit (or a lot, it's rebuildng xulrunner now!)
- meanwhile, cd into my tamtam download folder and git pull the  
latest TamTam
- when the sugar build completes, ./sugar-jhbuild run
- now Alt-0 to the developer console and open a terminal
- in the terminal, cd to my tamtam download folder
- python setup.py dist  (this creates a dist bundle TamTam-35.xo)
- sugar-install-bundle TamTam-35.xo
- exit sugar (to force it to see the new activity installed)
- re-run sugar
- click on the Tam Tam icon

Hey, what do you know - this time it seems to be working, sort of...  
I don't know what I did differently but TamTam has started. Well, I  
have the launcher screen, and there's an annoying clicking coming  
from the speakers.

Select TamTamJam, hit a few keys - yes, I get instrument sounds - but  
still nasty clicking.

Exit TamTam - clicking stops. Restart TamTam. Hmmm, not restarting,  
just pulsing the icon and says "Starting..."
ps seems to show the previous instance is still running?

Alt-0 to the dev console, check the logs:

shell.log has...

1187969863.6804 ERROR - dbus.proxies: Introspect error on  
org.laptop.TamTam:/org/laptop/TamTam: dbus.exceptions.DBusException:  
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible  
causes include: the remote application did not send a reply, the  
message bus security policy blocked the reply, the reply timeout  
expired, or the network connection was broken.
1187969863.6813 DEBUG - dbus.proxies: Executing introspect queue due  
to error
1187969910.5829 DEBUG - root: _key_pressed_cb: 19 8 <alt>0

And TamTam.log has... Oh, that's interesting, the CPU just maxed out  
and sugar is non-responsive...
Kill sugar.
CPU still maxed out... Hmmm, sugar-console is still running and top  
says it is the culprit. Kill it.

Now open the TamTam.log from my .sugar folder...

1187969037.1538 STDOUT - Debug Level 0
1187969037.1549 STDOUT -
1187969037.1553 STDOUT - INFO: loaded TAMTAM_ROOT=/home/devuser/ 
Activities/TamTam.activity
1187969037.1559 STDOUT -
1187969038.9759 DEBUG - root: Creating a jobject.
1187969038.9794 DEBUG - root: datastore.write
1187969039.1377 DEBUG - root: dbus_helpers.create:  
2ec2f62a-9c5e-44ba-8220-22241796dc41
1187969039.1398 DEBUG - root: Written object  
2ec2f62a-9c5e-44ba-8220-22241796dc41 to the datastore.
1187969040.5970 STDERR - /home/Shared/OLPC/sugar-jhbuild/build/lib/ 
python2.5/site-packages/sugar/graphics/window.py:45: GtkWarning:  
gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) || widget- 
 >parent == GTK_WIDGET (container)' failed
   self._vbox.remove(self.toolbox)
1187969040.8883 DEBUG - root: ActivityService.set_active: 1.
1187969059.3447 DEBUG - root: datastore.write
1187969059.3460 DEBUG - root: dbus_helpers.update:  
2ec2f62a-9c5e-44ba-8220-22241796dc41, /tmp/1187969059,  
{'activity_id': dbus.String 
(u'4c102d9485742e68bbfcc79acc3cc175de40f422'), 'title_set_by_user':  
'1', 'ctime': '2007-08-24T16:23:58.976254', 'title': 'TamTam Mini',  
'mtime': '2007-08-24T16:24:19.344986', 'tamtam_subactivity': 'mini',  
'keep': '0', 'icon-color': '#7F00BF,#AC32FF', 'activity':  
'org.laptop.TamTam', 'preview': '', 'mime_type': ''}
1187969059.3481 DEBUG - root: Written object  
2ec2f62a-9c5e-44ba-8220-22241796dc41 to the datastore.
1187969193.3475 DEBUG - root: datastore.write
1187969193.3549 DEBUG - root: dbus_helpers.update:  
2ec2f62a-9c5e-44ba-8220-22241796dc41, /tmp/1187969059,  
{'activity_id': dbus.String 
(u'4c102d9485742e68bbfcc79acc3cc175de40f422'), 'title_set_by_user':  
'1', 'ctime': '2007-08-24T16:23:58.976254', 'title': 'TamTam Mini',  
'mtime': '2007-08-24T16:26:33.347846', 'tamtam_subactivity': 'mini',  
'keep': '0', 'icon-color': '#7F00BF,#AC32FF', 'activity':  
'org.laptop.TamTam', 'preview':  
'iVBORw0KGgoAAAANSUhEUgAAASwAAADhCAIAAAD9Hh/8AAAAA3NCSVQICAjb4U/ 
gAAAgAElEQVR4nOy9d5xdV3Uvvsvp5/ZepldpRqNebck2tnEvGNv

<snip a lot of this...>

+1Gg0CchFIjsLh27Cf1ZG6OPDeB8bbbIsq2mav6f114TttQNobECbXQDyjdUmCV29Vh9IJgY 
GBnZ8HvO3gO16lR/89g6YZvwdECHE9ynQ+9jiV3f8wm5BkqRkOs1wHN9opDCOx+O7IjP6/ 
wEZnyjmF0SdtwAAAABJRU5ErkJggg==', 'mime_type': ''}
1187969193.3623 DEBUG - root: Written object  
2ec2f62a-9c5e-44ba-8220-22241796dc41 to the datastore.
1187969193.5638 DEBUG - root: ActivityService.set_active: 0.
1187969195.0963 DEBUG - root: _cleanup_jobject: removing '/tmp/ 
1187969059'


This seems to be a reproducible effect - TamTam now runs (but is  
clicky). If I stop TamTam I can't restart it.
Attempting to access TamTam.log maxes out sugar-console.

-- 
Ian