ipython-wx segfaults when %pylab called

Bug #509330 reported by Gokhan Sever on 2010-01-18
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

This segfault is caused by ipython-wx using from the unstable IPython branch at:


To reproduce: Start %pylab in a session.

$ ipython-wx
/usr/lib/python2.6/site-packages/wx-2.8-gtk2-unicode/wx/_core.py:14450: UserWarning: wxPython/wxWidgets release number mismatch
  warnings.warn("wxPython/wxWidgets release number mismatch")
Could not open Options.conf, defaulting to default values.
Segmentation fault (core dumped)

Also reported at: https://bugzilla.redhat.com/show_bug.cgi?id=556601

IPython version: 0.11.bzr.r1346
Platform info : os.name -> posix, sys.platform -> linux2
               : Linux-
Python info : 2.6.2 (r262:71600, Aug 21 2009, 12:22:21) [GCC 4.4.1 20090818 (Red Hat 4.4.1-6)]

Fernando Perez (fdo.perez) wrote :

Did you remember to uncheck the 'threading' box? If I uncheck that, it works fine on my ubuntu box. Also remember to run 'pylab wx' in the ipython-wx box, not just 'pylab', in case your default backend isn't wx.



Yes unchecking the "Execute in thread" option solves the segfault. %pylab automatically switch me to the wx backend mode. Even %pylab qt starts the wx.

Fernando Perez (fdo.perez) wrote :

since ipython-wx already shows a big warning dialog about unchecking that for pylab use, and it works as intended, closing for now.

Changed in ipython:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers