#9612 NORM 1.5-F11: Abruptly turning off XO-1.5 right after initial boot destroys system

[Zarro Boogs per Child]

#9612: Abruptly turning off XO-1.5 right after initial boot destroys system
------------------------------+---------------------------------------------
           Reporter:  wad     |       Owner:  marco                            
               Type:  defect  |      Status:  reopened                         
           Priority:  normal  |   Milestone:  1.5-F11                          
          Component:  sugar   |     Version:  Development build as of this date
         Resolution:          |    Keywords:                                   
        Next_action:  design  |    Verified:  0                                
Deployment_affected:          |   Blockedby:                                   
           Blocking:          |  
------------------------------+---------------------------------------------
Changes (by Quozl):

  * status:  closed => reopened
  * resolution:  fixed =>


Comment:

 Reopening for Sugar resilience improvement ... kernel has the right to
 generate incomplete or zero-filled files as a result of power failure, and
 as Daniel says there could be other reasons.

 Was able to get it to choke again with os40, the following call trace was
 seen:

 {{{
 Traceback (most recent call last):
   File "/usr/bin/sugar-presence-service", line 24, in <module>
     main.main()
   File "/usr/share/sugar-presence-service/main.py", line 64, in main
     presenceservice.main(test_num, randomize)
   File "/usr/share/sugar-presence-service/presenceservice.py", line 885,
 in main
     ps = PresenceService()
   File "/usr/share/sugar-presence-service/presenceservice.py", line 87, in
 __init__
     self._owner = self._create_owner()
   File "/usr/share/sugar-presence-service/presenceservice.py", line 56, in
 _create_owner
     return ShellOwner(self, self._session_bus)
   File "/usr/share/sugar-presence-service/buddy.py", line 971, in __init__
     'keyid/' + psutils.pubkey_to_keyid(key),
   File "/usr/share/sugar-presence-service/psutils.py", line 82, in
 pubkey_to_keyid
     return sha1(key).hexdigest()
 TypeError: sha1() argument 1 must be string or read-only buffer, not None
 }}}

 resulting in sugar-session not starting.  The name prompt reappears.

 Diagnosis: that jarabe/intro window reappears means that
 profile.is_valid() has returned false.  Manual gconftool-2 queries show
 that /desktop/sugar/user/{nick,color} are properly set.  The key also
 appears to be present; /home/olpc/.sugar/default/owner.key{,.pub} contain
 non-zero data, but it does not look like a key.  Removing these files
 progresses things to the next level of damage:

 {{{
 Traceback (most recent call last):
   File "/usr/bin/datastore-service", line 24, in <module>
     ds = DataStore()
   File "/usr/lib/python2.6/site-packages/carquinyol/datastore.py", line
 57, in __init__
     if layout_manager.get_version() == 0:
   File "/usr/lib/python2.6/site-packages/carquinyol/layoutmanager.py",
 line 49, in get_version
     version = int(open(version_path, 'r').read())
 ValueError: invalid literal for int() with base 10: '/'
 }}}

 Which was caused by the datastore/version file containing uninitialised
 data.

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