[Sugar-devel] PyGame can be run only once assertion error

Manuel Quiñones manuq at laptop.org
Mon Sep 30 15:24:52 EDT 2013

2013/9/30 Alan Jhonn Aguiar Schwyn <alanjas at hotmail.com>:
> Good job!
> I have one question about other thing:
> Check this request:
> http://git.sugarlabs.org/sugargame/mainline/merge_requests/1#db3f934e9aea80f9effc98ba68516d69e7856a81-db3f934e9aea80f9effc98ba68516d69e7856a81

Looks good, I will rebase it (we use GTK3 now) and push.

> That fixes something? Because sometimes I get in the activities log
> something like this:
> The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
>   (Details: serial 953 error_code 9 request_code 130 minor_code 3)
>   (Note to programmers: normally, X errors are reported asynchronously;
>    that is, you will receive the error a while after causing it.
>    To debug your program, run it with the --sync command line
>    option to change this behavior. You can then get a meaningful
>    backtrace from your debugger if you break on the gdk_x_error() function.)

I don't think that this error is a consequence of not connecting the
visibility_notify_event or screen-changed event.  Looks more a
consequence of embedding the PyGame display in a GTK window, which
according to the PyGame documentation has side effects:


"Be aware that there can be many strange side effects when running in
an embedded display."

.. manuq ..

More information about the Sugar-devel mailing list