#6640 NORM Never A: Input to Rainbow can trigger an assertion failure

[Zarro Boogs per Child]

#6640: Input to Rainbow can trigger an assertion failure
-----------------------+----------------------------------------------------
  Reporter:  bemasc    |       Owner:  mstone        
      Type:  defect    |      Status:  new           
  Priority:  normal    |   Milestone:  Never Assigned
 Component:  security  |     Version:                
Resolution:            |    Keywords:                
  Verified:  0         |    Blocking:                
 Blockedby:            |  
-----------------------+----------------------------------------------------

Comment(by bert):

 Replying to [comment:1 tomeu]:
 > I'm not sure what's the best solution, but certainly think that the
 error message that appeared in the logs should be much more clear.

 Seconded. Especially since not every developer is familiar with Python
 backtraces.

 Another option might be to silently correct the bad permissions. I have
 seen this problem by novice developers (novice to Linux and OLPC anyway),
 in particular when packaging the .xo on Windows.

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