A followup:

A similar sensekey/ASCII-based csd issues two slightly different error 
messages (with the same run abort):

rainbow-daemon: Fatal IO error 0 (Success) on X server :0.0
or
rainbow-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X 
server :0.0

Sometimes the run returns to Sugar, sometimes not.

The scripting seems to be right, and nearly identical for the two csd's.

Art Hunkins

----- Original Message ----- 
From: "Art Hunkins" 
To: 
Sent: Friday, May 01, 2009 9:28 PM
Subject: [Csnd] sensekey and Sugar (OLPC)


>I have a csd that runs impeccably from the XO console, but fails in Sugar 
>(a Python script is running as an XO project; I've been making progress). 
>I'm fairly certain the problem is sensekey, or the way in which Sugar is 
>(or isn't) dealing with ASCII keystrokes.
>
> The Sugar error occurs precisely at the first ASCII keystroke (prior to 
> that, the run is fine). With the keystroke, the run aborts and exits to 
> Sugar.
>
> The log shows the error message to be:
> rainbow-daemon: Fatal IO error 12 (Cannot allocate memory) on X server 
> :0.0
> then a bit later:
> Csound tidy up: Segmentation fault
>
> What do I need to change?
>
> Art Hunkins
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
> csound"