#6014 BLOC 8.2.0 (: Shutdown should sync activities data

[Zarro Boogs per Child]

#6014: Shutdown should sync activities data
-------------------------------+--------------------------------------------
   Reporter:  michael.tiemann  |       Owner:  marco                            
       Type:  defect           |      Status:  new                              
   Priority:  blocker          |   Milestone:  8.2.0 (was Update.2)             
  Component:  sugar            |     Version:  Build 653                        
 Resolution:                   |    Keywords:  relnote 8.2.0:+ joyride-2220:+ r+
Next_action:  finalize         |    Verified:  0                                
  Blockedby:  4877, 7574       |    Blocking:                                   
-------------------------------+--------------------------------------------

Comment(by marco):

 Replying to [comment:23 cscott]:
 > Just so I'm sure I understand this correctly: this ensures that data is
 sync'ed when you shutdown from the home view

 Correct. This does basically the same gnome-session does in GNOME (we
 reuse a lot of that code too).

 > but doesn't make 'shutdown -h now' from the terminal sync data.

 Correct.

 > Could this be fixed by just adding a simple python script to the
 initscripts to invoke 'syncData' on shutdown?

 Not sure. A tricky aspect is that activities can block shutdown, so the
 script would have to deal with it.

 > This might cause us to sync data twice if you shutdown from the home
 view -- is that a problem?

 I'd rather not save twice. It can be expensive for big files (and we don't
 have a dirty flag in activities at the moment).

 > For context, I'm trying to fix #4878 now that the blocker is gone.
 Should I be doing this by making 'shutdown' safe, or should olpc-update
 explicitly call sugar's syncData before it invokes /sbin/shutdown?

 sugar/src/session.py should expose a DBus service (maybe with the same
 interface as GNOME session http://svn.gnome.org/viewvc/gnome-session/trunk
 /gnome-session/org.gnome.SessionManagement.xml?revision=4777&view=markup).
 And I tend to think olpc-update should call the Shutdown method on it
 directly.

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