Re: [Sugar-devel] Error on running sugar-activity
Yes James, Now that I go through the commits for sugar-datastore, I had built datastore for Python2 instead of Python3. I shall repeat the sudo make install step once again, however this time building for python3 and post the result here Thanks. On Fri, Aug 2, 2019 at 8:10 AM James Cameron wrote: > Yes, it is possible that your issue of running sugar activities was > introduced at the commit where the warning got updated, so you should > test the possibility by checking out the immediately prior commit. > > You could also review the commit for functional change. > > First, find the commit. > > The message is in this file; > > > https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/src/sugar3/activity/activityinstance.py#L138 > > According to "git blame", the whitespace was introduced by 3b28597. > > > https://github.com/sugarlabs/sugar-toolkit-gtk3/blame/master/src/sugar3/activity/activityinstance.py#L138 > > https://github.com/sugarlabs/sugar-toolkit-gtk3/commit/3b28597486951c225239c220def190377ee1739f#diff-35db2ad94d2c22d773bce7bb50fdacafL138 > > The whitespace is not welcome. You may either remove it yourself, > tell Aniket about it, or if you don't want to work toward fixing it > create a new issue. > > However, given that the error message you posted specifically > identifies the datastore as failing to start, it is more likely that > the commits to the datastore have introduced a regression. I've given > you methods to prove that, but not enough information has been > revealed, and I've not had time to try it myself. I had tested it > already, so don't want to waste time testing again unless I can see > what is different. > > On speculation that you may not have been aware of the Port to Python > 3 of the datastore, I've updated the instructions for native install; > > > https://github.com/sugarlabs/sugar/commit/e3206870eca3b99bc5baf43750318b72a481191c > > Let me know if you had built the datastore for Python 2 by mistake. > > On Fri, Aug 02, 2019 at 07:22:33AM +0530, Swarup N wrote: > > Hi > > I noticed something strange. Earlier while i was trying run > sugar-activity > > through Ubuntu Terminal, the warning that is thrown "Activity written > for > > Python 2, consider porting to Python 3", was being shown as "Activity > written > > for Python 2, consider porting to > Python > > 3", with a considerable amount of whitespace in between in words. > > > > Could it be possible that the issue of running sugar activities was > introduced > > at the commit where the warning got updated? > > > > Thanks. > > > > On Fri, Aug 2, 2019 at 7:12 AM Swarup N <[1]nswaru...@gmail.com> wrote: > > > > Hi, > > > > I was able get Sugar running as expected, thanks to James's earlier > > suggestion. > > I entering each of the core sugar directories, apart from > sugar-toolkit, i > > checked out via "git checkout v0.114" to the v0.114 tag, and > repeated the > > process of sudo make install for each of these directories, and > logged out > > and logged in with Sugar-desktop selected. This way I was able to > get my > > activities running. > > > > Earlier, I had cloned the HEAD of each the repositories. Perhaps a > later > > change to sugar-datastore was what causing the issue? > > > > Thanks for all the help. > > > > -Swarup N > > > > On Thu, Aug 1, 2019 at 12:01 PM James Cameron <[2]qu...@laptop.org> > wrote: > > > > Again, this only tells you the datastore has failed on start. > > > > On Thu, Aug 01, 2019 at 11:25:09AM +0530, Swarup N wrote: > > > File > "/usr/local/lib/python2.7/dist-packages/sugar3/datastore/ > > datastore.py", > > > line 51, in _get_data_store > > > [...] > > > dbus.exceptions.DBusException: > > org.freedesktop.DBus.Error.Spawn.ChildExited: > > > Process org.laptop.sugar.DataStore exited with status 1 > > > > -- > > James Cameron > > [3]http://quozl.netrek.org/ > > > > References: > > > > [1] mailto:nswaru...@gmail.com > > [2] mailto:qu...@laptop.org > > [3] http://quozl.netrek.org/ > > -- > James Cameron > http://quozl.netrek.org/ > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Error on running sugar-activity
Yes, it is possible that your issue of running sugar activities was introduced at the commit where the warning got updated, so you should test the possibility by checking out the immediately prior commit. You could also review the commit for functional change. First, find the commit. The message is in this file; https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/src/sugar3/activity/activityinstance.py#L138 According to "git blame", the whitespace was introduced by 3b28597. https://github.com/sugarlabs/sugar-toolkit-gtk3/blame/master/src/sugar3/activity/activityinstance.py#L138 https://github.com/sugarlabs/sugar-toolkit-gtk3/commit/3b28597486951c225239c220def190377ee1739f#diff-35db2ad94d2c22d773bce7bb50fdacafL138 The whitespace is not welcome. You may either remove it yourself, tell Aniket about it, or if you don't want to work toward fixing it create a new issue. However, given that the error message you posted specifically identifies the datastore as failing to start, it is more likely that the commits to the datastore have introduced a regression. I've given you methods to prove that, but not enough information has been revealed, and I've not had time to try it myself. I had tested it already, so don't want to waste time testing again unless I can see what is different. On speculation that you may not have been aware of the Port to Python 3 of the datastore, I've updated the instructions for native install; https://github.com/sugarlabs/sugar/commit/e3206870eca3b99bc5baf43750318b72a481191c Let me know if you had built the datastore for Python 2 by mistake. On Fri, Aug 02, 2019 at 07:22:33AM +0530, Swarup N wrote: > Hi > I noticed something strange. Earlier while i was trying run sugar-activity > through Ubuntu Terminal, the warning that is thrown "Activity written for > Python 2, consider porting to Python 3", was being shown as "Activity written > for Python 2, consider porting to Python > 3", with a considerable amount of whitespace in between in words. > > Could it be possible that the issue of running sugar activities was introduced > at the commit where the warning got updated? > > Thanks. > > On Fri, Aug 2, 2019 at 7:12 AM Swarup N <[1]nswaru...@gmail.com> wrote: > > Hi, > > I was able get Sugar running as expected, thanks to James's earlier > suggestion. > I entering each of the core sugar directories, apart from sugar-toolkit, i > checked out via "git checkout v0.114" to the v0.114 tag, and repeated the > process of sudo make install for each of these directories, and logged out > and logged in with Sugar-desktop selected. This way I was able to get my > activities running. > > Earlier, I had cloned the HEAD of each the repositories. Perhaps a later > change to sugar-datastore was what causing the issue? > > Thanks for all the help. > > -Swarup N > > On Thu, Aug 1, 2019 at 12:01 PM James Cameron <[2]qu...@laptop.org> wrote: > > Again, this only tells you the datastore has failed on start. > > On Thu, Aug 01, 2019 at 11:25:09AM +0530, Swarup N wrote: > > File "/usr/local/lib/python2.7/dist-packages/sugar3/datastore/ > datastore.py", > > line 51, in _get_data_store > > [...] > > dbus.exceptions.DBusException: > org.freedesktop.DBus.Error.Spawn.ChildExited: > > Process org.laptop.sugar.DataStore exited with status 1 > > -- > James Cameron > [3]http://quozl.netrek.org/ > > References: > > [1] mailto:nswaru...@gmail.com > [2] mailto:qu...@laptop.org > [3] http://quozl.netrek.org/ -- James Cameron http://quozl.netrek.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Error on running sugar-activity
Hi I noticed something strange. Earlier while i was trying run *sugar-activity* through Ubuntu Terminal, the warning that is thrown "Activity written for Python 2, consider porting to Python 3", was being shown as "Activity written for Python 2, consider porting to Python 3", with a considerable amount of whitespace in between in words. Could it be possible that the issue of running sugar activities was introduced at the commit where the warning got updated? Thanks. On Fri, Aug 2, 2019 at 7:12 AM Swarup N wrote: > Hi, > > I was able get Sugar running as expected, thanks to James's earlier > suggestion. > I entering each of the core sugar directories, apart from sugar-toolkit, i > checked out via "git checkout v0.114" to the v0.114 tag, and repeated the > process of sudo make install for each of these directories, and logged out > and logged in with Sugar-desktop selected. This way I was able to get my > activities running. > > Earlier, I had cloned the HEAD of each the repositories. Perhaps a later > change to sugar-datastore was what causing the issue? > > Thanks for all the help. > > -Swarup N > > On Thu, Aug 1, 2019 at 12:01 PM James Cameron wrote: > >> Again, this only tells you the datastore has failed on start. >> >> On Thu, Aug 01, 2019 at 11:25:09AM +0530, Swarup N wrote: >> > File >> "/usr/local/lib/python2.7/dist-packages/sugar3/datastore/datastore.py", >> > line 51, in _get_data_store >> > [...] >> > dbus.exceptions.DBusException: >> org.freedesktop.DBus.Error.Spawn.ChildExited: >> > Process org.laptop.sugar.DataStore exited with status 1 >> >> -- >> James Cameron >> http://quozl.netrek.org/ >> > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Error on running sugar-activity
Hi, I was able get Sugar running as expected, thanks to James's earlier suggestion. I entering each of the core sugar directories, apart from sugar-toolkit, i checked out via "git checkout v0.114" to the v0.114 tag, and repeated the process of sudo make install for each of these directories, and logged out and logged in with Sugar-desktop selected. This way I was able to get my activities running. Earlier, I had cloned the HEAD of each the repositories. Perhaps a later change to sugar-datastore was what causing the issue? Thanks for all the help. -Swarup N On Thu, Aug 1, 2019 at 12:01 PM James Cameron wrote: > Again, this only tells you the datastore has failed on start. > > On Thu, Aug 01, 2019 at 11:25:09AM +0530, Swarup N wrote: > > File > "/usr/local/lib/python2.7/dist-packages/sugar3/datastore/datastore.py", > > line 51, in _get_data_store > > [...] > > dbus.exceptions.DBusException: > org.freedesktop.DBus.Error.Spawn.ChildExited: > > Process org.laptop.sugar.DataStore exited with status 1 > > -- > James Cameron > http://quozl.netrek.org/ > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Error on running sugar-activity
Again, this only tells you the datastore has failed on start. On Thu, Aug 01, 2019 at 11:25:09AM +0530, Swarup N wrote: > File "/usr/local/lib/python2.7/dist-packages/sugar3/datastore/datastore.py", > line 51, in _get_data_store > [...] > dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: > Process org.laptop.sugar.DataStore exited with status 1 -- James Cameron http://quozl.netrek.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Error on running sugar-activity
You say this is v0.114? I really doubt that. v0.114 didn't do this when I tested it. How are you ensuring you are using v0.114? You would have had to either; (a) git clone with the "-b v0.114" option, or; (b) git checkout v0.114 for each module repository. On Thu, Aug 01, 2019 at 10:54:36AM +0530, Swarup N wrote: > I reinstalled Ubuntu 18.04 once again, and install sugar v0.114 via the native > method > I have attached the shell.log after running attempting to run sugar from > Terminal for the very first time. > > I shall also investigate further based on suggestions from James > > Thanks. > > On Thu, Aug 1, 2019 at 8:45 AM James Cameron <[1]qu...@laptop.org> wrote: > > 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][2]qu...@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][3] > qu...@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
Re: [Sugar-devel] Error on running sugar-activity
Hello,
I tried to login to the Sugar desktop from the greeter and I have pasted
the traceback from the *shell.log *file.
Traceback (most recent call last):
File
"/usr/local/lib/python2.7/dist-packages/jarabe/desktop/favoritesview.py",
line 304, in __connect_to_bundle_registry_cb
self._add_activity(info)
File
"/usr/local/lib/python2.7/dist-packages/jarabe/desktop/favoritesview.py",
line 317, in _add_activity
icon = ActivityIcon(activity_info)
File
"/usr/local/lib/python2.7/dist-packages/jarabe/desktop/favoritesview.py",
line 434, in __init__
self._refresh()
File
"/usr/local/lib/python2.7/dist-packages/jarabe/desktop/favoritesview.py",
line 441, in _refresh
self._get_last_activity_async(bundle_id, properties)
File
"/usr/local/lib/python2.7/dist-packages/jarabe/desktop/favoritesview.py",
line 460, in _get_last_activity_async
error_handler=self.__get_last_activity_error_handler_cb)
File
"/usr/local/lib/python2.7/dist-packages/sugar3/datastore/datastore.py",
line 460, in find
_get_data_store().find(query, properties,
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
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/jarabe/main.py", line 125,
in setup_journal_cb
journalactivity.start()
File
"/usr/local/lib/python2.7/dist-packages/jarabe/journal/journalactivity.py",
line 658, in start
get_journal()
File
"/usr/local/lib/python2.7/dist-packages/jarabe/journal/journalactivity.py",
line 615, in get_journal
_journal = JournalActivity()
File
"/usr/local/lib/python2.7/dist-packages/jarabe/journal/journalactivity.py",
line 212, in __init__
self._setup_main_view()
File
"/usr/local/lib/python2.7/dist-packages/jarabe/journal/journalactivity.py",
line 281, in _setup_main_view
self._main_toolbox = MainToolbox()
File
"/usr/local/lib/python2.7/dist-packages/jarabe/journal/journaltoolbox.py",
line 150, in __init__
self.refresh_filters()
File
"/usr/local/lib/python2.7/dist-packages/jarabe/journal/journaltoolbox.py",
line 435, in refresh_filters
for bundle_id in model.get_unique_values('activity'):
File "/usr/local/lib/python2.7/dist-packages/jarabe/journal/model.py",
line 647, in get_unique_values
return _get_datastore().get_uniquevaluesfor(key, empty_dict)
File "/usr/local/lib/python2.7/dist-packages/jarabe/journal/model.py",
line 549, in _get_datastore
remote_object = bus.get_object(DS_DBUS_SERVICE, 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
(metacity:1487): metacity-WARNING **: 11:21:58.045: CurrentTime used to
choose focus window; focus window may not be correct.
Thanks
On Thu, Aug 1, 2019 at 10:54 AM Swarup N wrote:
> I reinstalled Ubuntu 18.04 once again, and install sugar v0.114 via the
> native method
> I have attached the shell.log after running attempting to run *sugar* from
> Terminal for the very first time.
>
> I shall also investigate further based on suggestions from James
>
> Thanks.
>
>
> On Thu, Aug 1, 2019 at 8:45 AM James Cameron wrote:
>
>> 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
Re: [Sugar-devel] Error on running sugar-activity
I reinstalled Ubuntu 18.04 once again, and install sugar v0.114 via the native method I have attached the shell.log after running attempting to run *sugar* from Terminal for the very first time. I shall also investigate further based on suggestions from James Thanks. On Thu, Aug 1, 2019 at 8:45 AM James Cameron wrote: > 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]qu...@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] > qu...@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. > > > > > > > >
Re: [Sugar-devel] Error on running sugar-activity
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]qu...@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]qu...@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 > > > 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 > > >
Re: [Sugar-devel] Error on running sugar-activity
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 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]qu...@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 > > > 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",
Re: [Sugar-devel] Error on running sugar-activity
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]qu...@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 > > 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]http://quozl.netrek.org/ > ___ > Sugar-devel mailing list > [3]Sugar-devel@lists.sugarlabs.org > [4]http://lists.sugarlabs.org/listinfo/sugar-devel > > References: > > [1] mailto:qu...@laptop.org > [2] http://quozl.netrek.org/ > [3] mailto:Sugar-devel@lists.sugarlabs.org > [4] http://lists.sugarlabs.org/listinfo/sugar-devel -- James Cameron http://quozl.netrek.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org
Re: [Sugar-devel] Error on running sugar-activity
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, 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 > > 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 > http://quozl.netrek.org/ > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Error on running sugar-activity
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 > 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 http://quozl.netrek.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Error on running sugar-activity
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 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. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
