Sugar Labs - User contributions [en]

BugSquad/Triage Guide/Stock Responses

2010-03-02T16:30:30Z

DanKrejsa: /* The bug report need some logs */

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
{{TOCright}}
=== If the bug is a duplicate ===

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

=== If the bug is a duplicate and need further information ===

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? Thanks in advance!

=== The bug report needs some logs ===

Thanks for taking the time to report this bug. Without logs from the bug it's very hard to determine what caused it. Can you get us logs? Please see http://sugarlabs.org/go/BugSquad/GetLogs for more information on how to do so. Thanks in advance!

=== If the bug is not described well ===

Thanks for taking the time to report this bug. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://sugarlabs.org/go/BugSquad/BugHowto and add a more useful description to this bug.

=== If the bug is in an obsolete version of the application ===

Thanks for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. Sugar developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of Sugar you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of Sugar.
Please feel free to reopen this bug if the problem still occurs with a newer version of Sugar.

=== If the bug is not in Sugar ===

Thanks for taking the time to report this bug. However, this application does not track its bugs in the Sugar tracker. We kindly ask you to report the bug to the application authors.

If the affected third party application has a bug tracking system you should investigate whether a bug for the reported issue is already filed in this system. If it has not been filed yet please do so. Also ensure that both bug reports contain a link to each other.
Thanks in advance!

[[Category:BugSquad]]

Spock

2010-02-28T18:06:51Z

DanKrejsa:

