[Bugs] #1576 HIGH: Kaleidoscope, Breakout, StackAttack crash on relaunch in Sugar 0.84.7 (XO-1/F11)
Sugar Labs Bugs
bugtracker-noreply at sugarlabs.org
Wed Nov 25 09:22:06 EST 2009
#1576: Kaleidoscope, Breakout, StackAttack crash on relaunch in Sugar 0.84.7
(XO-1/F11)
--------------------------+-------------------------------------------------
Reporter: mavrothal | Owner: bert
Type: defect | Status: new
Priority: High | Milestone: Unspecified by Release Team
Component: Etoys | Version: 0.84.x
Severity: Major | Keywords:
Distribution: OLPC | Status_field: New
--------------------------+-------------------------------------------------
Changes (by bert):
* priority: Unspecified by Maintainer => High
* severity: Unspecified => Major
* status_field: Unconfirmed => New
Comment:
Thanks for taking the time to report this. I'm sure others ran into this
too.
The activities don't actually "crash". You just get an annoying error on
resuming. I tried Kaleidoscope. If you click cancel, then okay, then close
the pink notifier, and right click to restore the screen, it is fine.
Analysis: What happens is that on resume, the project is loaded twice.
Once from the activity bundle, and once from the journal. The first load
from the bundle succeeds. The second load from the datastore fails,
because the first load triggered the security sand boxing, and the
datastore delivers the file outside of the Etoys sandbox directory. This
is because F11 does not have Rainbow enabled yet, so Etoys uses its own
sand boxing for security. With Rainbow enabled, both loads do succeed
(which is still wrong but no error gets shown).
Solution: Simplest and safest is to prevent saving anything to the Journal
when exiting such an activity, and also ignore any saved project when
resuming.
I opened an upstream ticket for this:
http://tracker.squeakland.org/browse/SQ-604
You may want to open a downstream ticket at http://dev.laptop.org/
--
Ticket URL: <http://bugs.sugarlabs.org/ticket/1576#comment:1>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system
More information about the Bugs
mailing list