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