On 12/5/06, Mike Hunter <[EMAIL PROTECTED]> wrote:

> ./sugar-jhbuild run
> Running the installed sugar...
> error opening security policy file /usr/lib/xserver/SecurityPolicy
> Extended Input Devices not yet supported. Impelement it at line 625 in
>../../../../hw/kdrive/src/kinput.c
>     xkb_keycodes             { include "xfree86+aliases(qwerty)" };
>     xkb_types                { include "complete" };
>     xkb_compatibility        { include "complete" };
>     xkb_symbols              { include "pc(pc101)+us" };
>     xkb_geometry             { include "pc(pc101)" };
> Could not init font path element /usr/share/fonts/X11/TTF/, removing
from list!
> Could not init font path element /usr/share/fonts/X11/OTF, removing from
list!
> Could not init font path element /usr/share/fonts/X11/CID/, removing
from list!
> matchbox-wm: X error warning (0): RenderBadPicture (invalid Picture
parameter) (opcode: >150)
> Tracebacks will be written to /tmp/sugar-shell-7407 on SIGUSR1
> Introspect error: The name org.laptop.DCONManager was not provided by
any .service >files


I am not positive, but I believe these just relate to not running sugar on
the motherboard itself(it seems to be expecting certain hardware).

Despite these warnings, the sugar gui comes up.  However, if I try to fire
> up abiword, I get the following:
>
> Introspect error: Process
/home/mhunter/sugar-jhbuild/build/bin/sugar-activity-factory >exited with
status 1
> Traceback (most recent call last):
>   File
"/home/mhunter/sugar-jhbuild/build/share/sugar/shell/view/frame/ActivitiesBox.py",
>line 71, in _activity_clicked_cb
>     self._shell.start_activity(icon.get_bundle_id())
>   File
"/home/mhunter/sugar-jhbuild/build/share/sugar/shell/view/Shell.py", line
200, in >start_activity
>     activity = ActivityFactory.create(activity_type)
>   File
>"/home/mhunter/sugar-jhbuild/build/lib/python2.4/site-packages/sugar/activity/ActivityFactory.py",
line 87, in create
>     xid = factory.create()
>   File "/var/lib/python-support/python2.4/dbus/proxies.py", line 25, in
__call__
>     ret = self._proxy_method (*args, **keywords)
>   File "/var/lib/python-support/python2.4/dbus/proxies.py", line 102, in
__call__
>     reply_message = self._connection.send_with_reply_and_block(message,
timeout)
>   File "dbus_bindings.pyx", line 455, in
>     bus_bindings.Connection.send_with_reply_and_block
> DBusException: Process
/home/mhunter/sugar-jhbuild/build/bin/sugar-activity-factory
> exited with status 1


I believe this has to do with not having libabiword and pyabiword installed.
I believe that they are part of the sugar-jhbuild, but they may have some
problems building still. So, unless you have libabiword built on your local
machine, you won't be able to build pyabiword with sugar-jhbuild.

I also get into trouble trying to run the drum thing:
>
> Introspect error: Process
/home/mhunter/sugar-jhbuild/build/bin/sugar-activity-factory exited with
status 1
> Traceback (most recent call last):
>   File
"/home/mhunter/sugar-jhbuild/build/share/sugar/shell/view/frame/ActivitiesBox.py",
line 71, in _activity_clicked_cb
>     self._shell.start_activity(icon.get_bundle_id())
>   File
"/home/mhunter/sugar-jhbuild/build/share/sugar/shell/view/Shell.py", line
200, in start_activity
>     activity = ActivityFactory.create(activity_type)
>   File
"/home/mhunter/sugar-jhbuild/build/lib/python2.4/site-packages/sugar/activity/ActivityFactory.py",
line 87, in create
>     xid = factory.create()
>   File "/var/lib/python-support/python2.4/dbus/proxies.py", line 25, in
__call__
>     ret = self._proxy_method (*args, **keywords)
>   File "/var/lib/python-support/python2.4/dbus/proxies.py", line 102, in
__call__
>     reply_message = self._connection.send_with_reply_and_block(message,
timeout)
>   File "dbus_bindings.pyx", line 455, in
dbus_bindings.Connection.send_with_reply_and_block
> DBusException: Process
/home/mhunter/sugar-jhbuild/build/bin/sugar-activity-factory exited with
status 1


Once again, I believe this has to do that it isn't on the motherboard. When
I looked into the issue, it seemed that csound was the dependency that was
causing the issue. I don't know much about this, so maybe that can be
installed locally as well.


--
Justin Gallardo
_______________________________________________
Sugar mailing list
[email protected]
http://mailman.laptop.org/mailman/listinfo/sugar

Reply via email to