#8861 HIGH Not Tri: Activity launch failure does not log error

[Zarro Boogs per Child]

#8861: Activity launch failure does not log error
----------------------+-----------------------------------------------------
   Reporter:  bert    |       Owner:  marco        
       Type:  defect  |      Status:  new          
   Priority:  high    |   Milestone:  Not Triaged  
  Component:  sugar   |     Version:  not specified
 Resolution:          |    Keywords:  polish:8.2.1 
Next_action:  code    |    Verified:  0            
  Blockedby:          |    Blocking:               
----------------------+-----------------------------------------------------
Changes (by mikus):

 * cc: mikus at bga.com (added)


Comment:

 Replying to [ticket:8861 bert]:
 > To test, change the exec line in some activity.info file to a non-
 existent program. An error should be logged when trying to launch the
 activity.

 The above is a complicated thing to test.  I changed the exec line in
 X.activity/activity/activity.info to invoke foobar.  With /etc/olpc-
 security present, when I went to Home View and clicked on the icon for 'X'
 - 'X' launched normally.  I'll assume that "what to launch" is cached in
 the activity registry -- so for a change to become effective, the registry
 needs to be rebuilt.  The easiest way to do that with current versions is
 to reboot the XO.

 [[BR]]After the reboot:

  * With /etc/olpc-security present, 'X' did not launch, and the log left
 behind gave "no such module" as the reason.

  * With /etc/olpc-security absent, 'X' did not launch, and the log left
 behind was of zero length (meaning the user could not learn what went
 wrong).

-- 
Ticket URL: <http://dev.laptop.org/ticket/8861#comment:1>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system