[Sugar-devel] Toolkit Installation Sugar v0.113
ANIKET MATHUR
amathur at ec.iitr.ac.in
Tue May 21 04:21:52 EDT 2019
Thanks James I was not starting Sugar as a desktop session. Now things work
fine for me.
On Tue, May 21, 2019 at 12:26 PM James Cameron <quozl at laptop.org> wrote:
> Thanks.
>
> Are you sure you gave me the correct log? There's no segmentation
> fault shown there. The log should be .sugar/default/logs/shell.log
>
> You can gather more information about a segmentation fault using gdb
> and backtrace command.
>
> Further reply in context below.
>
> On Tue, May 21, 2019 at 12:10:20PM +0530, ANIKET MATHUR wrote:
> > Regarding the Segmentation Fault.
> >
> > (main.py:2041): Gtk-WARNING **: 12:04:58.709: Theme parsing error:
> > gtk-widgets.css:16:32: The style property GtkExpander:expander-size
> is
> > deprecated and shouldn't be used anymore. It will be removed in a
> future
> > version
> >
> > (main.py:2041): Gtk-WARNING **: 12:04:58.709: Theme parsing error:
> > gtk-widgets.css:17:35: The style property
> GtkExpander:expander-spacing is
> > deprecated and shouldn't be used anymore. It will be removed in a
> future
> > version
> >
> > (metacity:2048): metacity-WARNING **: 12:04:58.799: Screen 0 on
> display
> > ":0" already has a window manager; try using the --replace option to
> > replace the current window manager.
> > 1558420503.333096 ERROR root: window manager did fail, restarting
> > Traceback (most recent call last):
>
> Confirm you are starting Sugar as a desktop session and not as a
> program inside another desktop session?
>
> For example, on my Ubuntu 18.04 test system, `ps axfww` shows jarabe
> to be a child process of gdm-x-session, gdm-session-worker, and gdm3;
> thus;
>
> ...
> 1885 ? Ssl 0:00 /usr/sbin/gdm3
> 2547 ? Sl 0:00 \_ gdm-session-worker [pam/gdm-password]
> 2557 tty2 Ssl+ 0:00 \_ /usr/lib/gdm3/gdm-x-session
> --run-script sugar
> 2560 tty2 Sl+ 0:10 \_ /usr/lib/xorg/Xorg vt2 -displayfd 3
> -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty
> -verbose 3
> 2569 tty2 Sl+ 0:10 \_ python2 -m jarabe.main
> 2635 ? Ss 0:00 \_ /usr/bin/ssh-agent
> /usr/bin/im-launch sugar
> 2659 tty2 Z+ 0:00 \_ [sugar] <defunct>
> 2670 tty2 Sl+ 0:00 \_ metacity --no-force-fullscreen
> --no-composite
>
> > File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line
> 604, in
> > msg_reply_handler
> > reply_handler(*message.get_args_list(**get_args_opts))
> > File "/usr/local/lib/python2.7/dist-packages/jarabe/model/
> > neighborhood.py", line 738, in __got_accounts_cb
> > self._server_account = self._ensure_server_account(account_paths)
> > File "/usr/local/lib/python2.7/dist-packages/jarabe/model/
> > neighborhood.py", line 851, in _ensure_server_account
> > properties)
> > File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70,
> in
> > __call__
> > return self._proxy_method(*args, **keywords)
> > File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145,
> in
> > __call__
> > **keywords)
> > File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line
> 651, in
> > call_blocking
> > message, timeout)
> > dbus.exceptions.DBusException:
> > org.freedesktop.Telepathy.Error.NotImplemented: Protocol 'jabber'
> not found
> > on CM 'gabble'
>
> Is Telepathy Gabble installed?
>
> > /usr/local/lib/python2.7/dist-packages/jarabe/main.py:378: Warning:
> > g_value_transform: assertion 'G_IS_VALUE (src_value)' failed
> > Gtk.main()
> > /usr/local/lib/python2.7/dist-packages/jarabe/main.py:378: Warning:
> unable
> > to set property 'buddy' of type 'PyObject' from value of type
> '(null)'
> > Gtk.main()
> >
> > (metacity:2175): metacity-WARNING **: 12:05:04.405: Screen 0 on
> display
> > ":0" already has a window manager; try using the --replace option to
> > replace the current window manager.
> > /usr/local/lib/python2.7/dist-packages/jarabe/main.py:378: Warning:
> > g_spawn_command_line_async: assertion 'command_line != NULL' failed
> > Gtk.main()
> >
> > This is the log that I am getting on starting Sugar Desktop.
>
> Apart from the log, is there anything else that happens? i.e. does
> Sugar start and show the activity ring or Journal?
>
> > On Wed, May 15, 2019 at 1:49 PM James Cameron <[1]quozl at laptop.org>
> wrote:
> >
> > Thanks!
> >
> > I've proposed a pull request to let the caller specify the Python
> > version, and a draft pull request documenting how to build for both
> > versions.
> >
> > [2]https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/411
> > [3]https://github.com/sugarlabs/sugar/pull/829
> >
> > Aniket, when you say v0.113 this means you are using either git tag
> > v0.113 (i.e. e30b73f) or tarball. Seems unlikely you are doing that,
> > but instead you would be using HEAD of master branch instead. Is my
> > guess right?
> >
> > Regarding the segmentation fault, please check
> > .sugar/default/logs/shell.log for any details, or run within gdb and
> > capture a backtrace of all threads.
> >
> > On Wed, May 15, 2019 at 01:31:23PM +0530, ANIKET MATHUR wrote:
> > > Regards,
> > > I agree with, James. What I think is that since [1]this pr is not
> yet
> > merged
> > > into master, sugar requires python 2,
> > > and the way I was installing Sugar builds the toolkit for Python
> 3. So I
> > first
> > > installed Sugar from sucrose and then installed the toolkit-gtk3
> v0.113
> > by
> > > hand.
> > > Doing this I am able to test ported activities through the command
> line
> > using
> > > Ubuntu 18.04 terminal, but opening Sugar home view causes
> "Segmentation
> > fault"
> > > with a warning "python2.7 has stopped unexpectedly". I am not yet
> able to
> > > figure out the reason for this.
> > >
> > > Regarding the Python version in [2][4]configure.ac, I think that
> the
> > caller should
> > > be allowed to specify the version or alternatively since we are
> porting
> > to six,
> > > a method building for both python2 and python3 would be great.
> > >
> > > I don't expect myself to be 100 percent right and expect to be
> corrected
> > > wherever required.
> > >
> > > Thanks a lot, everyone. ☺
> > >
> > > On Wed, May 15, 2019 at 3:17 AM James Cameron <[3][5]
> quozl at laptop.org>
> > wrote:
> > >
> > > G'day Aniket,
> > >
> > > If you were using the native sugar build method, then you are
> using
> > > HEAD, which contains all patches since 0.113. Don't try to
> apply the
> > > patch that Alex pointed out, as it is already applied.
> > >
> > > The error message "ImportError: No module named sugar3" is
> caused by
> > > not installing the Toolkit for Python 2.
> > >
> > > Sugar 0.113 requires Python 2.
> > >
> > > Toolkit by default installs for Python 3.
> > >
> > > You can verify this is the situation by testing the import by
> hand
> > > using different versions of Python;
> > >
> > > python3 -c 'import sugar3' # expect pass
> > >
> > > python2 -c 'import sugar3' # expect fail
> > >
> > > You'll find in [4][6]configure.ac where the Python version is
> chosen.
> > >
> > > [5][7]
> https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/
> > configure.ac
> > > #L18
> > >
> > > Perhaps that line should allow the caller to specify the
> version.
> > >
> > > What do you think?
> > >
> > > On Tue, May 14, 2019 at 04:42:16PM +0530, ANIKET MATHUR wrote:
> > > > Greetings everyone,
> > > >
> > > > I was installing Sugar v0.113 using the Native Sugar build
> method
> > [1]
> > > here. I
> > > > was using Ubuntu 18.10. After installation, on running Sugar
> I
> > received
> > > the
> > > > error message "ImportError: No module named sugar3". Need
> help with
> > a
> > > couple of
> > > > questions
> > > > 1) Is there a need to have a build of the older version for
> v0.113
> > to
> > > work
> > > > properly?
> > > > (never paid attention to that before).
> > > > 2) What is the correct procedure for installing v0.113?
> > > > Thanks!
> > > >
> > > > References:
> > > >
> > > > [1] [6][8]
> https://github.com/sugarlabs/sugar/blob/master/docs/
> > > development-environment.md
> > >
> > > > _______________________________________________
> > > > Sugar-devel mailing list
> > > > [7][9]Sugar-devel at lists.sugarlabs.org
> > > > [8][10]http://lists.sugarlabs.org/listinfo/sugar-devel
> > >
> > > --
> > > James Cameron
> > > [9][11]http://quozl.netrek.org/
> > >
> > > References:
> > >
> > > [1] [12]https://github.com/sugarlabs/sugar/pull/805
> > > [2] [13]http://configure.ac/
> > > [3] mailto:[14]quozl at laptop.org
> > > [4] [15]http://configure.ac/
> > > [5] [16]
> https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/
> > configure.ac#L18
> > > [6] [17]https://github.com/sugarlabs/sugar/blob/master/docs/
> > development-environment.md
> > > [7] mailto:[18]Sugar-devel at lists.sugarlabs.org
> > > [8] [19]http://lists.sugarlabs.org/listinfo/sugar-devel
> > > [9] [20]http://quozl.netrek.org/
> >
> > --
> > James Cameron
> > [21]http://quozl.netrek.org/
> >
> > References:
> >
> > [1] mailto:quozl at laptop.org
> > [2] https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/411
> > [3] https://github.com/sugarlabs/sugar/pull/829
> > [4] http://configure.ac/
> > [5] mailto:quozl at laptop.org
> > [6] http://configure.ac/
> > [7]
> https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/configure.ac
> > [8] https://github.com/sugarlabs/sugar/blob/master/docs/
> > [9] mailto:Sugar-devel at lists.sugarlabs.org
> > [10] http://lists.sugarlabs.org/listinfo/sugar-devel
> > [11] http://quozl.netrek.org/
> > [12] https://github.com/sugarlabs/sugar/pull/805
> > [13] http://configure.ac/
> > [14] mailto:quozl at laptop.org
> > [15] http://configure.ac/
> > [16]
> https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/configure.ac#L18
> > [17]
> https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md
> > [18] mailto:Sugar-devel at lists.sugarlabs.org
> > [19] http://lists.sugarlabs.org/listinfo/sugar-devel
> > [20] http://quozl.netrek.org/
> > [21] http://quozl.netrek.org/
>
> --
> James Cameron
> http://quozl.netrek.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20190521/1ae2b7dc/attachment-0001.html>
More information about the Sugar-devel
mailing list