Spock is an XO activity and pygtk application that implements a simple text editor with
an embedded proof verifier. The proof verifier is based on (an older version of) the
[http://sites.google.com/a/ghilbert.org/ghilbert/home Ghilbert] proof language,
with some modest extensions. Ghilbert in turn is inspired by the
[http://www.metamath.org/ Metamath] project.
Spock, Ghilbert, and Metamath can express a wide variety of logics and theories.

The activity could be used as the basis for a course on elementary propositional
or predicate logic (or even set theory), however as yet very little work has been
done to make the activity friendly to children, and introductory materials are not yet
available.

The code is hosted at [http://git.sugarlabs.org/projects/spock].

Spock

2010-02-28T17:38:31Z

DanKrejsa:

Spock is an XO activity and pygtk application that implements a simple text editor with
an embedded proof verifier. The proof verifier is based on the
[http://sites.google.com/a/ghilbert.org/ghilbert/home Ghilbert] proof language,
with some modest extensions. Ghilbert in turn is inspired by the
[http://www.metamath.org/ Metamath] project.
Spock, Ghilbert, and Metamath can express a wide variety of logics and theories.

The activity could be used as the basis for a course on elementary propositional
or predicate logic (or even set theory), however as yet very little work has been
done to make the activity friendly to children, and introductory materials are not yet
available.

The code is hosted at [http://git.sugarlabs.org/projects/spock].

Spock

2010-02-28T17:34:59Z

DanKrejsa: Created page with 'Spock is an XO activity and pygtk application that implements a simple text editor with an embedded proof verifier. The proof verifier is based on the [http://sites.google.com/a…'

User:DanKrejsa

2010-02-28T17:32:22Z

DanKrejsa: Created page with '==Projects== * Spock'

==Projects==

* [[Spock]]

Sugar on a Stick/TODO

2009-08-04T00:46:12Z

DanKrejsa: /* Sticks are dieing a lot - Make sticks more robust */

<noinclude>{{GoogleTrans-en}}{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792}}</noinclude>

==Sugar on a Stick Improve Deployability==

===Make it easier for a teacher or school to customize a spin and then copy it for a hundred kids===

Tickets on this topic:

Red Hat - https://bugzilla.redhat.com/show_bug.cgi?id=448030 - RFE: create a bootable Live USB stick from the running livecd
SugarLabs Ticket 74 - http://dev.sugarlabs.org/ticket/74

''Use Case''
A teacher should be able to create a USB stick, add activities, add some content, change the language, change the jabber server etc. Then create new sticks that reflect these changes but do not copy the name, color or collaboration key.

It would be great if the teacher could use an inexpensive USB hub to burn more then one stick at a time.

===Sticks are dying a lot - Make sticks more robust===

''Failure Modes''

# Gets stuck at Fedora Login
## With liveuser prefilled <br>I was able to repeatably create this failure when I was testing a version of schoolserver.py that had a typo in it.
## With nothing prefilled <br> This error has successfully been replicated by Restarting multiple times.
# Bug in initramfs /init detected. Dropping to a shell. Good luck! bash: no job control in this shell. <br> Stick abuse, like putting it through the washing machine, seems to precipitate this type of failure.
# Freezes during use of an activity. Rebooting on the same computer doesn't help it still freezes on the same activity. One time we rebooted on a different computer and it worked.

We don't know the root causes but we have plenty of theories.

Sticks will always fail. There will always be multiple causes for failure. This problem has to be addressed like a process engineering issue. Is stick failure a major cost in time or money? Find the largest cause of failure. Fix that to improve yield. Is stick failure a major cost in time or money? Find the the remaining largest cause of failure.....

This summer we had probably 10 sticks fail for 35 students. That is a major cost in time and money. The most common unrecoverable failure mode was stuck at Login.

====We need a more robust files system====

It has been shown that if you take a stick that is stuck at login and you copy over a fedora-overlay file from a working stick, the stick will boot again. Thus we are confident that the problem is corruption of the overlay file.

''Next Steps'' - Try some alternate file structures.

# Create a Fedora Full Install USB Stick, restart it a bunch of times and see if it does better. How much space will the Fedora Full Install take?<br>So far its > 4GB http://wiki.sugarlabs.org/go/VMware#Full_Install_with_F11_Net_install_CD_to_USB_Stick
# Create an Open Suse USB Stick, restart it multiple times and see if it fails. How much space does it use?

''Background Links''
Thread from the Fedora Forum: [[http://forums.fedoraforum.org/showthread.php?t=221719]]

Here is an idea for an alternative USB Format: [[http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/USB_format]]

Also see Ticket 907 [[http://dev.sugarlabs.org/ticket/907]]

A 2 GB USB is about $.60 more then a 1GB stick. If we need to compress less to get robustness its ok for us to require a 2GB USB. A 4GB stick is about $2.50 more then a $1GB Stick.

''Theories that have evidence against them''

Dave Bauer was able to replicate the failure easily by restarting a Sugar stick. This means its probably not:

* The Bulk Copier, Dave doesn't have one.
* The older slower computers and USB 1 ports we are using at the GPA.

====Sticks are damaged during formatting or burning====

http://wiki.laptop.org/go/How_to_Damage_a_FLASH_Storage_Device [[http://wiki.laptop.org/go/How_to_Damage_a_FLASH_Storage_Device]]

There was a detailed discussion thread back in February at: http://lists.laptop.org/pipermail/devel/2009-February/022987.html

If we understood how to win and we had our own stick creation activity perhaps we would have less failures.

====Sticks are of poor quality====

Here is an explanation of two processes used to create USB sticks: http://www.solutiongrove.com/blogger/2008/09/08/there-are-two-type-of-usb-flash-memory-slc-and-mlc [[http://www.solutiongrove.com/blogger/2008/09/08/there-are-two-type-of-usb-flash-memory-slc-and-mlc]]

====Sticks are being improperly removed====

Yes they are, but its not at all clear to me that that correlates with the sticks that are failing.

====There is a bug around restarting====
It is very common to fail after a restart, the system forgets its supposed to go to Sugar. See ticket 1069 [[http://dev.sugarlabs.org/ticket/1069]]

===Backup and recovery===

Ham and Dave from Solution Grove are making progress on this. You can track progress on ticket 916 [[http://dev.sugarlabs.org/ticket/916]]

===What is a reasonable expectation for the role of the XS in Sugar on a Stick deployments in the next 6 months?===
===Collaboration is unreliable and thus frustrating===
Its working fairly well in the wired network at the GPA lab, but no other use case seem to work reliably.

===Using a CD helper takes a lot of prep time before and after class===
A floppy helper would reduce it. A VM solution might also reduce it.

Tickets
* Ticket 598 Boot Helper Virtual Machine [[http://dev.sugarlabs.org/ticket/598]]
* Ticket 907 change the format we use for the USB stick [[http://dev.sugarlabs.org/ticket/907]]
* Ticket 597 Floppy Boot Helper [[http://dev.sugarlabs.org/ticket/597]]

See also [[Sugar on a Stick/Goals]].

*[[Gardner Pilot Academy#Critical Path Technical Issues]]

This is an the general todo list for SoaS. If you've any ideas or requests, please add them here.

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
| '''Task Name''' || '''Priority''' || '''Status/Notes'''
|-
| solicit USB key donations from companies || 1 || info needed
|-
| allow direct recreation of USB keys (cloning) || 2 || needs testing [http://bugzilla.redhat.com/show_bug.cgi?id=448030]
|-
| add additional activities, if requested || 3 || get them on [http://activities.sugarlabs.org/ a.sl.o]
|-
| work on a keyboard layout control panel || 3 || work in progress [http://dev.sugarlabs.org/ticket/473]
|-
| be able to backup and restore from a School Server || 3 || to be worked out
|-
| support printers, scanners, cameras || 3 || to be worked out
|-
| activity for cloning USB Sticks and .iso files (cloning)|| 3 || to be worked out [http://dev.sugarlabs.org/ticket/74#comment:3]
|}

Here's a list with completed tasks; feel free to move them from the table above.

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
| '''Task Name''' || '''Status/Notes'''
|-
| get SoaS included in [http://fedorahosted.org/liveusb-creator/ liveusb-creator] || done
|-
| create a virtual appliance (builds) || done [http://lists.sugarlabs.org/archive/sugar-devel/2009-March/012747.html] [http://dev.sugarlabs.org/ticket/114]
|-
| release a helper CD for boot from USB || done [http://dev.sugarlabs.org/ticket/265]
|-
| add sample content || done - add more if needed
|-
| fix blockers for release || most important point, check rawhide, as it progresses towards beta
|-
| update remaining RPMs || good progress done so far
|-
| check localization support || done
|-
| get artwork and branding together || done
|-
| change default Browse location || done
|-
|}

[[Category:TODO]]

Development Team/Jhbuild/Fedora

2009-06-20T22:18:07Z

DanKrejsa:

==Supported versions==
Currently Fedora 10 and Fedora 11 should both work. Fedora 10 will be phased out soon.

==Requirements==

A full build using sugar-jhbuild will require about 3 Gig of disk space.

==Prerequisites==

sudo yum -y update
sudo yum -y groupinstall "Development Tools"
sudo yum -y groupinstall "X Software Development"

Some installations may also require

sudo yum -y install redhat-lsb python-devel glib glib-devel glib2-devel dbus-glib-devel \
libxml2-devel popt-devel pygobject2-devel pygtk2-devel

Development Team/Jhbuild/Fedora

2009-06-20T22:12:57Z

DanKrejsa: /* Prerequisites */

Development Team/Jhbuild/Fedora

2009-06-20T22:11:36Z

DanKrejsa: /* Prerequisites */

Development Team/Jhbuild/Fedora

2009-06-20T21:59:53Z

DanKrejsa: /* Prerequisites */

Development Team/Jhbuild/Fedora

2009-06-20T21:52:25Z

DanKrejsa: /* Prerequisites */