Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Beginner Error: ipython qtconsole #1431

Closed
super-cache-money opened this issue Feb 22, 2012 · 7 comments
Closed

Beginner Error: ipython qtconsole #1431

super-cache-money opened this issue Feb 22, 2012 · 7 comments
Milestone
old

Comments

@super-cache-money
Copy link

Hi there people!

I have been struggling for days to get ipython qtconsole to work.

Here are some details:

I am running ubuntu
I can run ipython fine.
I have installed libzmq 2.1.11 and pyzmq 2.1.11
When I attempt to run $ipython qtconsole, I get the following:

$sudo ipython qtconsole
python: /build/buildd/sip4-4.12.1/siplib/siplib.c:7860: sip_api_can_convert_to_type: Assertion `(((td)->td_flags & 0x0007) == 0x0000) || (((td)->td_flags & 0x0007) == 0x0002)' failed.
arjun@ArjunUbuntu:~$ [IPKernelApp] To connect another client to this kernel, use:
[IPKernelApp] --existing kernel-21405.json

What do I do?
@ivanov
Copy link
Member

ivanov commented Feb 22, 2012

just a shot in the dark, but have you tried doing this without sudo?

@super-cache-money
Copy link
Author

yes

@fperez
Copy link
Member

fperez commented Feb 24, 2012

You have a broken qt installation, it seems. This is not really an ipython bug, I bet you'd have problems running any PyQt app, as the error message is coming from deep inside Qt. Can you confirm first that you can indeed run arbitrary PyQt examples? I suggest debugging your PyQt installation first, as that seems to be what's broken here.

@super-cache-money
Copy link
Author

I reinstalled everything qt related, and it now works! Thanks!

On Fri, Feb 24, 2012 at 3:32 AM, Fernando Perez <
reply@reply.github.com

wrote:

You have a broken qt installation, it seems. This is not really an
ipython bug, I bet you'd have problems running any PyQt app, as the error
message is coming from deep inside Qt. Can you confirm first that you can
indeed run arbitrary PyQt examples? I suggest debugging your PyQt
installation first, as that seems to be what's broken here.

Reply to this email directly or view it on GitHub:
#1431 (comment)

@fperez
Copy link
Member

fperez commented Feb 24, 2012

good, closing.

@fperez fperez closed this as completed Feb 24, 2012
@juliantaylor juliantaylor mentioned this issue Jan 7, 2013
Merged
juliantaylor added a commit to juliantaylor/ipython that referenced this issue Jan 7, 2013
@juliantaylor
check for complete pyside presence before trying to import
9106259 
importing pyside partially and then falling back to pyqt causes a crash
in sip (see ipythongh-1431)
To avoid it try to locate all modules before the import and should that
fail print a warning.
@juliantaylor
Copy link
Contributor

with leousa in irc I could now reproduce this issue, the cause seems to be an incomplete pyside installation which is possible in debian and ubuntu.
Importing pyside partly and then falling back to pyqt causes this crash.

A fix is to install pyside completely (python-pyside.qtsvg python-pyside.qtcore python-pyside.qtgui), remove it or setting QT_API=pyqt ipython qtconsole

@juliantaylor juliantaylor mentioned this issue Jan 7, 2013
Closed
@leousa
Copy link

leousa commented Jan 7, 2013

I can confirm this issue and that installing the missing python-pyside packages fixed this issues. Once again thanks to the guys in ipyhon IRC channel for helping me figure this out.

minrk pushed a commit to minrk/ipython that referenced this issue Jan 26, 2013
@juliantaylor @minrk
check for complete pyside presence before trying to import
010e1ae 
importing pyside partially and then falling back to pyqt causes a crash
in sip (see ipythongh-1431)
To avoid it try to locate all modules before the import and should that
fail print a warning.
minrk added a commit that referenced this issue Mar 5, 2013
@minrk
Backport PR #2757: check for complete pyside presence before trying t…
b7de089 
…o import

importing pyside partially and then falling back to pyqt causes a crash
in sip (see gh-1431)
To avoid it try to locate all modules before the import and should that
fail print a warning.

debian splits pyside into many small packages so sometimes people end up with incomplete pyside installations.
@tacaswell tacaswell mentioned this issue Jul 18, 2014
Closed
mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this issue Nov 3, 2014
@juliantaylor
check for complete pyside presence before trying to import
15040c2 
importing pyside partially and then falling back to pyqt causes a crash
in sip (see ipythongh-1431)
To avoid it try to locate all modules before the import and should that
fail print a warning.
@elpaso elpaso mentioned this issue Apr 21, 2015
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
old
Development

No branches or pull requests
5 participants
@fperez @ivanov @juliantaylor @super-cache-money @leousa