[Sugar-devel] Glucose and Frame
gaknar at gmail.com
Tue Dec 15 15:02:35 EST 2009
Thanks to tomeu, who had the patience to guide me on IRC. And now it
Here are the solutions for the record :
The first bug was a conflict in Python's sys.path, the main module
imported was finally jhbuild's one instead of
sugar-presence-service's. On my config, I decided to prepend
/usr/share/sugar-presence-service to the path instead of appending it.
I don't know if it's the best solution but if I fix that bug on the
jhbuild side, sugar may conflict again with another package. So here,
sugar-presence-service modules are checked before anything else.
Second bug, xapian and it's python bindings are required (need to
include that to my depends array and also to review the strangely
named "xapian-python-bindings" package in AUR where it should be
simply named "python-xapian")
Last bug, gconf schemas where not merged, so after installing files,
you should run as root
# export GCONF_CONFIG_SOURCE=`gconftool-2 --get-default-source`
# gconftool-2 --makefile-install-rule /etc/gconf/schemas/sugar.schemas
These steps are handled by make install normally but when creating a
package, they must be included into the installation script.
After this, Sugar should work properly.
Packages will be available in AUR when I have tested them enough to
be sure they are correct.
2009/12/15 Tomeu Vizoso <tomeu at sugarlabs.org>:
> On Tue, Dec 15, 2009 at 16:58, Cilyan Olowen <gaknar at gmail.com> wrote:
>> Thanks for the reply, here is the log and indeed, it seems there is a
>> problem with the presence service.
> Ok, and what says sugar-presence-service?
>> 2009/12/15 Tomeu Vizoso <tomeu at sugarlabs.org>:
>>> On Tue, Dec 15, 2009 at 16:39, Cilyan Olowen <gaknar at gmail.com> wrote:
>>>> Hello !
>>>> I'm all new in the Sugar community, but I'm very interested in Sugar's
>>>> very simple and intuitive interface for my grand parents who are
>>>> completely new to computers. As I need a light and very strong system,
>>>> I decided to base this on a distrib I know very well : ArchLinux. I
>>>> met here another Archer who has almost the same needs and same
>>>> interests, and together we decided to package Sugar for ArchLinux.
>>>> That's for the background.
>>>> Now the project has a little bit progressed, and I'm ending with
>>>> Glucose almost packaged :
>>>> hippo-canvas, hulahop, python-xklavier, squeak, sugar, sugar-artwork,
>>>> sugar-base, sugar-datastore, sugar-presence-service, sugar-toolkit
>>>> (I'm missing etoys and pyabiword). All this is now installed on my
>>>> system and I wanted to make a little check of where I was. And
>>>> surprise, after launching "sugar" in a console, no Frame ! Metacity is
>>>> launched, together with a nice big cursor, but no Frame or Activity
>>>> Circle. Same with "sugar-emulator" which opens a nice Xephyr window
>>>> with a black screen and the famous cursor inside, but nothing more.
>>>> And indeed it seems that the sugar script ends with no error or maybe
>>>> forks to the background but I have no trace of it in "ps".
>>>> This leads to the simple question : Do I have a misconfiguration here,
>>>> a bug, or am I simply missing a packet ?
>>>> Woo, such a long message for a simple question, yes I know, sorry. But
>>>> I needed to introduce myself too to your community ;)
>>> Hi Cilyan, welcome.
>>> Can you attach ~/.sugar/default/logs/shell.log? There should be some error.
>>>> Sugar-devel mailing list
>>>> Sugar-devel at lists.sugarlabs.org
>>> «Sugar Labs is anyone who participates in improving and using Sugar.
>>> What Sugar Labs does is determined by the participants.» - David
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
> «Sugar Labs is anyone who participates in improving and using Sugar.
> What Sugar Labs does is determined by the participants.» - David
More information about the Sugar-devel