Comment 8 for bug 156679

Revision history for this message
Bruno coudoin (bruno-coudoin) wrote :

I confirm the issue but I cannot explain it. Here is the backtrace:
[Switching to Thread -1224730944 (LWP 14744)]
_wrap_gnome_canvas_item_set (self=0x84a04b4, args=0x8652404, kwargs=0x84a446c) at canvas.override:172
172 canvas.override: No such file or directory.
        in canvas.override
(gdb) bt
#0 _wrap_gnome_canvas_item_set (self=0x84a04b4, args=0x8652404, kwargs=0x84a446c) at canvas.override:172
#1 0xb513c85d in PyCFunction_Call (func=0x8493b4c, arg=0x8652404, kw=0x0) at ../Objects/methodobject.c:77
#2 0xb5105c17 in PyObject_Call (func=0x84a04b4, arg=0x8652404, kw=0x84a446c) at ../Objects/abstract.c:1860
#3 0xb51858cc in PyEval_EvalFrameEx (f=0x8334714, throwflag=0) at ../Python/ceval.c:3775
#4 0xb518b734 in PyEval_EvalCodeEx (co=0x87f95c0, globals=0x849cd74, locals=0x0, args=0x84a81a0,
    argcount=4, kws=0x0, kwcount=0, defs=0x0, defcount=0, closure=0x0) at ../Python/ceval.c:2831
#5 0xb5128a4a in function_call (func=0xb50b0d84, arg=0x84a8194, kw=0x0) at ../Objects/funcobject.c:517
#6 0xb5105c17 in PyObject_Call (func=0x84a04b4, arg=0x84a8194, kw=0x0) at ../Objects/abstract.c:1860
#7 0xb510d438 in instancemethod_call (func=0x84a0504, arg=0x84a8194, kw=0x0)
    at ../Objects/classobject.c:2509
#8 0xb5105c17 in PyObject_Call (func=0x84a04b4, arg=0x84a0644, kw=0x0) at ../Objects/abstract.c:1860
#9 0xb518380c in PyEval_CallObjectWithKeywords (func=0x84a0504, arg=0x84a0644, kw=0x0)
    at ../Python/ceval.c:3433
#10 0xb5105f2c in PyObject_CallObject (o=0x84a0504, a=0x84a0644) at ../Objects/abstract.c:1851
#11 0xb5055607 in ?? () from /var/lib/python-support/python2.5/gtk-2.0/gobject/_gobject.so

I have absolutely no idea what may cause this crash. The workaround is to play at another python based activity first.
I tested on gutsy GCompris 8.3.4, the latest stable in the 8.3 branch and it does work fine.
Sadly, there are no changes I can see concerning this code. There maybe a side effect in the build process or from another
fix.

Can someone build a 8.3.4 on gutsy following the official process and check if the problem is still there.