Activity not working in Sugar 0.121

[tplobo]

Hi there. I tried downloading this Activity for my son but when we start it, it "fails to open". Any ideas how to fix that? How can I produce a log to attach to this issue?

[quozl]

Thanks.

The link you provided is for a Python 2 system, and chances are you are using a Python 3 system. Can you tell me what operating system and release version you are using?

Produce a log using the Log activity. Explanation here: https://help.sugarlabs.org/en/log.html

[tplobo]

Hey @quozl, thanks for the reply.
I have installed Sugar 0.121 on an Ubuntu 24.04.1 LTS using the sudo apt install sucrose command.
I have also checked whether my OS has python 2 installed, and indeed it only includes version 3.12.3.
I have saved the logs using the Log Activity as you suggested:
log-1735038418.zip

[quozl]

Thanks. There was no error in your Log for Physics, because Sugar wasn't able to start the activity at all because of missing Python 2, and didn't log why. So I created sugarlabs/sugar#991.

Hoping to see if I could deploy Physics in another way, I set up a container instance of Ubuntu 24.04.1 and installed Sugar in the same way you did.

Physics was no longer available as the package sugar-physics-activity, nor from v4.activities.sugarlabs.org, so I created #61, then cloned the repository and placed it in Sugar's activity path. Restart of Sugar showed the activity icon in the home view.

First try at running failed to start, and Log cited ModuleNotFoundError: No module named 'Box2D', so I followed How to install dependencies for development but got no such option: --system to which my response was pip3 install . --break-system-packages, and 96da52f ("Fix how to install dependencies").

Then it worked. Remove your current install of Physics and give my method a try?

[tplobo]

hey @quozl, thanks for the reply and sorry for the delay

Physics was no longer available as the package sugar-physics-activity, nor from v4.activities.sugarlabs.org, so I created #61, then...

I had actually installed the activity from activities.sugarlabs.org (but indeed not from v4.activities.sugarlabs.org, since it is not available there; thanks for #61 btw), and it was already visible in my Sugar installation.

I followed How to install dependencies for development but got no such option: --system to which my response was pip3 install . --break-system-packages, and 96da52f ("Fix how to install dependencies").

I directly followed your instructions without cloning the physics repo, and it did not work. But I then tried moving the original Physics.activity folder (that was inside the Activities directory) and cloned the repo into a brand new Physics.activity folder. This time the activity appeared again in my sugar desktop and it is working!

However, I do not know if it is behaving correctly. For example, the floor sometimes vanishes to a position below the lowest point of my monitor. I do not know if this is a different bug (and thus needs a new issue) or if it is a consequence of this method of installation to make it work with the current version of Sugar.

[quozl]

Thanks for the update. I've tried but was unable to dislodge the floor. Have you a way to reproduce that?

[quozl]

I think I've done it by opening toolbars; the floor exists, things don't fall off the universe, but it is not visible, so one toolbar width. Is that what you saw?

[tplobo]

I think I've done it by opening toolbars; the floor exists, things don't fall off the universe, but it is not visible, so one toolbar width. Is that what you saw?

yes, precisely that!

Other strange behavior includes: not being able to use the "Pin Tool" (I click and nothing happens, while the simulation is stopped or running), some flickering of the toolbars, the "Trash Can" being greyed out (unusable) in some instances even though I have items on the canvas, ...

[quozl]

Thanks. Guess there were changes to our dependencies such as Box2d or Pygame that will require changes in Physics to compensate. A developer will be needed to try selected prior versions of Box2d or Pygame and then perhaps iterate over the commit stream of each using git bisect.