#10016 LOW 1.5-sof: os109 -- Icon in Frame did not have session associated with it

[Zarro Boogs per Child]

#10016: os109 -- Icon in Frame did not have session associated with it
--------------------------------+-------------------------------------------
           Reporter:  mikus     |       Owner:  dsd                              
               Type:  defect    |      Status:  new                              
           Priority:  low       |   Milestone:  1.5-software-later               
          Component:  sugar     |     Version:  Development build as of this date
         Resolution:            |    Keywords:                                   
        Next_action:  diagnose  |    Verified:  0                                
Deployment_affected:            |   Blockedby:                                   
           Blocking:            |  
--------------------------------+-------------------------------------------

Comment(by mikus):

 Replying to [comment:1 Quozl]:
 > Tested on os109, and was unable to reproduce.  Have you a reliable way
 to reproduce this?

 Occasionally on my XO-1.5 system (perhaps I'm paying more attention when
 the system has just started) random things which would normally occur
 rapidly - instead involve a perceptible time lapse.

 If I remember correctly, this was one of those occasions.  When Sugar
 startup draws Home View, first the "me icon" gets shown, then the ring,
 finally the "Journal icon".  When this time I clicked on the "Terminal
 icon" in the ring, there was no feedback - and by reflex I happened to
 click a second time.  Only then did I notice the "Journal icon" being
 drawn, followed by the screen itself changing to show Terminal being
 launched.  Apparently there happened to be a time lapse (between the
 showing of the ring, and the showing ot the "Journal icon") long enough
 for me to click twice on the "Terminal icon".

 Just now I tried to reproduce the situation by double-clicking on the
 "Terminal icon" as soon as the ring got drawn - but now the system did not
 exhibit any time lapse - and the ring got replaced rapidly enough that the
 second part of my double-click did NOT get interpreted as another request
 for Terminal.  So no -- I don't have a reliable way to reproduce this
 problem.

 [When the situation that I describe in this ticket occurred, I went on
 working (in the Terminal session that was launched) without realizing that
 anything unusual had happened.  It was only when I brought up Frame that I
 noticed the second "icon for Terminal" still pulsing in Frame.]

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