Bug 266969

Application: kopete (1.0.80)
KDE Platform Version: 4.6.00 (4.6.0)
Qt Version: 4.7.1
Operating System: Linux 2.6.37-sabayon x86_64
Distribution: "Gentoo Base System release 2.0.1"

-- Information about the crash:
I'm using Sabayon Linux (gentoo based) fully updated.

- What I was doing when the application crashed:
Kopete crash when starting. I have autoconnect enabled.

- Unusual behavior I noticed:
I try --noplugins --noconnect command line options
Kopete starts well and then I'm able to start session with XMPP (2 gmail accounts)
When connecting wlm account kopete crash again.

This is what I get on console:

JingleSessionManager::JingleSessionManager created. 
Creating the PushJingleSession task.... 
Object::connect: No such signal XMPP::JingleSessionManager::incomingSession()
Create JingleCallsManager 
Created Media Manager. 
Unknown signature value:  795 
Unknown signature value:  7 
Unknown signature value:  7 
Unknown signature value:  7 
Unknown signature value:  7 
JingleSessionManager::JingleSessionManager created. 
Creating the PushJingleSession task.... 
Object::connect: No such signal XMPP::JingleSessionManager::incomingSession()
Create JingleCallsManager 
Created Media Manager. 
KCrash: Application 'kopete' crashing...
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit

The crash can be reproduced every time.

-- Backtrace:
Application: Kopete (kopete), signal: Segmentation fault
[KCrash Handler]
#6  0x00007fdec6a12900 in X509_NAME_cmp () from /usr/lib/libcrypto.so.1.0.0
#7  0x00007fdec4c980b2 in OBJ_bsearch_ex () from /usr/lib/libcrypto.so.0.9.8
#8  0x00007fdec4cf48cc in ?? () from /usr/lib/libcrypto.so.0.9.8
#9  0x00007fdec4d269d5 in X509_OBJECT_retrieve_match () from /usr/lib/libcrypto.so.0.9.8
#10 0x00007fdec4d2710f in X509_STORE_add_cert () from /usr/lib/libcrypto.so.0.9.8
#11 0x00007fdee3febe33 in ?? () from /usr/lib64/qt4/libQtNetwork.so.4
#12 0x00007fdee3feed09 in ?? () from /usr/lib64/qt4/libQtNetwork.so.4
#13 0x00007fdee3fe3908 in ?? () from /usr/lib64/qt4/libQtNetwork.so.4
#14 0x00007fdee3fe8745 in QSslSocket::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/qt4/libQtNetwork.so.4
#15 0x00007fdec5be0ea8 in ?? () from /usr/lib64/kde4/kopete_wlm.so
#16 0x00007fdee78b7ae7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
#17 0x00007fdee3fc79de in ?? () from /usr/lib64/qt4/libQtNetwork.so.4
#18 0x00007fdee3fc9b58 in ?? () from /usr/lib64/qt4/libQtNetwork.so.4
#19 0x00007fdee3fba5f9 in ?? () from /usr/lib64/qt4/libQtNetwork.so.4
#20 0x00007fdee69c9ddc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#21 0x00007fdee69ce95d in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#22 0x00007fdee833b4b6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#23 0x00007fdee789fe5c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#24 0x00007fdee78cc28a in ?? () from /usr/lib64/qt4/libQtCore.so.4
#25 0x00007fdee0e7b6b0 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#26 0x00007fdee0e7f5e8 in ?? () from /usr/lib/libglib-2.0.so.0
#27 0x00007fdee0e7f79c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#28 0x00007fdee78cbed3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#29 0x00007fdee6a7adae in ?? () from /usr/lib64/qt4/libQtGui.so.4
#30 0x00007fdee789eb82 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#31 0x00007fdee789ef6c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#32 0x00007fdee78a302b in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4
#33 0x00000000004160f2 in _start ()

This bug may be a duplicate of or related to bug 245486.

Possible duplicates by query: bug 245486, bug 233631.

Reported using DrKonqi