Seg fault with latest dev snapshot of spyderlib on linux mint (ubuntu) 64 bit with pyside

[spyderlibuser]

I'm trying to run spyderlib (I donwloaded the dev branch, I also tried
with 2.1.9 zip file). I'm getting a segfault.
Here is the output when run through gdb. I'm on 64 bit linux mint (a
derivative of ubuntu)
I'd appreciate any help to debug this. (details are below)

-------------------------------------------------------


GNU gdb (Ubuntu/Linaro 7.3-0ubuntu2) 7.3-2011.08
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/
gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show
copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.launchpad.net/gdb-linaro/>...
Reading symbols from /usr/bin/python...(no debugging symbols
found)...done.
Starting program: /usr/bin/python bootstrap.py
[Thread debugging using libthread_db enabled]
Executing Spyder from source checkout
Revision 2003:32085ff749a8, Branch: default
01. Patched sys.path with ./spyderlib
02. PySide is detected, selecting (experimental)
03. Imported Spyder 2.2.0dev (Qt 4.7.4 via PySide 1.1.0)
0x. Enforcing parent console (Windows only)
04. Executing spyder.main()

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff45eb0dd in
Shiboken::Conversions::isPythonToCppConvertible(SbkConverter*,
_object*) () from /usr/lib/x86_64-linux-gnu/libshiboken-python2.7.so.
1.1

(gdb) bt
#0 0x00007ffff45eb0dd in
Shiboken::Conversions::isPythonToCppConvertible(SbkConverter*,
_object*) () from /usr/lib/x86_64-linux-gnu/libshiboken-python2.7.so.
1.1
#1 0x00007ffff5186be1 in ?? () from /usr/lib/python2.7/dist-packages/
PySide/QtGui.so
#2 0x000000000047c1d1 in ?? ()
#3 0x000000000041ad2a in PyObject_Call ()
#4 0x00000000004b6b9e in PyEval_EvalFrameEx ()
#5 0x00000000004bcd2d in PyEval_EvalCodeEx ()
#6 0x0000000000448edf in ?? ()
#7 0x000000000041ad2a in PyObject_Call ()
#8 0x000000000043074e in ?? ()
#9 0x000000000041ad2a in PyObject_Call ()
#10 0x00000000004b6b9e in PyEval_EvalFrameEx ()
#11 0x00000000004b6d77 in PyEval_EvalFrameEx ()
#12 0x00000000004b6d77 in PyEval_EvalFrameEx ()
#13 0x00000000004bcd2d in PyEval_EvalCodeEx ()
#14 0x00000000004b6a5b in PyEval_EvalFrameEx ()
#15 0x00000000004bcd2d in PyEval_EvalCodeEx ()
#16 0x00000000004b6a5b in PyEval_EvalFrameEx ()
#17 0x00000000004bcd2d in PyEval_EvalCodeEx ()
#18 0x00000000004b6a5b in PyEval_EvalFrameEx ()
#19 0x00000000004bcd2d in PyEval_EvalCodeEx ()
#20 0x00000000004b6a5b in PyEval_EvalFrameEx ()
#21 0x00000000004bcd2d in PyEval_EvalCodeEx ()
#22 0x00000000004b6a5b in PyEval_EvalFrameEx ()
#23 0x00000000004bd325 in PyEval_EvalCodeEx ()
#24 0x0000000000448edf in ?? ()
#25 0x000000000041ad2a in PyObject_Call ()
#26 0x000000000043074e in ?? ()
#27 0x000000000041ad2a in PyObject_Call ()
#28 0x0000000000480c73 in ?? ()
#29 0x000000000047c1d1 in ?? ()
#30 0x000000000041ad2a in PyObject_Call ()
#31 0x00000000004b6b9e in PyEval_EvalFrameEx ()
#32 0x00000000004bd325 in PyEval_EvalCodeEx ()
#33 0x00000000004b6a5b in PyEval_EvalFrameEx ()
#34 0x00000000004b6d77 in PyEval_EvalFrameEx ()
#35 0x00000000004b6d77 in PyEval_EvalFrameEx ()
#36 0x00000000004bcd2d in PyEval_EvalCodeEx ()
#37 0x00000000004bd802 in PyEval_EvalCode ()
#38 0x00000000004dcc22 in ?? ()
#39 0x00000000004dd7e4 in PyRun_FileExFlags ()
#40 0x00000000004de2ee in PyRun_SimpleFileExFlags ()
#41 0x00000000004ee6dd in Py_Main ()
#42 0x00007ffff699e30d in __libc_start_main () from /lib/x86_64-linux-
gnu/libc.so.6

[Carlos Córdoba]

Spyder doesn't work with the latest PySide version. We think it should
run fine with next one but we're waiting for it to be released and we
don't know when that could happen. So in the meantime you'll have to use
PyQt.

Cheers,
Carlos

El 19/04/12 07:55, spyderlibuser escribió:

[spyderlibuser]

don't know when that could happen. So in the meantime you'll have to use
PyQt.

Is there a way to tell spyderlib to use PyQT instead of Pyside?

[Carlos Córdoba]

Using

$ python bootstrap.py --gui=pyqt

Inside your spyder snapshot

El 19/04/12 14:23, spyderlibuser escribió:

don't know when that could happen. So in the meantime you'll have to use
PyQt.

Is there a way to tell spyderlib to use PyQT instead of Pyside?

--
You received this message because you are subscribed to the Google Groups "spyder" group.
To view this discussion on the web visit https://groups.google.com/d/msg/spyderlib/-/Kr6HPHh1arUJ.
To post to this group, send email to spyd...@googlegroups.com.
To unsubscribe from this group, send email to spyderlib+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/spyderlib?hl=en.

[Pierre Raybaut]

Or, if you prefer the environment variable approach, you may also create a variable named "QT_API" with the value "pyqt". 

-Pierre