animation blit under gtk*

I just noticed that the blit API in GTK* is causing a seg fault on my
desktop. Can anyone confirm this on another system. Has anyone made
any changes that you are aware of that might have affected this part
of the code? I am seeing problems with
examples/animation_blit.py and examples/poly_editor.py so it looks
like anything using the copy region / blit API in GTK is broken, at
least on my system. tkagg is working fine, so it is probably not a
problem on the agg side, and GTK and GTKAgg are both affected. I
don't use this functionality often, so I don't know how long the
problem has persisted. In fact, it is possible I have never tested it
on this system (solaris x86 with pygtk 2.6)

JDH

John Hunter wrote:

I just noticed that the blit API in GTK* is causing a seg fault on my
desktop. Can anyone confirm this on another system. Has anyone made
any changes that you are aware of that might have affected this part
of the code? I am seeing problems with
examples/animation_blit.py and examples/poly_editor.py so it looks
like anything using the copy region / blit API in GTK is broken, at
least on my system. tkagg is working fine, so it is probably not a
problem on the agg side, and GTK and GTKAgg are both affected. I
don't use this functionality often, so I don't know how long the
problem has persisted. In fact, it is possible I have never tested it
on this system (solaris x86 with pygtk 2.6)

JDH

John: Works fine on OS X with

Gtk+: gtk+: 2.6.10, glib: 2.12.4, pygtk: 2.6.3, pygobject [pre-pygobject]

-Jeff

···

--
Jeffrey S. Whitaker Phone : (303)497-6313
Meteorologist FAX : (303)497-6449
NOAA/OAR/PSD R/PSD1 Email : Jeffrey.S.Whitaker@...236...
325 Broadway Office : Skaggs Research Cntr 1D-124
Boulder, CO, USA 80303-3328 Web : http://tinyurl.com/5telg

Works on RHEL4, with most applicable things built from source... Python 2.5, Gtk+: gtk+: 2.10.9, glib: 2.12.9, pygtk: 2.10.4, pygobject: 2.13.1

Cheers,
Mike

Jeff Whitaker wrote:

···

John Hunter wrote:

I just noticed that the blit API in GTK* is causing a seg fault on my
desktop. Can anyone confirm this on another system. Has anyone made
any changes that you are aware of that might have affected this part
of the code? I am seeing problems with
examples/animation_blit.py and examples/poly_editor.py so it looks
like anything using the copy region / blit API in GTK is broken, at
least on my system. tkagg is working fine, so it is probably not a
problem on the agg side, and GTK and GTKAgg are both affected. I
don't use this functionality often, so I don't know how long the
problem has persisted. In fact, it is possible I have never tested it
on this system (solaris x86 with pygtk 2.6)

JDH

John: Works fine on OS X with

Gtk+: gtk+: 2.6.10, glib: 2.12.4, pygtk: 2.6.3, pygobject [pre-pygobject]

-Jeff

--
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

All OK here too, SVN build of numpy/matplotlib, ubuntu Feisty standard
packages of everything else:

In [6]: gtk.gtk_version
Out[6]: (2, 10, 11)

In [7]: gtk.pygtk_version
Out[7]: (2, 10, 4)

Python 2.5.1 (r251:54863, May 2 2007, 16:56:35)

Cheers,

f

···

On Dec 3, 2007 12:12 PM, Michael Droettboom <mdroe@...31...> wrote:

Works on RHEL4, with most applicable things built from source... Python
2.5, Gtk+: gtk+: 2.10.9, glib: 2.12.9, pygtk: 2.10.4, pygobject: 2.13.1