Talk:Sugar on Ubuntu

Notice: A motion has been made to purge all-pre Gutsy content from this page. Please comment on the Talk page !

automake default in Ubuntu Edgy seems to be automake-1.7 and not automake-1.4

Ubuntu

Please delete or move pre-Gutsy content.

xo-get

I know that I should report bugs in Ubuntu packages on the Ubuntu bug tracker. But where should I report bugs in packages installed using xo-get on ubuntu?

The most appropriate place would be on dev.laptop.org at the moment since the activities are published on wiki.laptop.org, and that is still the upstream bug tracker for most activities. Some activities (particularly those packaged in Ubuntu and Fedora) will move to dev.sugarlabs.org as the upstream bug tracker, but that hasn't happened yet. --morgs 17:55, 17 November 2008 (UTC)

python2.4-avahi??

To be quite honest, i've only been using debian based systems for about 2 weeks now, so my no means am I an expert, but I believe the "python2.4-avahi" in the big apt-get statement should be "python-avahi". Python-avahi is a virtual package that (as of now) supplies python2.4-avahi. --PKPerson

The python2.4-avahi package has been replace by python-avahi according to my APT application. I'll modify the main page.

Dapper has python2.4-avahi. RussNelson 21:21, 1 June 2007 (EDT)

Sugar-jhbuild is hard to work with

I realize that Sugar is changing very rapidly and you guys on the OLPC team are doing an incredible job. I am trying to build activities and teach others how to do the same. However I find it very difficult to use sugar-jhbuild. I get so many errors and I am currently wrestling w/ them -- chundevi

My experience

I'm running Edgy, recently updated from Dapper. After installing all the packages listed in the article, I still got a complaint about missing Python 2.5; I think this may be due to a recent change to the OLPC source. I tried installing a python2.5-dev package with apt-get, but jhbuild didn't recognize it, probably because 2.4 was still the version behind the "python" command. I managed to get around the problem by running a command I saw on another sugar page, which apparently builds Python 2.5 (among other things) from source:

./sugar-jhbuild build meta-sugar-base	 
./sugar-jhbuild build

I had to skip the abiword module (don't remember the error), and I had to skip the Squeak module because a "tinlizzie.org" site was down; I guess that's where it downloads the source from. Otherwise, sugar seemed to build OK for me.

The commands listed in the article failed to launch the avahi-daemon for me, for some reason (error: "The name org.freedesktop.Avahi was not provided by any .service files"). I had to start it manually:

sudo avahi-daemon

After that, "sugar-jhbuild run" worked. When it is running, I see the icons for chat, abiword, penguin TV, firefox, and tamtam. There is a blank spot where the memosono icon would be; clicking on the spot launches memosono. There are errors in the console that may be related:

IOError: [Errno 2] No such file or directory: 
'/media/data2/src/sugar-jhbuild/build/share/activities/Memosono.activity/activity/activity-memorygame.svg'

(/media/data2/src is the local path on my machine where I put sugar-jhbuild.) The penguin TV icon fails with this message in the console:

DBusException: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process 
/media/data2/src/sugar-jhbuild/build/bin/sugar-activity-factory received signal 8

Likewise, tamtam fails with the following message:

DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Process
/media/data2/src/sugar-jhbuild/build/bin/sugar-activity-factory exited with status 1

The other icons all seem to work OK (chat, firefox, abiword). Surprisingly, the abiword icon works, even though I chose to skip the module's failed build. —Leejc 00:15, 7 February 2007 (EST)

Firefox problem on Ubuntu

I got so inspired by the Live CD image for Ubuntu/Sugar that I installed it as a dual boot on a Windows machine and I've pretty well decided I can live without Windows. That's the good news. More good news: the Sugar emulation worked pretty well for a week or so. The bad news: At some point the browser on the Sugar emulator quit working. The application won't start up. The Firefox in Ubuntu works fine.

I'd like to fix the browser activity in Sugar, but can't see how to do it without a full reinstall, which I am reluctant to do at this point.

Can someone please recommend a fix for this, that a relative idiot in the Linux world can understand? I've been around computers since the CP/M days, but I'm a real novice in Linux.

By the way, my compliments to the creator of that Live CD image -- it was a very smooth installation and is a nice package overall.

12/15/07 -- never mind; the latest software update fixed the problem.

Gutsy experiences with jhbuild (1 jan 2008)

You'll also need to apt in libgnomevfs2-dev (evince won't configure without it).

I'm building xulrunner now as 28/50. Wish me luck :)

--Adricnet 08:09, 1 January 2008 (EST)

Built 50/50 with no further guff. Awesome.

--Adricnet 17:01, 1 January 2008 (EST)

Call for purge, any objections?

