Closed Dimi20cen closed 1 year ago
Yes, that's expected. Based on the versions in your other logs you are using Ubuntu 22.04, which had Sugar Datastore 0.118, with a known problem since fixed in https://github.com/sugarlabs/sugar-datastore/commit/df4f45697d07a49cbdd2fcd0c90fbaebf3c539ab caused by an API change.
Upgrade the python3-carquinyol package to fix the ValueError, then please test again to see if you get the "Invalid resolution for Surface" error. Thanks.
(For testing, it may be possible to place the Sugar Datastore module inside the activity source tree. I've not done that for a while, but it has worked before.)
I'm now using 0.120 Sugar, the dbus error is fixed. Now I just get the following "Gtk-CRITICAL **: 18:17:41.931: gtk_widget_draw: assertion '!widget->priv->alloc_needed' failed". This issue isn't present in the live-build.
Perhaps you should assign environment variable G_DEBUG=fatal-criticals
in order to capture more details of the execution context associated with the message, especially a traceback.
Does the message appear in logs of any other activities? If so, the issue may be with the toolkit, not the activity. See https://github.com/sugarlabs/log-activity/issues/21 for the same message in the Log activity.
I'm now using 0.120 Sugar, the dbus error is fixed. Now I just get the following "Gtk-CRITICAL **: 18:17:41.931: gtk_widget_draw: assertion '!widget->priv->alloc_needed' failed". This issue isn't present in the live-build.
The activity runs now correct?
I haven't tried quozl's solution yet, but the issue is probably with my installation of sugar. I get a black page with all pygame activities I have tried. With other pygame activities I don't get an error or warning either, so yeah, it's something on my side that I need to fix, sorry for not updating sooner.
I haven't tried quozl's solution yet, but the issue is probably with my installation of sugar. I get a black page with all pygame activities I have tried. With other pygame activities I don't get an error or warning either, so yeah, it's something on my side that I need to fix, sorry for not updating sooner.
The black page you're seeing is because of pygame1.9, update to pygame2.0 and the activities should work fine.
Support for SDL_WINDOWID
in pygame has been added for SDL 2, that's why you're experiencing that.
I already have pygame 2.1.2
I think the version that fixed the issue is 2.3.0
You absolutely need to have Sugar and activities running properly before embarking on any real development, in order to avoid having to repeat your changes once you find they aren't compatible in some way.
Mine wasn't a solution, but a step toward identifying the problem.
I mainly try out and test activities with the live build and with the native builds on vm, thankfully I resolved any issues with those. But yeah I don’t use the packaged build
I think the version that fixed the issue is 2.3.0
Just used 2.3.0 and yep, now pygame activities work as expected, thank you
Great! Closing this now.
I get the following logs, might be an issue with the journal and might not be related to the activity.