#9974 NORM Not Tri: Read fails on start

[Zarro Boogs per Child]

#9974: Read fails on start
-------------------------------------+--------------------------------------
           Reporter:  Quozl          |       Owner:  sayamindu                         
               Type:  defect         |      Status:  new                               
           Priority:  normal         |   Milestone:  Not Triaged                       
          Component:  read-activity  |     Version:  1.5 Software Build os64 aka 10.1.0
         Resolution:                 |    Keywords:  os64 os105                        
        Next_action:  diagnose       |    Verified:  0                                 
Deployment_affected:                 |   Blockedby:                                    
           Blocking:                 |  
-------------------------------------+--------------------------------------

Comment(by mikus):

 While Quozl is correct that readtopbar.py does not define "logging", I
 believe he encountered this problem because accessing the property
 'battery.charge.level.percentage' on the device object 'battery' (as
 identified by Hal) had failed -- and it was this failure that triggered
 the logging attempt.  A look ought to be taken at why the 'battery'
 information was not available.

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