On Wed, Nov 17, 2010 at 11:59:12AM +0100, Sascha Silbe wrote: > As explained on the ticket, the bug is in some other component > (probably python-xpcom), not Browse. I'm leaving the ticket open > because it affects Browse pretty badly (risk of data loss),
Session data loss, I presume? Not a biggy, in my opinion. > but I'm afraid we can't do anything about it on the Browse side. I agree, short of rejecting that URL or adding a checkpoint and segmentation fault handler that re-execs, that Sugar can't handle this in Browse. The origin of the failure should be tracked down and fixed though. Is that something you'd like to do, Esteban? -- James Cameron http://quozl.linux.org.au/ _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel