[PySide] QSslSocket in Linux
Erik Johansson
erik.johansson at fido.se
Mon Jul 8 12:33:00 CEST 2013
Runtime ssl enabled QSslSocket in pyside on linux as well.
On Fri, Jul 5, 2013 at 2:39 PM, Erik Johansson <erik.johansson at fido.se>wrote:
> Going to try on a qtbuild that was built with runtime instead of linked
> openssl and see if that helps.
>
>
> On Fri, Jul 5, 2013 at 2:36 PM, Erik Johansson <erik.johansson at fido.se>wrote:
>
>> Yeah, it's those instructions I am following.
>>
>> When trying to open an https page maya segfaults with:
>> QMetaObject::invokeMethod: No such method
>> WebCore::SocketStreamHandlePrivate::socketSentData()
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x00007fffe1a9acc4 in RSA_size () from
>> /usr/autodesk/maya2012-x64/lib/libcrypto.so.6
>> (gdb) bt
>> #0 0x00007fffe1a9acc4 in RSA_size () from
>> /usr/autodesk/maya2012-x64/lib/libcrypto.so.6
>> #1 0x00007fffe1a281bd in RSA_verify () from
>> /usr/autodesk/maya2012-x64/lib/libcrypto.so.6
>> #2 0x00007fffb5842433 in ssl3_get_key_exchange () from
>> /usr/lib64/libssl.so.0.9.8
>> #3 0x00007fffb5844c50 in ssl3_connect () from /usr/lib64/libssl.so.0.9.8
>> #4 0x00007fffea0878fb in ?? () from
>> /usr/autodesk/maya2012-x64/lib/libQtNetwork.so.4
>> #5 0x00007fffea088a03 in ?? () from
>> /usr/autodesk/maya2012-x64/lib/libQtNetwork.so.4
>> #6 0x00007fffea0830df in QSslSocket::qt_metacall(QMetaObject::Call, int,
>> void**) () from /usr/autodesk/maya2012-x64/lib/libQtNetwork.so.4
>> #7 0x00007fffed497849 in QMetaObject::activate(QObject*, QMetaObject
>> const*, int, void**) () from /usr/autodesk/maya2012-x64/lib/libQtCore.so.4
>> #8 0x00007fffea0659c3 in ?? () from
>> /usr/autodesk/maya2012-x64/lib/libQtNetwork.so.4
>> #9 0x00007fffea0556c1 in ?? () from
>> /usr/autodesk/maya2012-x64/lib/libQtNetwork.so.4
>> #10 0x00007fffec7e6f0e in QApplicationPrivate::notify_helper(QObject*,
>> QEvent*) () from /usr/autodesk/maya2012-x64/lib/libQtGui.so.4
>> #11 0x00007fffec7edb70 in QApplication::notify(QObject*, QEvent*) () from
>> /usr/autodesk/maya2012-x64/lib/libQtGui.so.4
>> #12 0x00007ffff4c4bd6e in QmayaApplication::notify(QObject*, QEvent*) ()
>> from /usr/autodesk/maya2012-x64/lib/libExtensionLayer.so
>> #13 0x00007fffed4827c3 in QCoreApplication::notifyInternal(QObject*,
>> QEvent*) () from /usr/autodesk/maya2012-x64/lib/libQtCore.so.4
>> #14 0x00007fffed4ae17b in ?? () from
>> /usr/autodesk/maya2012-x64/lib/libQtCore.so.4
>> #15 0x0000003bd6a38f0e in g_main_context_dispatch () from
>> /lib64/libglib-2.0.so.0
>> #16 0x0000003bd6a3c938 in ?? () from /lib64/libglib-2.0.so.0
>> #17 0x0000003bd6a3ca3a in g_main_context_iteration () from
>> /lib64/libglib-2.0.so.0
>> #18 0x00007fffed4ae2c5 in
>> QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
>> () from /usr/autodesk/maya2012-x64/lib/libQtCore.so.4
>> #19 0x00007fffec890aef in ?? () from
>> /usr/autodesk/maya2012-x64/lib/libQtGui.so.4
>> #20 0x00007fffed481b85 in
>> QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
>> /usr/autodesk/maya2012-x64/lib/libQtCore.so.4
>> #21 0x00007fffed481dec in
>> QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
>> /usr/autodesk/maya2012-x64/lib/libQtCore.so.4
>> #22 0x00007fffed483c69 in QCoreApplication::exec() () from
>> /usr/autodesk/maya2012-x64/lib/libQtCore.so.4
>> #23 0x00007ffff4c487a9 in Tapplication::start() () from
>> /usr/autodesk/maya2012-x64/lib/libExtensionLayer.so
>> #24 0x000000000040eeaa in appmain() ()
>> #25 0x000000000041cf21 in main ()
>>
>> So maybe its not pysides fault but some funky system lib.
>>
>> //Erik
>>
>>
>> On Fri, Jul 5, 2013 at 1:30 PM, Mike Owen <mjnowen at gmail.com> wrote:
>>
>>> Hi Erik,
>>> Have you seen these pages?
>>>
>>> http://around-the-corner.typepad.com/adn/2012/10/building-qt-pyqt-pyside-for-maya-2013.html
>>> http://images.autodesk.com/adsk/files/pyqtmaya2013.pdf
>>> Mike
>>>
>>>
>>> On 5 July 2013 12:00, Erik Johansson <erik.johansson at fido.se> wrote:
>>>
>>>> Hi again list
>>>>
>>>>
>>>> I have been compiling Qt and PySide for use with autodesk maya in linux
>>>> but can't seem to get QSslSocket and ssl support working. It works in osx
>>>> and windows.
>>>>
>>>> Qt is build with
>>>> ./configure -separate-debug-info -no-rpath -no-qt3support -no-phonon
>>>> -no-phonon-backend -openssl-linked
>>>>
>>>> and openssl is found during build.
>>>>
>>>> When configuring pyside i see:
>>>> -- Found OpenSSL: /usr/lib64/libssl.so
>>>> and:
>>>> -- Checking for QSslCertificate in QtNetwork -- found
>>>> -- Checking for QSslCipher in QtNetwork -- found
>>>> -- Checking for QSslConfiguration in QtNetwork -- found
>>>> -- Checking for QSslError in QtNetwork -- found
>>>> -- Checking for QSslKey in QtNetwork -- found
>>>> -- Checking for QSslSocket in QtNetwork -- found
>>>>
>>>> But when import QtNetwork and printing out dir(QtNetwork) this is the
>>>> result:
>>>>
>>>> ['QAbstractNetworkCache', 'QAbstractSocket', 'QAuthenticator', 'QFtp',
>>>> 'QHostAddress', 'QHostInfo', 'QHttp', 'QHttpHeader', 'QHttpRequestHeader',
>>>> 'QHttpResponseHeader', 'QIPv6Address', 'QLocalServer', 'QLocalSocket',
>>>> 'QNetworkAccessManager', 'QNetworkAddressEntry', 'QNetworkCacheMetaData',
>>>> 'QNetworkConfiguration', 'QNetworkConfigurationManager', 'QNetworkCookie',
>>>> 'QNetworkCookieJar', 'QNetworkDiskCache', 'QNetworkInterface',
>>>> 'QNetworkProxy', 'QNetworkProxyFactory', 'QNetworkProxyQuery',
>>>> 'QNetworkReply', 'QNetworkRequest', 'QNetworkSession', 'QSsl',
>>>> 'QTcpServer', 'QTcpSocket', 'QUdpSocket', 'QUrlInfo', '__doc__',
>>>> '__file__', '__name__', '__package__']
>>>>
>>>>
>>>> and upon trying to visit an page with https the application crashes.
>>>>
>>>>
>>>> If anyone got some ideas or knows if its some known bug please let me
>>>> know.
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> Erik
>>>>
>>>> _______________________________________________
>>>> PySide mailing list
>>>> PySide at qt-project.org
>>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130708/78101592/attachment.html>
More information about the PySide
mailing list