Le lundi 25 mai 2009 à 20:12 +0200, Julien Valroff a écrit :
>
> Many thanks for sharing your experience with this issue.
>
> I am not able to reproduce the issue neither with listen.
>
> I keep you informed whether I manage to find anything useful...
>
> Cheers,
> Julien
>
tags 519758 patch
Le lundi 25 mai 2009 à 19:58 +0200, Julien Lavergne a écrit :
>
> Hi,
>
Hi Julien,
> Let me share what I have found on this, working on the similar bug on
> screenlets [1].
> After reporting this bug upstream [2], they advise me to change the
> way
> Class are initialized, using class Foo(objec
Hi,
Let me share what I have found on this, working on the similar bug on
screenlets [1].
After reporting this bug upstream [2], they advise me to change the way
Class are initialized, using class Foo(object) instead of only class
Foo .
This fixed the problem for some users, but not for some other
Hi,
I get this error when running your script within gdb:
Starting program: /usr/bin/python gui.py
[Thread debugging using libthread_db enabled]
Program received signal SIGSEGV, Segmentation fault.
PyType_IsSubtype (a=0xabc530, b=0x75867240)
at ../Objects/typeobject.c:836
836 ../Objects/
Le samedi 14 mars 2009 à 22:52 +0100, arno renevier a écrit :
> Package: python-gobject
> Version: 2.16.1-1
> Severity: normal
>
> Hi,
> Attached script segfaults with following trace:
I can’t reproduce that. Instead, I get an error:
TypeError: Error when calling the metaclass bases
value fo
Package: python-gobject
Version: 2.16.1-1
Severity: normal
Hi,
Attached script segfaults with following trace:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f9adbc676f0 (LWP 2138)]
0x0045dd45 in PyType_IsSubtype ()
(gdb) where
#0 0x0045dd45 in PyTyp
6 matches
Mail list logo
