[Sugar-devel] Error on running sugar-activity
James Cameron
quozl at laptop.org
Wed Jul 31 23:15:38 EDT 2019
Thanks. With datastore not running, expected symptoms are as you say;
activities are not shown, and activities cannot be started.
(Colour of icon in home view is determined by existence of a journal
object for that activity, so before home view is shown the journal
must be searched for matching objects. The journal is held by the
datastore.)
However, I am surprised at your shell.log, for three reasons;
1. it does not show any errors about trying to contact the datastore.
2. the timestamp in the file of 1564399715.389937 is 29th July at
4:58pm, which was 2.65 days ago, yet the traceback was from 31st July
at 10:17am.
3. it shows Sugar was being started on an X11 display that already
has a window manager; normally Sugar is run on a display with no
window manager, and this may imply you are starting Sugar from a
Terminal instead of from an X session or login greeter.
On the theory that the datastore is failing to start, please test
again by one or more of;
(a) looking at apport /var/crash to find evidence confirming failure,
(b) temporarily excluding Sugar and activities, using instead the
copy-to-journal tool provided by the datastore,
(c) deinstalling the /usr/local datastore and reinstalling the
packaged datastore,
(d) running the datastore by hand instead of requiring D-Bus to start
it, and look for errors.
Hope that helps.
On Thu, Aug 01, 2019 at 08:21:27AM +0530, Swarup N wrote:
> I agree with James,
> I have not had a problem with the order either, because I have often used
> multiple orders while settings up Sugar v0.114 in the past.
>
> The activity is being run outside the sugar desktop environment. When I log
> into to the Sugar desktop, from the initial gdm3 greeter, the activities in the
> home view (Favourites) do not appear. On trying to run an activity from the
> home view (All activities), the activity does not start, rather, the icon
> continues to blip on the screen,
>
> On looking at the shell.log in the logs directory, I have the following
> warnings,
>
> (metacity:3385): metacity-WARNING **: 16:58:35.241: Screen 0 on display ":0"
> already has a window manager; try using the --replace option to replace the
> current window manager.
> 1564399715.389937 ERROR root: window manager did fail,
> /usr/local/lib/python2.7/dist-packages/jarabe/main.py:378: Warning:
> g_spawn_command_line_async: assertion 'command_line != NULL' failed
> Gtk.main()
>
> Thanks.
>
> On Thu, Aug 1, 2019 at 3:40 AM James Cameron <[1]quozl at laptop.org> wrote:
>
> I've not had a problem with order, but have had problems mixing
> install destination because of the extra changes needed.
>
> I'll speculate some more.
>
> Looking at the traceback shows the toolkit is installed to /usr/local,
> and the activity source is being run in
> /home/buba/sugar-stuff/sugar-activities/ via
> /usr/local/bin/sugar-activity.
>
> I can't tell if sugar-activity is being run by a Terminal inside
> Sugar, or by a Terminal outside Sugar.
>
> When the datastore does not work, the Sugar shell.log would also
> indicate this, and the Journal would not be usable.
>
> On Wed, Jul 31, 2019 at 04:00:58PM +0530, ANIKET MATHUR wrote:
> > Swarup, what is the order of installation you followed for datastore,
> sugar and
> > sugar-toolkit?
> >
> > I am not much sure about it but it might be related.
> >
> > Thanks.
> >
> > On Wed, 31 Jul 2019, 3:55 pm James Cameron, <[1][2]quozl at laptop.org>
> wrote:
> >
> > The datastore process failed. Look in datastore.log for more
> > information.
> >
> > Datastore is started by Sugar through D-Bus API, and would normally
> > continue operating until Sugar is stopped. If it fails before an
> > activity is started, then the activity call through the D-Bus API
> will
> > restart the datastore. The traceback you pasted shows this has
> > happened, and then the datastore failed again.
> >
> > Check the D-Bus service file created by the datastore source. It may
> > refer to the wrong path for the binary.
> >
> > On Wed, Jul 31, 2019 at 10:21:48AM +0530, Swarup N wrote:
> > > Hi,
> > > I setup Sugar 0.114 via the Native method on a new laptop. On
> running
> > > sugar-activity, I get the following message.
> > >
> > > Traceback (most recent call last):
> > > File "/usr/local/bin/sugar-activity", line 5, in <module>
> > > activityinstance.main()
> > > File "/usr/local/lib/python2.7/dist-packages/sugar3/activity/
> > > activityinstance.py", line 230, in main
> > > instance = create_activity_instance(activity_constructor,
> > activity_handle)
> > > File "/usr/local/lib/python2.7/dist-packages/sugar3/activity/
> > > activityinstance.py", line 59, in create_activity_instance
> > > activity = constructor(handle)
> > > File "/home/buba/sugar-stuff/sugar-activities/convert/
> activity.py",
> > line 41,
> > > in __init__
> > > activity.Activity.__init__(self, handle, True)
> > > File "/usr/local/lib/python2.7/dist-packages/sugar3/activity/
> > activity.py",
> > > line 432, in __init__
> > > self._jobject = self._initialize_journal_object()
> > > File "/usr/local/lib/python2.7/dist-packages/sugar3/activity/
> > activity.py",
> > > line 520, in _initialize_journal_object
> > > datastore.write(jobject)
> > > File "/usr/local/lib/python2.7/dist-packages/sugar3/datastore/
> > datastore.py",
> > > line 394, in write
> > > transfer_ownership)
> > > File "/usr/local/lib/python2.7/dist-packages/sugar3/datastore/
> > datastore.py",
> > > line 344, in _create_ds_entry
> > > object_id = _get_data_store().create(dbus.Dictionary
> (properties),
> > filename,
> > > File "/usr/local/lib/python2.7/dist-packages/sugar3/datastore/
> > datastore.py",
> > > line 51, in _get_data_store
> > > DS_DBUS_PATH),
> > > File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 241, in
> > get_object
> > > follow_name_owner_changes=follow_name_owner_changes)
> > > File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line
> 248, in
> > > __init__
> > > self._named_service = conn.activate_name_owner(bus_name)
> > > File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 180, in
> > > activate_name_owner
> > > self.start_service_by_name(bus_name)
> > > File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 278, in
> > > start_service_by_name
> > > 'su', (bus_name, flags)))
> > > File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line
> 651,
> > in
> > > call_blocking
> > > message, timeout)
> > > dbus.exceptions.DBusException:
> > org.freedesktop.DBus.Error.Spawn.ChildExited:
> > > Process org.laptop.sugar.DataStore exited with status 1
> > > 1564548420.435550 WARNING root: DSObject was deleted without
> cleaning up
> > first.
> > > Call DSObject.destroy() before disposing it.
> > >
> > > I would be grateful for any suggestions on fixing this.
> > >
> > > Thanks.
> >
> > --
> > James Cameron
> > [2][3]http://quozl.netrek.org/
> > _______________________________________________
> > Sugar-devel mailing list
> > [3][4]Sugar-devel at lists.sugarlabs.org
> > [4][5]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > References:
> >
> > [1] mailto:[6]quozl at laptop.org
> > [2] [7]http://quozl.netrek.org/
> > [3] mailto:[8]Sugar-devel at lists.sugarlabs.org
> > [4] [9]http://lists.sugarlabs.org/listinfo/sugar-devel
>
> --
> James Cameron
> [10]http://quozl.netrek.org/
> _______________________________________________
> Sugar-devel mailing list
> [11]Sugar-devel at lists.sugarlabs.org
> [12]http://lists.sugarlabs.org/listinfo/sugar-devel
>
> References:
>
> [1] mailto:quozl at laptop.org
> [2] mailto:quozl at laptop.org
> [3] http://quozl.netrek.org/
> [4] mailto:Sugar-devel at lists.sugarlabs.org
> [5] http://lists.sugarlabs.org/listinfo/sugar-devel
> [6] mailto:quozl at laptop.org
> [7] http://quozl.netrek.org/
> [8] mailto:Sugar-devel at lists.sugarlabs.org
> [9] http://lists.sugarlabs.org/listinfo/sugar-devel
> [10] http://quozl.netrek.org/
> [11] mailto:Sugar-devel at lists.sugarlabs.org
> [12] http://lists.sugarlabs.org/listinfo/sugar-devel
--
James Cameron
http://quozl.netrek.org/
More information about the Sugar-devel
mailing list