maemo.org - Talk
Page 2 of 3 1 2 3
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Development (https://talk.maemo.org/forumdisplay.php?f=13)
-   -   PR 1.3 and Qt version confusion... (https://talk.maemo.org/showthread.php?t=64402)

handaxe 2010-10-28 00:07
Re: PR 1.3 and Qt version confusion...
 
I might be off track here but see my reply here as I found something odd about the upgrade of the QT libraries

http://talk.maemo.org/showpost.php?p...9&postcount=79

jonnenau 2010-11-01 00:03
Re: PR 1.3 and Qt version confusion...
 
Quote:
Originally Posted by Yabba (Post 852901)
Ok, I have Segmentation fault with my program (pyKake), arise with Pr 1.3. As I have tracked it down it is in QApplication, so I just put this short question here (before I create new topic or anything), is this caused compatibility problems with Qt4.7 and current PyQt or have I done something terribly wrong (except that with Pr 1.2 the program worked fine)

The (short) code:
Code:
print "a"
app = QApplication(sys.argv) # Allways crashes here, newer prints out that b or later ones.
print "b"
MiscFunctions().loadSettings()
print "c"
MiscFunctions().controlLircd("start")
print "d"

main = MainWindow()
print "e"
if USEFULLSCREEN == True:
    print "f"
    main.showFullScreen()
else:
    print "g"
    main.show()
print "h"
app.exec_()
MiscFunctions().exitFunction()
I have the exact same problem with my dropn900 app, it's essentially broken in PR 1.3. Attila any ideas what might be causing this? My code is only different so that I have subclassed QApplication and my init is "QApplication.__init__(self, sys.argv)". maemo repository is giving me 504 when doing dist-upgrade to PR1.3 so im a bit stuck, cant even try to resolve this but on the device :E

attila77 2010-11-01 00:18
Re: PR 1.3 and Qt version confusion...
 
In theory, the new Qt should be binary compatible with the old one and everything should 'just work'. In theory. Well, we'll see soon enough if a PyQt4.8 (or just a recompile) will help it.

Rob1n 2010-11-01 14:56
Re: PR 1.3 and Qt version confusion...
 
Quote:
Originally Posted by attila77 (Post 859100)
In theory, the new Qt should be binary compatible with the old one and everything should 'just work'. In theory. Well, we'll see soon enough if a PyQt4.8 (or just a recompile) will help it.
I've been debugging my app and have found that moving all other Qt import statements (other than QApplication) until after initialising QApplication eliminates the segmentation fault. I don't see why this should be needed though, so I suspect it's more a PyQt issue.

jonnenau 2010-11-01 21:56
Re: PR 1.3 and Qt version confusion...
 
Quote:
Originally Posted by Rob1n (Post 859734)
I've been debugging my app and have found that moving all other Qt import statements (other than QApplication) until after initialising QApplication eliminates the segmentation fault. I don't see why this should be needed though, so I suspect it's more a PyQt issue.
Yes this works, very very strange though. Lets see after we get the next PyQt update. I just reinstalled my whole development env with fresh everything, did not install any Qt 4.7 experimental related things, just the needed PyQt packages and some other python things that I can run my app. Segfaults would indicate the crash is somewhere in the c++ libs of course, maybe some confusion with the numbers.

Thanks a lot robin for your help!

keithzg 2010-11-02 02:20
Re: PR 1.3 and Qt version confusion...
 
Soooooo, is the not-yet-updated PyQt the reason I'm getting this error on any PyQt apps?

Using khweeteur as an example,

Code:
Traceback (most recent call last):
  File "/usr/bin/khweeteur_launch.py", line 3, in <module>
    import khweeteur
  File "/usr/lib/python2.5/site-packages/khweeteur/__init__.py", line 9, in <module>
    from PyQt4.QtGui import *
RuntimeError: the sip module implements API v8.0 but the PyQt4.QtGui module requires API v7.1
All my searching doesn't seem to have come up with *anyone* else with the same problem, which has me suspecting that my apt-get dist-upgrade was a bad idea in the end ;) Unfortunately this is really delaying my attempts to learn PyQt by writing an app for my local transit system, alas!

Yabba 2010-11-02 08:35
Re: PR 1.3 and Qt version confusion...
 
Thank you Rob1n and Jonnenau, moving the initializing of QApplication solved my problem too :)

int_ua 2010-11-06 16:39
Re: PR 1.3 and Qt version confusion...
 
Code:
>>> from PyQt4.QtGui import *
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
RuntimeError: the sip module implements API v8.0 but the PyQt4.QtGui module requires API v7.1
Can someone point the bug for this to vote for?

blubbi 2010-11-10 11:40
Re: PR 1.3 and Qt version confusion...
 
Okay, now this is getting weird.
In fact it has something to do with PyQt4 and not playing nice with some other modules (so far I could track down gobject, glib, and evolution).

Here's a proof of concept for this bug:

Code:
#!/usr/bin/env python
# -*- coding: utf-8 -*-
#

import sys
from PyQt4.QtGui import QApplication

##NOTE: Uncommenting this import (even each on it's own) cause a segfault
##NOTE: Using the same import after initializing QApplication() works!
#import gobject, glib, evolution

print "hello1"
app = QApplication(sys.argv)
print "hello2"

##NOTE: This does not cause a segfault:
import gobject, glib, evolution
print "hello3"

sampppa 2010-11-11 20:32
Re: PR 1.3 and Qt version confusion...
 
Quote:
Originally Posted by int_ua (Post 865288)
Code:
>>> from PyQt4.QtGui import *
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
RuntimeError: the sip module implements API v8.0 but the PyQt4.QtGui module requires API v7.1
Can someone point the bug for this to vote for?
I get the same error with the latest dropn900 from extras-devel. I had fresh n900 and nothing else installed. DropN900 was the first one i wanted to try :)


All times are GMT. The time now is 22:16.
Page 2 of 3 1 2 3
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8