[Sugar-devel] SunMoonMusic Activity does not open in Mango Lassi

[Art Hunkins]

James,

Thanks both for your well-expressed advice, as well as your continued 
interest in my musical projects. I've recently had several "go's" at git - 
and thanks to your help, did not experience heart failure (it went quite 
well in fact).

I've discovered what was wrong, and so file your suggestions for my next set 
of troubles.

I've been using primarily 1GB USB sticks, which (with Mango especially) 
doesn't leave much extra room (I use the LiveUSB Creator, reserving the 
remainder of the stick's space). The hitch about Mango is that it doesn't 
allow you to delete any activities, *and* once you add some, you can't 
delete *them* either - even though there is an option to do so.

I always load in my six activities, two of which (with sound files) are 7MB 
each. I've apparently always loaded in the big ones prior to SunMoonMusic. 
It seems the stick just runs out of space. If I load SunMoonMusic before the 
others, it opens and runs fine.

I would hope that all distributions would allow for deleting activities, 
*especially* those added by the user. (This seems to be intended; is 
probably a bug in Mango Lassi.) Many previous distros allowed you to delete 
any activity you wanted.

BTW, I enjoyed your tunes, especially the last few. The "fiddle tune" in 
triplets is particularly fetching.

Thanks again -

Art Hunkins

----- Original Message ----- 
From: "James Cameron" <quozl at laptop.org>
To: "Art Hunkins" <abhunkin at uncg.edu>
Cc: <sugar-devel at lists.sugarlabs.org>
Sent: Monday, May 30, 2011 7:54 PM
Subject: Re: [Sugar-devel] SunMoonMusic Activity does not open in Mango 
Lassi


> I've no idea what might be special, the activity looks normal to me, but
> if there is no error log left behind my next step in diagnosis is to
> launch the activity from a Terminal prompt using sugar-launch, then if
> still no output is visible launch it with strace and interpret the
> output.
>
> To launch using sugar-launch, start Terminal, "cd" to the activity
> directory, check the activity bundle id or service name from the
> activity/activity.info file, and then use it like so:
>
> sugar-launch ${NAME}
>
> where ${NAME} os the bundle id or service name, in your case
> org.laptop.SunMoonMusic.
>
> It is unfortunate that this is so complex, but an alternative is:
>
> cd ~/Activities/SunMoonMusic.activity && \
> sugar-launch \
> $(grep bundle_id activity/activity.info | cut -f3 -d' ')
>
> To capture further diagnostic data using strace, add the word strace
> before the word sugar-launch.  You can redirect the output to a file.
>
> cd ~/Activities/SunMoonMusic.activity && \
> strace -o strace.log -f \
> sugar-launch \
> $(grep bundle_id activity/activity.info | cut -f3 -d' ')
>
> I offer to review the output if you still don't see what is causing
> the problem.
>
> -- 
> James Cameron
> http://quozl.linux.org.au/