[Trac #1166] UI to kill not responsive activities

[Zarro Boogs per Child]

#1166: UI to kill not responsive activities
--------------------+-------------------------------------------------------
 Reporter:  marco   |        Owner:  Eben    
     Type:  defect  |       Status:  assigned
 Priority:  normal  |    Milestone:  BTest-3 
Component:  sugar   |   Resolution:          
 Keywords:          |  
--------------------+-------------------------------------------------------
Comment (by AlbertCahalan):

 The initial "close" operation might cause the app to query the user. ("Are
 you sure you want to quit?") Even if such behavior might violate some UI
 guideline, it needs to be supported.

 If "not responding" means a failure to respond to X events, then an
 automatic disconnect after 10 seconds is fairly reasonable. This should be
 followed by SIGTERM to the process group, and ultimately SIGKILL after
 another 10 seconds has passed. Note that this could interfere with
 developers trying to debug their shutdown code.

 Supplying a real kill (forced X server disconnect followed by SIGTERM and
 SIGKILL) as a normal menu option is certainly the easy choice. It may even
 be easiest for kids to deal with. The alternatives involve unexpected
 behavior changes based on hidden internal state. If the menu option is
 always there, kids will quickly learn what it does.

 BTW, "kill" is a fine term for the English locale. It's not like "murder".
 Translators can do as they see fit, hopefully including a localized icon.

-- 
Ticket URL: <http://dev.laptop.org/ticket/1166#comment:4>
One Laptop Per Child <http://laptop.org/>