Re: [Sugar-devel] Toolkit Installation Sugar v0.113

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 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 >

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

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

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

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 **:

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

Aniket, I've refined the native environment instructions after testing on Fedora 30 and Ubuntu 19.04. I've made a pull request here; https://github.com/sugarlabs/sugar/pull/830 It is a hybrid configuration, which may leave a copy of the downstream Sugar packages in /usr, and our latest HEAD in

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

It is a wicked problem. Here are my thoughts; 1. there are three temporal scopes of dependency; build time, run time, and those for downloaded activities, 2. our activity bundle specification doesn't list dependencies, so we had early assumptions about what would be available, 3. some of

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

Thanks. James. Agreed, there can be a number of runtime dependencies that the user has to install. I don't think mentioning them all in the documentation will be a good idea. What do you think? On Thu, May 16, 2019 at 9:31 AM James Cameron wrote: > Thanks for testing, Aniket. > > Because 0.113

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

Thanks for testing, Aniket. Because 0.113 introduces a dependency on Six for the first time, the method of resolving dependencies in the instructions is out of date. I've added https://github.com/sugarlabs/sugar/pull/829/commits/97d1ef60b65a0fffe52ec4070944e2b03fe56ac2 to the pull request. Yes,

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

hey, I tested the changes that James made. I started with a fresh Ubuntu 18.04 VM. Cloned artwork, datastore, toolkit-gtk3, and sugar. Applied his patch to toolkit-gtk3 and then followed the native procedure in the documentation considering his changes. I installed the toolkit for both python2 and

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

James by v 0.113 I mean HEAD. Sorry for the confusion. On Wed, 15 May 2019, 1:49 pm James Cameron, 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. > >

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

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. https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/411 https://github.com/sugarlabs/sugar/pull/829 Aniket, when you say v0.113 this means you

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

Regards, I agree with, James. What I think is that since 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

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

+1 On 5/14/19 8:41 PM, Walter Bender wrote: Any chance of a 0.113.1 maintenance release [1] to make this patch available? Seems unreasonable to expect mere mortals to find and apply patches just to get started. regards. -walter [1] https://en.wikipedia.org/wiki/Maintenance_release On Tue,

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

I've two answers. 1. No. Aniket did not hit the problem for which this patch is the solution. 2. No. Next release is 0.114, and I'm waiting on better evidence of testing of 0.113 plus the errata patches. Mere mortals may confine themselves to Fedora 30 which has Sugar 0.113, or Ubuntu 19.04

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

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

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

Any chance of a 0.113.1 maintenance release [1] to make this patch available? Seems unreasonable to expect mere mortals to find and apply patches just to get started. regards. -walter [1] https://en.wikipedia.org/wiki/Maintenance_release On Tue, May 14, 2019 at 11:46 AM Alex Perez wrote: >

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

Aniket, You have hit a known bug for 0.113. Please see https://github.com/sugarlabs/sugar/issues/822 I should also point out that this was an easily search-able issue, and would encourage you to use Google or your preferred search engine, when you encounter issues like this in the future.

[Sugar-devel] Toolkit Installation Sugar v0.113

Greetings everyone, I was installing Sugar v0.113 using the Native Sugar build method here . I was using Ubuntu 18.10. After installation, on running Sugar I received the error message "ImportError: No module named