#6484 HIGH Never A: gcompris chess won't run with Rainbow

[Zarro Boogs per Child]

#6484: gcompris chess won't run with Rainbow
----------------------------------+-----------------------------------------
  Reporter:  walter               |       Owner:  mstone        
      Type:  defect               |      Status:  new           
  Priority:  high                 |   Milestone:  Never Assigned
 Component:  gcompris-activities  |     Version:                
Resolution:                       |    Keywords:                
  Verified:  0                    |    Blocking:                
 Blockedby:                       |  
----------------------------------+-----------------------------------------

Comment(by mstone):

 I've only examined the 'chess_computer' activity so far. Here's what I
 found:

 The first sign of trouble is that the activity fails to launch with
 isolation on, and succeeds with isolation off. This means that an
 interaction with Rainbow is clearly to blame, which further means that we
 need to read the activity's log file to see what's going on.

 {{{
 less -R
 /home/olpc/.sugar/default/logs/net.gcompris.chess_computerActivity-1.log
 }}}

 This shows us a colorful traceback originating from Rainbow's
 'check_bundle_id()' contract-check which informs us that Rainbow is
 killing the launch because it doesn't like the '_' in the activity.info's
 service_name field. Arguably Rainbow is enforcing a standard for bundle
 names that is too restrictive. Fortunately, deleting the '_' in the
 service_name field in the activity.info file allows the activity to start.

 The second problem we encounter, now that the activity succeeds in
 launching, is that it expects the gnuchess binary to live at
 /usr/games/gnuchess instead of /usr/bin/gnuchess. Here, we have two
 choices. We can either insert a compatibility symlink:

 {{{
 ln -s /usr/bin/gnuchess /usr/games/gnuchess
 }}}

 or we could modify either the gnuchess RPM or the GCompris activities.

 Either way, we've now got a playable chess game.

 Bruno - how would you like to proceed?

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