#12593 NORM 13.1.0: Unable to restart XO-4 from Sugar
Zarro Boogs per Child
bugtracker at laptop.org
Mon Mar 11 15:44:02 EDT 2013
#12593: Unable to restart XO-4 from Sugar
--------------------------------+-------------------------------------------
Reporter: wad | Owner: erikos
Type: defect | Status: new
Priority: normal | Milestone: 13.1.0
Component: sugar | Version: Development build as of this date
Resolution: | Keywords: XO-4, restart
Next_action: diagnose | Verified: 0
Deployment_affected: | Blockedby:
Blocking: |
--------------------------------+-------------------------------------------
Comment(by godiard):
I found one way to reliably reproduce this issue:
1) Use two xo-4. In one xo, start Write activity and share it.
2) Join the activity in the other xo.
3) Write something in every xo (collaboration does not work [1]).
4) Close the activity in the xo where started the collaboration, and later
in the other xo.
5) Go to the neighborhood view: if you see a orphan write icon (there are
no activity shared right now), you can continue, if not, try again from
step 1.
6) Try close the sugar session from the menu in the main buddy icon. You
will see the cursor changing for a second to the clock, but sugar will no
close. Restart or shutdown is the same.
Adding log, I found the problem is in the class sugar3.SessionManager.
This class in the method initiate_shutdown call to
SugarExt.Session.initiate_shutdown() (SugarExt.Session is GsmSession
implemented in gsm-session.c) The problem is GsmSession never trigger
shutdown_completed signal.
What is the use of this GsmClient class? Can we ignore if has not closed?
[1] http://bugs.sugarlabs.org/ticket/4436
--
Ticket URL: <http://dev.laptop.org/ticket/12593#comment:8>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list