[Trac #1125] Activity load time-out issues evident under slow emulation

[Zarro Boogs per Child]

#1125: Activity load time-out issues evident under slow emulation
----------------------+-----------------------------------------------------
 Reporter:  follower  |       Owner:  dcbw     
     Type:  defect    |      Status:  new      
 Priority:  normal    |   Milestone:  Untriaged
Component:  sugar     |    Keywords:           
----------------------+-----------------------------------------------------
 For example, between build 239 and build 303 activity loading slowed
 enough for me (Qemu / 1.6GHz G4 PPC / OS X) that no activities loaded
 successfully. Symptons include messages in
 {{{/home/olpc/.sugar/default/logs/shell.log}}} like this:
 {{{
 DEBUG - Shell.start_activity
 DEBUG - Activity f4a9f5322b49dcc3364a4eca9b13633c0ce1868e
 (org.laptop.ChatActivity) launching...
 DEBUG - Activity f4a9f5322b49dcc3364a4eca9b13633c0ce1868e
 (org.laptop.ChatActivity) launch timed out
 STDERR - Introspect error: 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.

 DEBUG - Couldn't create activity f4a9f5322b49dcc3364a4eca9b13633c0ce1868e
 (org.laptop.ChatActivity): 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.
 ERROR - Model for activity id f4a9f5322b49dcc3364a4eca9b13633c0ce1868e
 does not exist.
 DEBUG - Activity f4a9f5322b49dcc3364a4eca9b13633c0ce1868e
 (org.laptop.ChatActivity) launching...
 DEBUG - Activity f4a9f5322b49dcc3364a4eca9b13633c0ce1868e
 (org.laptop.ChatActivity) finished launching
 }}}

 I discovered two timeouts are being encountered (one in Sugar and the
 other in D-Bus) and wrote up a
 [http://wiki.laptop.org/go/OS_images_for_emulation#Coping_with_Slow work
 around].

 Discussion on IRC with marcopg suggests some potential issues:

  1. Should the Sugar and D-Bus timeouts be changed to be equal?
  1. Should the Sugar timeout be removed and the D-Bus timeout error caught
 instead?
  1. Should the timeout length be increased?
  1. Why does the error from D-Bus ("{{{STDERR - Introspect error}}}") not
 prevent the activity from eventually loading? Is this a bug?

-- 
Ticket URL: <http://dev.laptop.org/ticket/1125>
One Laptop Per Child <http://laptop.org/>