Testing/Reports/ARM RPi

Sugar on a Raspberry pi is functional, robust and stable, testable by children (in progress) but incomplete.

Test report

Product of the command

   sweets  sdk/sugar:emulator

Raspberry pi, running OS from http://www.raspbian.org/ (pisces image) on a SanDisk 4 GB, class 4, SDHC card.

Sweets, following these instructions Platform_Team/Guide/Sugar_via_Sweets

From my computer

Build: Debian GNU/Linux testing/unstable

Sugar: 0.94.1

All Function keys, F1 to 6, work fine

All Views and avatars seen correctly, without error.

Software Updates fully functional.

Calculate.activity v.40 - Chat.activity v.77 - HorseGame.activity v.4 - IRC.activity v.10 - Log v.29 - Labyrinth.activity v.12 - Maze.activity v.21 - Memorize.activity v.4 - Moon.activity v.14 - Pippy.activity v.49 - SprayPlay.activity v.2 - SugarCommander.activity v.8 - Terminal.activity v.40 - Turtle Art v.149 - TurtleConfusion.activity v.10 -

Fixed Items

Earlier in the process, to fix:

ImportError: No module named vte
ImportError: No module named gst
ImportError: No module named pygame

sudo apt-get install python-vte python-gst0.10 python-pygame

Still to Fix

Surf.activity v.115 Reports, Failed to start.

ImportError: No module named webkit

To fix tried:

sudo apt-get install libwebkitgtk-3.0-dev

which added

gir1.2-javascriptcoregtk-3.0 gir1.2-soup-2.4 gir1.2-webkit-3.0 libgtk-3-dev libjavascriptcoregtk-3.0-dev libsoup2.4-dev libwebkitgtk-3.0-dev libxml2-dev

But error persists:

ImportError: No module named webkit

As a known issue (for Debian), suggested dependencies, i.e., -S sweets command argument, don't work for now.

sweets -S sdk/sugar:emulator

responds

-- Cannot find requireed implementations for
http://sweets.sugarlabs.org/sdk/xulrunner, http://sweets.sugarlabs.org/base/abiword, http://sweets.sugarlabs.org/sdk/evince-python
-- Use status command with -d argument to show problem dependencies             
-- Use -D argument for debug info, -DD for full debuging output and tracebacks

Help with install on IRC

• from IRC with permission--Satellit 08:01, 22 June 2012 (EDT)
• Based on these instructions: http://wiki.sugarlabs.org/go/Platform_Team/Guide/Sugar_via_Sweets

<inkyfingers> Image from: http://www.raspbian.org/
<inkyfingers> is Debian Hard Float (armhf) for RPi
<inkyfingers> Is armhf likely to be a problem for <sweets>?
<alsroot> inkyfingers: I didn't try to run sugar on arm. OLPC people support it but I dunno do they use sugar directly from upstream brunches (what was used for sweets (not SD)) or not
<inkyfingers> #644010 is now marked fixed - so wheezy seems fine to me with python 2.7 - I believe eliminated.
<alsroot> btw, whats exact sugar version you are running on Raspberry?
<inkyfingers> Ok tried sdk/sugar and dextrose/
<inkyfingers> dextrose marginally more success.
<inkyfingers> * Booting Rpi ... will try to ssh for notes . I tested Sugar 0.88 and 0.94
...
<inkyfingers>  raspbian@pisces:~$ sweets  dextrose/sugar:emulator
<inkyfingers> Xephyr on :30.0
<inkyfingers> About my computer:
<inkyfingers> Build: Debian GNU/Linux testing/unstable
<inkyfingers> Sugar: 0.88.1
...
<inkyfingers> I will try to write only about sweets  dextrose/sugar:emulator ...
<inkyfingers> F1 to F6 all fine ok
<alsroot> thats fine..
<alsroot> though, in my mind SD, finally, is more useful way to start sugar itself. but unfortunately, it does not [yet]support arm
<inkyfingers> I could see no avatars in F1 in dextrose <seen fine in sdk, 0.94>
<inkyfingers> I have no Activities in F3
<alsroot> for activities, you can unzip some of them (that are pure python) to ~/Activities
<inkyfingers> That would be a good next step.
<inkyfingers> Two usb ports are used by mouse and kbd. I will prepare a USB stick next and try that out.
<alsroot> inkyfingers: btw, how long it took to build sugar via "sweets" command?
<inkyfingers> Over 8 or 9 mins of 100% CPU
<inkyfingers> sorry ssh into my rubbish notes is hard !! I keep not finding what I want!
<inkyfingers> raspbian@pisces:~$ sweets  sdk/sugar:emulator
<inkyfingers> -- Solve sdk/sugar-artwork for building
<inkyfingers> -- Solve sdk/sugar-base for building
<inkyfingers> -- Solve sdk/sugar-toolkit for building
<inkyfingers> -- Solve sdk/sugar-datastore for building
<inkyfingers> -- Solve sdk/telepathy-mission-control for building
<inkyfingers> -- Solve sdk/sugar for building
<inkyfingers> -- Build sdk/sugar-artwork (0.94.0)
<inkyfingers> -- Build sdk/sugar-base (0.94.0)
<inkyfingers> -- Build sdk/sugar-toolkit (0.94.0)
<inkyfingers> -- Build sdk/sugar-datastore (0.94.0)
<inkyfingers> -- Build sdk/telepathy-mission-control (5.7.1)
<inkyfingers> -- Build sdk/sugar (0.94.1)
<inkyfingers> this made me think Activities should be on-board?
<alsroot> inkyfingers: nope, this way you can't install activities
<alsroot> dunno will Browse work on or not (to open ASLO), but just download .xo files to unzip them to ~/Activities
<inkyfingers> So that trace was just my first successful launch
<inkyfingers> df -h (before that command)
<inkyfingers> Filesystem      Size  Used Avail Use% Mounted on
<inkyfingers> rootfs          3.3G  2.1G  1.1G  68% /
<inkyfingers> now
<inkyfingers> rootfs          3.3G  2.2G  985M  69% /