On Friday 21 January 2011, you wrote:
> Hi guys we experienced the issue as well and can for us creating a
> entirely new Ubuntu User solved the problem. So for the moment the
> problem doesn't seem to be related to packages in the first place but
> rather to configuration of the GTK environment.
Can you check which "engine" is the Gtk theme using at each case?
GTK engines are C programs and sometimes influence the allocation/deallocation
of "objects" at that framework. Then, Python may find itself tracking a wrongly
referenced object..
On Friday 21 January 2011, you wrote:
> Hi guys we experienced the issue as well and can for us creating a
> entirely new Ubuntu User solved the problem. So for the moment the
> problem doesn't seem to be related to packages in the first place but
> rather to configuration of the GTK environment.
Can you check which "engine" is the Gtk theme using at each case? deallocation
GTK engines are C programs and sometimes influence the allocation/
of "objects" at that framework. Then, Python may find itself tracking a wrongly
referenced object..