After a polite debate period of a week or two, and if there are no strong objections, then I move we purge all pre-Gutsy content from this page as part of a remake that will restore it to usefulness.

We could keep the LTS stuff longer, if anyone needs it.

So what say you all?

- I think developers will most likely only run the latest ubuntu, I don't see a need for supporting LTS. Great idea, most supported. --Sebastian 03:10, 16 February 2008 (EST)

Adricnet 03:05, 6 February 2008 (EST)

I support the purge. If supporting outdated Ubuntu flavors is a drain on resources and usefulness, it should be avoided except in the face of a good reason otherwise. I'm not convinced a good reason exists. -FrankTobia 16:34, 17 February 2008 (EST)

I support the purge too. If anyone complains, we could pull the deleted content into a page dedicated to older versions. --morgs 14:21, 19 February 2008 (EST)

support as per morgs. Homunq 18:18, 23 February 2008 (EST)

It has been over a week since the first proposal - I'm going to go ahead and do the purge. 66.65.114.204 23:15, 1 March 2008 (EST)

Rough first-pass purge is done. Please move over anything I may have not moved/moved-erroneously. (The last comment was me, not logged in.) Mchua 23:23, 1 March 2008 (EST)

In future, could you please move this kind of information to a separate page, instead of purging. Reason being - sugar users in the third-world don't have the kind of equipment you first-worldies have, and therefore, are bound to end up being restricted to older distributions or versions of Ubuntu. Please think of them, rather than yourselves. Its is a great pity that you have gone and done this, because I have people with gutsy and earlier asking me about sugar.

python-simplejson

A new dependency? I had to add this to even try to build on Hardy beta

Adricnet 05:05, 22 March 2008 (EDT)

Fresh sugar-jhbuild on Hardy

My old directory wasn't working so I am taking taking the opportunity to move it aside and start a fresh build on Hardy. First off:

Missing packages:
libcroco3-dev libwnck-dev librsvg2-dev python-xapian libxapian15 libloudmouth1-dev

Cheerfully all of these are in main or universe and seem to have apt'd in cleanly. More later, then.. built clean with no guff:

 *** success *** [39/39]

-- Adricnet 05:49, 27 April 2008 (EDT)

Sugar in Hardy Universe

Mr Monoses blog carries some startlingly good news: Sugar is in Hardy's Universe repositories, save a few packages that still need help catching up. This is fabulous news!

I just pulled in the packages and have sugar-emulator up now, with Journal. -- Adricnet 06:18, 27 April 2008 (EDT)

Screen problems with sugar-emulator

I have installed sugar on ubuntu hardy but the default screen resolution makes it impossible to use, as the bottom of the window is cut off. The instructions on Sugar-jhbuild#Configure_the_mode_and_resolution_of_Sugar is of absolutely no use, since the files are in different locations. Would it be possible to make an "howto: change screen resolution on ubuntu". Many modern laptops are widescreen with less than 900 px in hight so this problem might hinder other people than me.

I think it's a great project but if other people are to participate it would be grate if you didn't have to edit python files as the first thing to get it working.

For a half experienced linux guy as my self it was strange to find that there are no man pages on sugar.

--Thorseth 11:59, 2 May 2008 (EDT)

Just a wild guess, but with sugar-jhbuild I run "sugar-emulator -x". HoboPrimate 13:06, 2 May 2008 (EDT)

Thanks, it helps but not enough. I can now see the very top of the activity icons in the bottom of the screen. Where can I find the options such as '-x' etc. ? Thorseth 14:12, 2 May 2008 (EDT)

Error in the instruction for changing screen resolution in Hardy

The description on how to change screen resolution in the emulator on Hardy is wrong. The file

/usr/bin/sugar-emulator

does not have any of the code mentioned in the howto, this code is in

/usr/share/sugar/shell/emulator.py

if nobody protests or overtake me I will make the appropriate changes when I get the time. -- Thorseth 09:11, 12 May 2008 (EDT) Bold text

Installing Sugar desktop in Ubuntu Hardy

I installed the sugar desktop from the Hardy repository a while ago and it worked wonderfully except for a few bugs. I remember having to edit the .desktop file in order to work. Recently I upgraded and lost the installation. Now i want to reinstall, but I can't get into a session since I don't know where the instructions for editing the .desktop file are. Does anybody know how to do this, since I don't want to run in emulation?

I can't log into my sugar session. This is the error code

[CODE]/etc/gdm/Xsession: Beginning session setup... setting IM thorugh im-switch for locale = en_ZA. start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default

• • • PULSEAUDIO: unable to connect: Connection refused
  • (sugar-shell:13118): CRITICAL **.

_wrap-gstmixer-list-tracks: assertion 'GST_IS_MIXER (self->obj)' failed[/CODE]